Moving a dashboard via update set does not carry over all widgets when the dashboard tab is broken - Known Error

Moving a dashboard via update set does not carry over all widgets when the dashboard tab is broken Description Moving a dashboard via an update set does not carry over all widgets to target instance when the dashboard tab is broken. However, it allows adding widgets to the broken tabs in source instance.

Steps to Reproduce

1. Create a new dashboard with one tab.

2. Add a few OOB PA widgets.

3. Create a new local update set unload this dashboard.

4. Move to another instance, commit the update set, confirm the dashboard looks good.

5. On the source instance (where dashboard was originally created), create a new local update set.

6. Create a new tab on the dashboard and add some widgets to this tab.

7. Go to the update set confirm the newly added updates are included in the update set.

8. Mark the update set as complete.

9. Export to XML or retrieve completed update sets from the target instance.

10. Import the XML on the target instance again, preview the update set.

11. Preview results show errors of type: "Could not find a record in sys_portal_page for column page referenced in this update" "Could not find a record in sys_portal_page for column legacy_page referenced in this update" "Could not find a record in sys_portal for column portal_widget referenced in this update"

12. Accept remote update and commit the update set. The commit is successful, the dashboard shows the new tab but no widgets on this tab. There is no message indicating "This tab is broken".

13. Admin users are then able to add content to this tab even if there is no page associated with the tab.

14. Unload the dashboard from this target instance into an update set, this will have a broken tab without the associated portal page.

Workaround This is expected behaviour when not following the documented guidelines. In order for the dashboard to be moved correctly between instances using update set, all the tabs need to have valid associated components. If the tab is broken i.e. does not have a portal page associated with it, the admin users are still able to add widgets to dashboard tab. If you re-link the portal page to tab and unload the dashboard, the widgets added to the tab when it was broken will still not be unloaded to update set. It is required to re-link the missing portal page to the tab before adding new widgets. The portal page being added should contain the same widgets as the canvas page associated with the same tab. The sys_portal_page records and the sys_grid_canvas ones need to be kept in synch due to continued support of the legacy dashboards (non-responsive ones). The sys_portal_page table records are not automatically tracked by the platform (update_synch=false) and need to be manually unloaded as explained in the documentation. The process of unloading a dashboard and all its associated records is facilitated by the "Unload dashboard" option at the dashboard record level.

Rebuilding the broken dashboard tab is the valid recommended workaround once the issue has occurred. Move a dashboard with an update set : In the source instance, navigate to the location of the dashboard you want to unload, for example, Self-Service > Dashboards. Select the dashboard you want to unload to an update set. Click the context menu icon and select Dashboard Properties to open the dashboard record. Click the context menu icon and select Unload Dashboard. Only perform this step once the dashboard is ready to unload, meaning that all content is added to the tabs. When you are ready to move the update set, mark the update set as complete. On the target instance, move the update using standard update set functionality. For more information, see Retrieve an update set . On the Remote Instance page, the Retrieved Update Sets related list shows all retrieved update sets. Click the update set to see if there are errors. Errors are shown on the Retrieved Update Set form in a related list calledUpdate Set Preview Problems. See Solving errors on dashboards moved with update sets . On the target instance, make sure that all the tabs of the dashboard have associated portal pages. See Validate that tabs have moved to a target dashboard . If the portal page is missing in the Tab form, click the search icon next to the Page field to search for the associated portal page. NOTE : If you can not find the associated portal page in the target instance, follow these steps to move each missing portal page through the update: Navigate to Homepage Admin > Pages Filter the list to show only the portal page with the sys_id you copied Right-click the record and select Unload Portal Page Related Problem: PRB1358285