Hi Anupriya,
Based on your screenshots, I would suggest troubleshooting the date-filter persistence and KPI filtering behavior separately, as they are controlled by different configurations in Platform Analytics.
1. Retaining the selected date range when reopening the dashboard
In Platform Analytics, the Date filter supports a default relative date range that is applied when the dashboard opens.
Please try the following:
- Open the dashboard in Edit mode.
- Select the existing Date filter.
- Open its configuration panel.
- Check the Default values setting.
- Verify whether the default is configured as This month, Last month, or another relative range.
- Save the configuration and reopen the dashboard.
If the default is configured as This month, the dashboard may initialize with October 2026 rather than retaining your previous September selection. If you want the dashboard to open with the previous month automatically, configure Last month as the default. However, retaining the user’s last manually selected date range is different from configuring a default value.
For preserving a particular filter selection, you can also try the dashboard’s Share → Copy link with filter option.
Open the dashboard, select the required date range, generate the filtered link, and reopen the dashboard using that link.
This can help preserve the selected filter state through the URL, subject to the supported filter types and your ServiceNow release.
2. Do KPI visualizations require a breakdown for date filtering?
No, a breakdown is not mandatory for standard date filtering in Platform Analytics.
For supported Performance Analytics indicator visualizations, please verify the Apply date range configuration.
You can check this by:
- Opening the dashboard in Edit mode.
- Selecting the KPI visualization.
- Opening the visualization configuration.
- Locating the Date range settings.
- Enabling Apply date range, if available.
- Saving the visualization.
This allows the dashboard Date filter to affect the indicator visualization.
For time-series visualizations, date-range application is implicit.
Breakdowns are primarily intended to segment indicator data by attributes such as Priority, Category, or Assignment Group.
3. Filtering KPI data using the Closed date field
This depends on whether your KPI uses table-based data or Performance Analytics indicator scores.
If the KPI is table-based, configure the dashboard Date filter against the relevant table and select the Closed date field, such as closed_at.
For example, selecting September 2026 should restrict the underlying records to those closed during September, provided the visualization and filter are configured correctly.
If the KPI is based on a Performance Analytics indicator, the Date filter generally operates on the indicator’s collected scores.
It does not necessarily recalculate the indicator using the Closed date field of the underlying records.
In that case, please verify:
- Indicator source configuration
- Source conditions
- Collection frequency
- Historical indicator scores
- Date-range aggregation settings
If the requirement is to dynamically count records closed within any selected date range, a table-based Score visualization may be more appropriate than an indicator with a fixed collection window.
4. Why are Last month and This month working while other date ranges are inaccurate?
This could be related to historical score availability, indicator collection conditions, aggregation settings, or the date-filter configuration.
Please check the following:
- Verify that historical indicator scores exist for the selected periods.
- Confirm that the indicator collection jobs completed successfully.
- Check whether the indicator source uses a fixed date condition, such as Last 30 days.
- Verify that the KPI visualization has Apply date range enabled.
- Review the Show data for selected period as setting.
For example, if your indicator collects the number of records closed each day and the KPI should display the total for the selected month, Sum may be appropriate.
However, if the indicator represents a snapshot of records at a particular point in time, Latest score may be more appropriate. The correct aggregation depends on the indicator’s underlying calculation.
5. Recommended validation
Since your screenshot shows 8 records for September 2026 and 323 for October 2026, I recommend comparing these values with the underlying records or collected indicator scores.
If you are expecting the KPI to count records based on Closed date, open the source table and apply the equivalent Closed date conditions.
Compare those results with the KPI visualization.
If the results differ, check whether the KPI is using historical indicator scores rather than the underlying record dates.
6. Suggested configuration
For a dashboard that must dynamically filter records by Closed date:
- Use a supported table-based Score visualization.
- Configure the appropriate source table and conditions.
- Add a Platform Analytics Date filter.
- Map the Date filter to the Closed date field.
- Configure the appropriate default date range.
- Validate the KPI results against the underlying records.
If you must continue using Performance Analytics indicators, ensure that the collection logic and historical scores support the required reporting periods.
A date breakdown is not required simply to enable date filtering. I would first check the Date filter’s default configuration, enable Apply date range for the KPI visualizations where applicable, and verify whether the KPI is using indicator scores or table records. The key point is that filtering Performance Analytics scores by their collection date is not necessarily equivalent to filtering source records by Closed date. Could you confirm which ServiceNow release you are using and whether the Priority Level 1 and Priority Level 2 KPIs are Performance Analytics indicators or table-based Score visualizations?
That will help identify the most appropriate configuration.
Hope this helps!
Sasibhushan Rao Chanthati (sasi)
