Platform Analytics Dashboard-Prevent visualizations from loading until interactive filter is selcted

[vyshnavikan]

Hi All,

I am working on a Platform Analytics Dashboard that contains a sys_user interactive filter.

Requirement:

- When the dashboard initially loads, visualizations should not load any data.

- Users must first select a value from the sys _ user interactive filter.

- Once a user is selected, all visualizations should display data related to that user.

- If no user is selected, visualizations should show "No data available".

Current setup:

- Interactive filter source = sys _ user

- Filter is connected to the visualizations through the appropriate fields.

- Default value is blank.

- I could not find an option to make the interactive filter mandatory before visualizations load.

Questions:

1. Is there a supported way in Platform Analytics Dashboards to prevent visualizations from loading until an interactive filter value is selected?

2. Is this typically achieved through Interactive Filter configuration, Indicator Source/Data Source conditions, or another approach?

Additionally, I need to restrict the sys _ user filter lookup to only actual human users and exclude service/system accounts. What is the recommended approach for this in Platform Analytics interactive filters?

Any guidance would be appreciated.

Thanks.

[shubhamseth]

@vyshnavikan 

For Requirement #1

A common approach is to design the indicator/data source so that it returns no records when the user filter is empty.

For example:

• Add a condition that expects a valid user value.
• If the interactive filter is blank, the query returns zero records and the visualization displays "No data available".

This is generally handled at the Indicator Source/Data Source level rather than through the Interactive Filter configuration itself.

 

For Requirement #2 (Exclude Service Accounts)

The recommended approach is to apply a reference qualifier/filter on the interactive filter source so that only human users are returned.

Typical filters include:

active=true
AND user_nameNOT LIKEsvc_
AND user_nameNOT LIKEsystem

Or, even better, filter based on:

• User criteria
• Department
• Employee type
• Role membership

For example:

active=true^employee_numberISNOTEMPTY

This is usually more reliable than naming conventions.