Not all objects available for levels in NPrinting 17

[nathan_beene]

Hello - we are using NPrinting 17.4 along with Qlik Sense June Release and are running into an issue when trying to create a pixel perfect report with levels.  The issue is that not all objects are available to be added as levels.  All field look to be available, but not all tables are.  Is there something special we need to do to make a table object eligible to be used as a level?  The same table is eligible to be added in as a table, just not added in as a level.

[Ruggero_Piccoli]

Hello Nathan,

Not all object types can be added at all nodes. For example, you can check the list of objects that you can add at the Images node and compare it with the list of objects you can add to the Levels node. Images node has a longer list.

Qlik NPrinting Designer will show you only the objects you can add to a specific node. If you cannot see an object it means that it is not supported by the selected node.

To the Levels node you can add fields (F), straight tables (CH) and table boxes (TB).

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

[kdmarkee]

Ruggero -

I'm wondering if you have any info on this related situation.  I have a QV straight chart that has a Calculated Dimension field like this that is joining 2 keys together to make a "chart" key that I can use for an NPrinting level:

=[field01] & [field02]

However, when in NP Designer, this calculated dimension field is not available as a selectable field under Levels, so I am forced to add this field in my script instead.  Is this by design?  Does NP dislike certain calculated dimensions "make ups"?  Thanks.

[Lech_Miszkiewicz · Accepted solution]

Hi Kris,

If you think about calculated dimensions they can change every time user is making a selection. Level property is making a selection therefore calculated dimension cannot cycle through it as the next value in the cycle cannot be calculated.

That was a case also in all previous versions of NPrinitng (also v16).

I strongly suggest not to use any calculated dimensions (even those where you only change the display format; like =Date(Field, 'YY-MM-DD')

regards

Lech

[kdmarkee]

Thanks for replying, appreciate it.

[AxelZ]

Hi, 

How would you implement these calculated fields in tables then?
Would you do it in the script before ?

Thanks,

Axel

[David_Friend]

@AxelZ this is a really old thread, you may be better off starting a new/fresh one...and yes its generally better to move calculated dimensions out to the load script, also helps with performance 🙂