https://community.splunk.com/t5/Reporting/Knowledge-object/m-p/690561#M12498 <P>Assuming you don't have suitable admin permissions to directly manipulate knowledge objects, then the simplest way is to&nbsp;</P><P>Dashboard</P><UL><LI>Edit the dashboard source, copy the dashboard</LI><LI>Change to new app, create new dashboard and paste the data</LI></UL><P>If you cannot edit the dashboard, but can clone it, then clone it privately, edit the dashboard and copy as above</P><P>Lookup - assuming the existing lookup is app visible only and NOT global</P><UL><LI>in the source app run&nbsp;</LI></UL><LI-CODE lang="markup">| inputlookup lookup_to_be_copied.csv | outputlookup my_tmp_copy.csv</LI-CODE><P>then in the new app space do</P><LI-CODE lang="markup">| inputlookup my_tmp_copy.csv | outputlookup new_name_in_new_app.csv</LI-CODE><P>This assumes that when you do the&nbsp; outputlookup, it will get private or global app permissions. If it gets global, then the new app will see this, but take care - you don't want 2 lookups of the same name with global scope.</P><P>If it is output as private then you should be able to 'upgrade' the permissions to app scope in the new app.</P><P>Much will depend on the permissions you have</P> Wed, 12 Jun 2024 22:18:42 GMT bowesmana 2024-06-12T22:18:42Z https://community.splunk.com/t5/Reporting/Knowledge-object/m-p/690542#M12497 <P>How do i clone a dashboard and lookuptables from one App to another in Splunk</P> Wed, 12 Jun 2024 19:34:14 GMT https://community.splunk.com/t5/Reporting/Knowledge-object/m-p/690542#M12497 whitecat001 2024-06-12T19:34:14Z https://community.splunk.com/t5/Reporting/Knowledge-object/m-p/690561#M12498 <P>Assuming you don't have suitable admin permissions to directly manipulate knowledge objects, then the simplest way is to&nbsp;</P><P>Dashboard</P><UL><LI>Edit the dashboard source, copy the dashboard</LI><LI>Change to new app, create new dashboard and paste the data</LI></UL><P>If you cannot edit the dashboard, but can clone it, then clone it privately, edit the dashboard and copy as above</P><P>Lookup - assuming the existing lookup is app visible only and NOT global</P><UL><LI>in the source app run&nbsp;</LI></UL><LI-CODE lang="markup">| inputlookup lookup_to_be_copied.csv | outputlookup my_tmp_copy.csv</LI-CODE><P>then in the new app space do</P><LI-CODE lang="markup">| inputlookup my_tmp_copy.csv | outputlookup new_name_in_new_app.csv</LI-CODE><P>This assumes that when you do the&nbsp; outputlookup, it will get private or global app permissions. If it gets global, then the new app will see this, but take care - you don't want 2 lookups of the same name with global scope.</P><P>If it is output as private then you should be able to 'upgrade' the permissions to app scope in the new app.</P><P>Much will depend on the permissions you have</P> Wed, 12 Jun 2024 22:18:42 GMT https://community.splunk.com/t5/Reporting/Knowledge-object/m-p/690561#M12498 bowesmana 2024-06-12T22:18:42Z