The CreatorCon Call for Content is officially open! Get started here.

Dashboard is showing empty in test environment post deployment

venori26
Tera Contributor

Hello Team,

 

I am facing issues in deployment of a Dashboard that is developed in platform analytics. I have created updateset and included every possible component in it, like tabs,canvas,widgets,indicators, breakdowns etc.there are around 103 components that are added in update set.

 

Post deployment to test, the dashboard is showing blank, with no tabs or data or visualizations.

 

Did anyone face such issue? any suggestions would be of help..thanks in advance!

 

 

venori26_0-1760191797139.png

 

1 REPLY 1

NavinAgarwal
Kilo Guru

Hi @venori26 ,

 

The most likely reason your dashboard is showing blank after deployment is that the dashboard itself, or its associated content, was not fully captured in the update set. To fix this, first try navigating to the dashboard and clicking "View Homepage" to see if it displays the widgets. If that doesn't work, clear the dashboard's cache in the target instance and try again. For future deployments, ensure all components are correctly included by creating the dashboard and its content in an update set, then migrating the entire update set to the target instance. 

 

Troubleshooting steps:

 

  • View the dashboard on the target instance:
    Go to Homepage Admin > Pages on the target instance. 

Find the record for the dashboard and click View Homepage to see if it displays correctly. 

 

  • Clear the dashboard cache:
    If the dashboard is still not showing content, find the dashboard's sys\_id or name in the par_dashboard_cache table. 

Delete the record from the par_dashboard_cache table. 

In the instance, navigate to cache.do and clear the cache. 

Log out and then log back in to the instance. 

 

Best practices for future deployments:

  • Ensure all components are included: 
    When creating the dashboard, make sure to create all components, such as tabs, widgets, indicators, and breakdowns, in the same update set as the dashboard itself. 
  • Consider using a script for comprehensive migration: 
    For a more reliable migration process, you may want to use a script to capture all dashboard components automatically. You can create a catalog item with a script that captures all elements related to the selected dashboard. 

Related resources:

 

For more information on migrating dashboards, you can refer to the https://www.servicenow.com/docs/bundle/yokohama-now-intelligence/page/use/dashboards/task/move-pae-d...

 

 

To learn more about dashboard caching, see this ServiceNow article

https://www.servicenow.com/community/s/cgfwn76974/attachments/cgfwn76974/platform-analytics-blog/879...

 

If you found my response helpful, could you please mark it as ‘Accept as Solution’ and ‘Helpful’? This small action goes a long way in helping other community members find the right answers more easily and supports the community.