Paging metada

[mgranillo]

Can someone tell me how nprinting decides to pull object metadata on paging? As in, what objects can be used for paging and why?

[Lech_Miszkiewicz]

Well,

short answer is:

* Fields (!!! not calculated dimensions !!!)

* Straight Tables - this would be for pages which would require combination of multiple fields you would use as a Page level.

Why - because you can only "cycle through" combinations of values from your application based on those 2 above mentioned entities. Reason? - Page (and similarly Level) "i think" is applied as a filter/selection when report is generated. 

cheers

Lech

[mgranillo]

Straight table is a Qlikview object. Do you know about Sense? Is there a straight table equivalent that behaves the same in Sense? I tested the Sense table chart and Nprinting would pull metadata only if there was 1 dimension in the table. Oddly, my heatmap extension with 2 dimensions pulled in. So I'm left confused as to how it works.

I need the straight table functionality of paging over multiple fields but Sense doesn't have this object. I suppose I have a work around with my heatmap extension but I would still like to know how it works for maintenance purposes.

[Lech_Miszkiewicz · Accepted solution]

Yes it does. "Table Object" is a straight table object equivelent and will work as a Page. Keep in mind what i said about "Calculated dimensions". Make sure that your dimensions in the Qlik Sense Table (aka Straight table as it is not a Pivot Table 🙂 ) does NOT start wit "=" sign, which would make it calculated dimension/expression and disqualify from use in Page/Level.

Also make sure you do not have conditional hide/show on the columns (depending on QS version you are using it might be available). 

cheers

Lech

[mgranillo]

Works perfectly now.  I had equal signs my dimensions. Thanks so much.  Extremely helpful. Qlik Support told me this was not supported functionality.

[Lech_Miszkiewicz]

Awesome - glad i could help!