How can we replicate interactive and cascading filter in Platform Analytics dashboard

[naraharasetti]

Hi Team,

Previously, interactive and cascading filters were functioning correctly in Performance Analytics. However, after migrating from the traditional dashboard to Platform Analytics, these filters are no longer working as expected and are resulting in incorrect data.

We raised this with the vendor team, and they confirmed that interactive and cascading filters are not automatically migrated to Platform Analytics. Therefore, we need to manually recreate these filters in the Platform Analytics dashboard to match the behavior of the existing Performance Analytics dashboard.

As this is a high-priority issue, could you please provide a clear, step-by-step procedure to implement interactive and cascading filters in Platform Analytics without any discrepancies, ensuring the same functionality as the previous dashboard?

Your support in resolving this at the earliest would be highly appreciated.

[vaishali231]

Hey @naraharasetti 
What the vendor mentioned is correct. During the migration from Performance Analytics dashboards to Platform Analytics dashboards, interactive filters and cascading filter configurations are not automatically carried over. The dashboard visualizations may be migrated, but the filter relationships generally need to be recreated manually.
To achieve the same behavior as the legacy dashboard, you can follow the approach below:
Review the existing Performance Analytics dashboard and document:
All interactive filters
Cascading filter relationships (parent-child dependencies)
Fields used by each filter
Widgets affected by each filter
Open the Platform Analytics dashboard in edit mode and create equivalent dashboard filters for each legacy filter.
Configure filter dependencies:
Create the parent filter first.
Configure the child filter to use the parent filter as its dependency.
Verify that child filter values are dynamically restricted based on the selected parent value.
Associate the filters with the required visualizations/widgets.
Ensure every widget that should respond to the filter is mapped correctly.
Missing filter-to-widget associations are a common cause of inconsistent results.
Validate the underlying data sources:
Confirm the filter fields exist in the data source used by the widget.
Verify indicator sources, breakdowns, and datasets support the filtering field.
If the legacy dashboard relied on PA breakdowns, additional configuration may be required in Platform Analytics.
Perform side-by-side validation:
Apply the same filter combinations in both dashboards.
Compare widget results, drilldowns, and record counts.
Check whether any widget is using a different source table or aggregation logic after migration.
A few areas worth checking if the numbers are still different:
Dashboard filters are not connected to all widgets.
The filter field is unavailable in the widget's dataset.
Breakdown mappings differ between the legacy PA dashboard and Platform Analytics.
Some visualizations are using different indicator sources or aggregation methods.

*********************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb