Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Catch up on the newest Qlik features and improvements: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
Abh1234
Contributor
Contributor

Qlik Sense Filter Pane - Prevent Users from Selecting Greyed-Out Values?

Hi,

I am looking for recommendations regarding Filter Pane selection behavior in Qlik Sense.

Current Scenario

I have a Year filter pane containing values such as:

  • 2022
  • 2023
  • 2024
  • 2025

When a user selects one year (for example, 2025), Qlik Sense correctly evaluates the associations in the data model.

As expected:

  • The selected year remains green.
  • Some other years become greyed out because they are no longer associated with the current selection.
  • The greyed-out values indicate that no matching records exist for the current selection state.

However, even though those years are greyed out, users can still click and select them.

Example

Initial State:

□ 2022

□ 2023

□ 2024

□ 2025

After selecting 2025:

✓ 2025 (green)

 

□ 2024 (grey)

□ 2023 (grey)

□ 2022 (grey)

Even though 2022, 2023, and 2024 are greyed out (excluded values), users are still able to click and add those selections.

Requirement

Ideally, I would like the greyed-out years to behave as locked or disabled values so that users cannot select them once they are excluded by the current selection state.

The objective is to make the filter behavior more intuitive and prevent users from creating selection combinations that are not meaningful for the analysis.

Questions

  1. Is there any native Qlik Sense functionality to prevent users from selecting greyed-out values in a Filter Pane?
  2. Can excluded values be automatically locked, frozen, or made non-clickable?
  3. Is there any setting available in Filter Pane properties that controls this behavior?
  4. Has anyone implemented a custom solution to achieve this?
  5. What would be considered the best practice for this type of requirement?

I would be interested in hearing how other developers handle this situation in production dashboards.

Thank you!

 

Labels (1)
1 Reply
tres_sdz
Contributor III
Contributor III

Hi @Abh1234 ,
You can try using expression like : Aggr(Year, Year) , instead of the direct field in the listbox