Clarification on "Unload Dashboard" vs Update Set Capture in ServiceNow

[mypdi]

Hi Community,
Why is the "Unload Dashboard" option available in the form header when dashboard updates are already captured in update sets?

[Ankur Bawiskar · Accepted solution]

@mypdi 

"Unload Dashboard" is present because not everything gets captured and migrated

check this KB

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

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[mypdi · Accepted solution]

Hi @Ankur Bawiskar ,

My understanding is that update sets can fail to capture incremental dashboard changes (like adding new tabs or widgets later), whereas Unload Dashboard ensures everything including dependencies is captured correctly.
It means Unload Dashboard captures all  related records of Dashboard from the start in update set.
so when we again import this via update set ,matched records get updated and new records get created.

Is this understanding accurate, or am I missing something?

Thanks

[mypdi]

Hello community,
I've checked multiple posts and articles but couldn't find a clear answer.

@Ankur Bawiskar  @GlideFather   @Dr Atul G- LNG   could you please share your thoughts on this?

Thanks in advance

[Dr Atul G- LNG]

Hi @mypdi 

The "Unload Dashboard" option in ServiceNow form headers allows administrators to pack a dashboard’s structure—including tabs, widgets, and layout—into a Local Update Set for migration between instances. It acts as a specialized transfer tool for dashboard configuration when automated capture fails. 

How to Use the Unload Dashboard Option

1. Navigate to the desired dashboard and click the context menu icon in the header.
2. Select Dashboard Properties.
3. Click the context menu icon again and choose Unload Dashboard.
4. Navigate to System Update Sets > Local Update Sets to mark the active update set as Complete

[mypdi]

Hi @Dr Atul G- LNG ,
Thanks for the reply.

I tried creating a dashboard with two tabs and different widget layouts, then moved it via an update set to another PDI. Everything worked as expected.

Could you please share specific scenarios where update sets fail to capture dashboard changes properly and using "Unload Dashboard" becomes necessary?

Thanks!

[Dr Atul G- LNG · Accepted solution]

Hi @mypdi 

To clarify, if you build a dashboard with a couple of tabs and then move it to another instance without any issues, it usually means everything has been captured properly in the update set. In such cases, the changes are straightforward and migrate as expected.

However, there are many scenarios where this is not the case. For example, if the dashboard was built while the user was working across different parts of the platform, some components or configurations might not be fully captured in the update set. This makes it difficult to guarantee that all changes will move correctly.

There are mixed experiences with this. Sometimes, the update set captures everything related to the dashboard in one go, while in other cases, it does not. This inconsistency is why dashboard migrations can be tricky and require careful validation.