Some reports in my dashboard not getting displayed even after Moving Dashboard from one PDI to another PDI through 'Unload Dashboard' with the help of Update Sets.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-22-2022 05:06 AM
I have created one Dashboard in my PDI. I have added some Reports that I created and also some OOB reports as widgets to my Dashboard. I wanted to migrate that dashboard (to move that dashboard) to Another PDI instance with all of the reports included. I had done the migration by using 'Unload Dashboard' option and captured it with an update set.
I retrieved the update set in my target instance and committed it. The dashboard I created got moved to the target instance with all OOB reports displayed. But the reports created by me in the source instance was not displaying in the target instance. It was showing like (as in the screenshot attached) :
I have used the following 'Product Documentation' and 'KB Article' as reference for moving the dashboard via update set :
Move a dashboard with an update set (servicenow.com)
Deep Copy a Dashboard from one ServiceNow Instance to Another - Support and Troubleshooting
I need to display the Reports which I created in the Source Instance to the Target Instance. Any suggestions would be helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2022 02:58 AM
Can you please elaborate the steps on Exporting and importing my reports and merging it with my moved dashboard?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2025 04:23 AM
Hi,
This error is due to the records in sys_portal and sys_portal_page for the dashboard is not found in the target instance.
The solution I found while facing this was to export the xml of these records(your dashboard specific records from sys_portal and sys_portal_page) and import them to the target instance first. After importing the xml, if you migrate the update set, you should no longer face this error and the dashboard layout or reports should not be messed up or empty.
Also, you may need to capture the records separately in the updateset along with the dashboard as the SysID of the reports may sometimes differ from different instances.
Thankyou.