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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Gabbar
Specialist
Specialist

Show Zero Values Button Customisation

Hi Everyone, 
I have a table, the user has requested to have a button to select 
Show Zero Values or not in a table in an ADHOC kind of report (User can select which measure and Dimensions to show).

I tried 2 methods
1st one was to create a measure that will show a value of '1' when 'Yes' is selected in Show Zero Values.

This solution conflicts with User Experience as it adds another Column.

2nd Solution was to create a Table with the same structure (One with a Show Zero Checked and another without checked) and put both the tables in a container, which shows the table based on selection.

This would have worked with 1 table, but there are multiple tables that require the same functionality.

Has anyone ever faced this ?

Version :- Qlik Sense Enterprise Version of 2023.


Labels (3)
4 Replies
Sivapriya_d
Creator
Creator

Hi @Gabbar 

if possible, you can derive the measure in the backend and create a flag field for zero, then in button setup action to filter the flag field to reduce records in Table


Thanks,

marcus_sommer

There are no real shortcuts for such a task.

For ZERO records are customized objects (extensions) thinkable which are providing an external control of certain object-features. Whereby this won't be sufficient for not existing NULL records. To show these kind of information and making them accessible it needs always to create appropriate dimensional values. This could be done in general within the UI with calculated dimensions but they are quite tricky and coming with more or less significantly disadvantages in the usability and performance.

Simpler is it usually to populate the missing data within the data-model - especially if it's limited to a few essential areas and not against many fields with a depth granularity. 

Gabbar
Specialist
Specialist
Author

Thanks @Sivapriya_d ,
But that would mean adding a Field to the table, which is not good on UX part.

Gabbar
Specialist
Specialist
Author

Hi @Sivapriya_d , Thanks
butThat would also create additional fields, which is a UX issue