Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
alexpanjhc
Specialist
Specialist

show all rows in the pivot table regardless null values

Hi experts!

i have an external contact table , an internal contact table and a table about their meeting time .

external contact table has a contactID linked to meeting table

internal contact table has a employeeid linked to meeting table, and i tagged some employees with leader and i only want to show them below.

not all contactids are in the meeting table, not all employees are showing in the meeting table either.

 

if i do not check the include null values, it will show like this below, if i check it will not show external contact 3.

i want to show external contact 3 and also not want to see the null value at the last column.

how do i do that? 

thanks for your help

  internal contact1 internal contact2 internal contact3 internal contact4 -
external contact 1 june-2-2022        
external contact 2   aug-4-2023      
external contact 3 - - - - -
Labels (3)
12 Replies
marcus_sommer

Yes, it's possible. But it may not be trivial and will probably need some efforts. Quite important is to understand the various kinds of NOTHING - their cause and effects - to decide how to handle them. Very helpful for the matter are the explanations here:

NULL handling in QlikView - Qlik Community - 1484472 

alexpanjhc
Specialist
Specialist
Author

thank you for that link.

i am asking visualization wise, is it possible to show external contact 3 if i uncheck include nulls  for internal contact in pivot table.

 

or another ay to ask is how to keep external contact 3 while not showing null on the internal contacts?

marcus_sommer

I think there should be a possibility to do it only within the UI - but rather not with the default-properties and/or without adjustments to the dimensions and expressions. Probably only by the use of calculated dimensions which could become quite tricky and complex and which have often serious side-effects in regard to the usability and the performance.

From a general point of view such tasks should be better resolved within the data-model as within the UI. Therefore I suggest to start there.