Table not appearing in Levels

[JustinDallas]

Hello Folks,

We are on NPrinting May 2022 SR2.  I have a table in QlikSense that does not appear in the Levels selector, but does appear in the Tables selection.  

What could be the cause of this?

Any help is greatly appreciated.

[Lech_Miszkiewicz · Accepted solution]

Hi. The obvious reason would be calculated dimension which would be not supported in levels. Note that having field starting with “=“ sign is considered as calculated dimension too…

cheers

[Lech_Miszkiewicz]

Ohh and one more-check if you use conditional show/hide on columns which would disqualify table from levels and in tables would bring table as a whole table tag and not individual columns tags. 
cheers

[Lucas_Gatling]

@JustinDallas see the following KB articles for all unsupported items in Nprinting: https://community.qlik.com/t5/Official-Support-Articles/Qlik-NPrinting-Unsupported-QlikView-Document...

[JustinDallas]

Got it =( .

I assume a Set Analysis measure also will keep the chart from being brought in too right?  I'm considering doing all the calculations in the datamodel to make actual fields in the table instead of using Set Analysis. 

Do you think that's a reasonable workaround?

Thanks for the super-fast response.

[Lech_Miszkiewicz]

Measure is not a problem - only dimensions with = sign. Reason is obvious-levels “cycle” through dimension values (not measure values) when table is in level…

[Lech_Miszkiewicz]

Moving calculations to data model is only necessary if it affects dimension values. I often use set analysis to ensure that levels cycle only through dimension values which return measure i want-or are suppressing values i dont want to see. 

the only scenario where set analysis may cause issues is when selection state caused by filters removes certain values from possible in selection state, but set analysis overwrites it and makes them visible in table-that may not work properly in level then.

[JustinDallas]

You were right, as expected, those equal signs were what was messing everything up.  I had to remove them outside of the expression editor viewed by hitting the fx button.  Thanks a lot Lech!

[Lech_Miszkiewicz]

That is correct - clicking at f(x) causes it to be expression/calculated dimension by default.