Is it possible to move a dashboard AND CONTENTS in an update set?

[Tracy Davis]

I need to create reports and dashboards in Dev and promote them using update sets. I can capture all the reports (contents) in an update set and get those moved. But then I really would like to be able to move the entire dashboard with the contents/layout included.

The only thing I can find about moving a dashboard though only seems to move the dashboard name and tab names - it doesn't auto populate with the report content? Am I missing something?

I am having to rebuild the dashboards in each of our sub prod environments after moving the update set with the reports in it. Is there a better way to do this?

[ytrottier]

Good point.

[Les1]

Anyone figure out how to successfully do this? i'm trying to recover the Discovery Dashboard on our PROD instance that was deleted by exporting from sub-Prod instance but cant figure out how to accomplish. ive tried to follow the documentation link but not found that to work, seems like it just captures the base page record (which i can import as xml anyway) and doesnt capture the content elements (dropzones)

[bvloch]

This procedure does not move the content of the dashboard (such as reports, PA widgets, content blocks, and other widgets) to the update set. 

https://docs.servicenow.com/bundle/madrid-performance-analytics-and-reporting/page/use/performance-a...

[Adam Stout]

If you build everything in an application, you can move it all together.  If not, you have to build you update set like anything else in ServiceNow.  You may want to look at how to add the UI action to "Force to Update Set" which will allow you to manually push things to an update set.

The reason for this is pretty straight forward.  What do you want to overwrite and what don't you?  A Dashboard has Tabs which have Report and Widgets which have Indicators which may have Indicators (in the case of formula) which have Indicator Sources and Job and Breakdowns and Breakdown Sources.  If you always took all of this, you would end up with major collision headaches.  The current implementation allows you to only take the changed and use everything else from production.  If this isn't desired, using a scoped app may solve this as it always moves everything in the application.