Dashboard Widgets not being captured properly in update set

[nityabans27]

Hi @everyone,

I created a pre-defined filter on a report source and attached it to an existing widget. However, when I capture the widget, the filter is not being captured with it. Only the original widget is captured, and the pre-defined filter is captured separately as a report source record.

Has anyone faced this issue before or knows how to ensure the filter is captured along with the widget?

[nishant3101 · Accepted solution]

Hi,

Yes, I’ve run into this before. When you create a pre-defined filter on a Report Source and attach it to a widget, the platform doesn’t treat that filter as part of the widget record. Instead, it treats it as a separate Report Source configuration, which is why it gets captured independently.

Why this happens:

• Widget records only store references (like the data source or filter ID).

• Report Source filters are stored as their own records.

• So, when you use ATF / Update Set / Capture UI, ServiceNow captures the widget and the report source separately.

How to ensure it moves together:

1. Include the Report Source filter record in the same Update Set where the widget is captured.

2. Make sure both records move to the target instance together — otherwise the widget will load without the expected filter.

3. If you want the filter baked into the widget, you can also consider:

   • Hardcoding the filter directly in the widget’s server script

   • Or creating a custom data source with the filter included

Extra tip: Report Source changes don’t always auto-capture, so manually add the filter record if needed.

If this helps, please mark the answer as Resolved — it may help others facing the same issue!

[prajaktajga · Accepted solution]

Hello @nityabans27 ,

1.Pre-defined filters on Report Sources do not get included when capturing a widget.
2.Manually add the filter to the same update set.

[nishant3101 · Accepted solution]

Hi,

Yes, I’ve run into this before. When you create a pre-defined filter on a Report Source and attach it to a widget, the platform doesn’t treat that filter as part of the widget record. Instead, it treats it as a separate Report Source configuration, which is why it gets captured independently.

Why this happens:

• Widget records only store references (like the data source or filter ID).

• Report Source filters are stored as their own records.

• So, when you use ATF / Update Set / Capture UI, ServiceNow captures the widget and the report source separately.

How to ensure it moves together:

1. Include the Report Source filter record in the same Update Set where the widget is captured.

2. Make sure both records move to the target instance together — otherwise the widget will load without the expected filter.

3. If you want the filter baked into the widget, you can also consider:

   • Hardcoding the filter directly in the widget’s server script

   • Or creating a custom data source with the filter included

Extra tip: Report Source changes don’t always auto-capture, so manually add the filter record if needed.

If this helps, please mark the answer as Resolved — it may help others facing the same issue!

[prajaktajga · Accepted solution]

Hello @nityabans27 ,

1.Pre-defined filters on Report Sources do not get included when capturing a widget.
2.Manually add the filter to the same update set.

[Ankith Sharma · Accepted solution]

Hi @nityabans27 

Yes, I’ve seen this behaviour a couple of times while moving dashboards across instances.

The widget record itself doesn’t store the filter, ServiceNow keeps the pre-defined filter inside the Report Source, so the platform treats it as a separate configuration item. Because of that, the widget gets captured, but the filter doesn’t come along automatically.

What usually works for me is:

• After creating or modifying the pre-defined filter, open the Report Source record and switch the update set there as well.

• Save it once so the filter is captured properly.

• Then go back to the widget and re-save the widget so the reference is fresh.

Once both records are in the same update set, the dashboard usually behaves correctly after migration.

If you found this useful, please mark it as Helpful and Accepted.

— Ankit