Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I'm using NPrinting May 2021 SR3 and Sense Nov 2021. I have one Level in a PixelPerfect report, and my dates appear as numbers, not dates, even though they are formatted with Date() in Sense. This post discusses a similar problem:
But the two solutions discussed there do not work for me. (Wrapping my date with Text() in Sense, and trying the 'Before Print' script in NPrinting, both cause the date to not appear at all in PixelPerfect.)
Thanks for any advice, and Happy New Year!
Hi,
I guess this topic became now not focused on "date" not showing but general concepts of how to build pixel perfect reports.
In your case you should add your table not to "Tables" but as a SubLevel: https://help.qlik.com/en-US/nprinting/May2021/Content/NPrinting/PixelPerfectReports/Add-Totals-Subto...
Here again you would need to revisit your table as you still have calculated dimensions in it and :
So fixing things like First Name &' '& Last name or Future Appointment date in script would be first step. Maybe you have added those as a measures but they are simply naked field references and work like dimensions. I do not see other fields as your screenshot only shows few so I cannot comment on others.
Once you manage to add your object to sublevel then I suggest you go through a topic on how to add it to your page as detailed report which is also described in link I have provided above.
Summary:
Working with Pixel Perfect reports can be difficult if you are just starting learning it. If you are in this position when you just start learning it I suggest to invest time to go through whole PixelPerfect section of NPrinting help which has tutorials and allow you to understand most of general concepts.
I also encourage you to go through whole section of youtube pixel perfect video tutorials here:
https://www.youtube.com/playlist?list=PLkRFvjyuHFvLeIaA9N5qyQBEBSjhDEMl9
cheers
Lech
Hi @Lauri
you are saying that when you load your date in data load script and you create dedicated field for date to be represented as text by using something like:
still does not work for you?
That is very strange as effectively we are creating text field -like any other text field you have in your data model and it should just appear.
Unless you are trying to do calculated dimension on the chart by adding an expression instead of field. That obviously has limitations as described here as not supported in help document:
cheers
Lech
Thank you, Lech, that's helpful. My dates are calculated measures in Sense (e.g., =date(max({<Condition={1}>}GivenDate)) ). They work fine in NPrinting Word and Excel reports, but not PixelPerfect. I will stick with Word. Too bad, because I love the additional functionality in PixelPerfect!
Hi @Lauri
If your dates are set in Qlik Sense table as measures and have format like :
Text(date(max({<Condition={1}>}GivenDate)))
then it should all work ok.
I just tested it and it worked:
Qlik Sense Table:
Nprinting Template:
Result:
So yeah - I am not sure what you are doing wrong that it does not work for you, but as a solution it definitely works.
by the way - have you regenerated metadata and re-added object in NPrinting template after you changed your column to Text()?
cheers
Lech
This is interesting... Yes, I regenerated the metadata and re-added the table in the PixelPerfect template. But things look a little different for me than in your screenshot:
My goal is to create a PDF with one page per PatientID, so I created that PatientID Level. The date field that shows up blank is the last one in my screenshot (wrapped in Text()).
Am I supposed to use fields under my PatientID_Level instead of adding a table object and then dragging fields from the table onto the template? Problem is, I don't see how to add my calculated measure as a field under "PatientID_Level" the way you have additional fields under "UmZMh_Level".
Thank you for your help.
Hi,
I guess this topic became now not focused on "date" not showing but general concepts of how to build pixel perfect reports.
In your case you should add your table not to "Tables" but as a SubLevel: https://help.qlik.com/en-US/nprinting/May2021/Content/NPrinting/PixelPerfectReports/Add-Totals-Subto...
Here again you would need to revisit your table as you still have calculated dimensions in it and :
So fixing things like First Name &' '& Last name or Future Appointment date in script would be first step. Maybe you have added those as a measures but they are simply naked field references and work like dimensions. I do not see other fields as your screenshot only shows few so I cannot comment on others.
Once you manage to add your object to sublevel then I suggest you go through a topic on how to add it to your page as detailed report which is also described in link I have provided above.
Summary:
Working with Pixel Perfect reports can be difficult if you are just starting learning it. If you are in this position when you just start learning it I suggest to invest time to go through whole PixelPerfect section of NPrinting help which has tutorials and allow you to understand most of general concepts.
I also encourage you to go through whole section of youtube pixel perfect video tutorials here:
https://www.youtube.com/playlist?list=PLkRFvjyuHFvLeIaA9N5qyQBEBSjhDEMl9
cheers
Lech
Many thanks for that guidance, @Lech_Miszkiewicz . I was definitely missing some basic NPrinting concepts about PixelPerfect. I should be able to calculate everything in the Sense load script to make it work.
As a side note, I created a straight table in Sense with just fields (no calculated dimensions) and I was able to add it to PatientID_Level. Then I tried adding the same measure as you did -- Text(Date(Today())) -- and I can no longer add the table to PatientID_Level (it no longer appears in the "Select Levels" popup). So I must still be doing something wrong, but since I will calculate everything in the load, I should be OK. Just curious if you see my error.
I can't show you the "Patient" column because of real names but here are the others:
Hi,
no - I cannot see anything obvious so I am not sure whats wrong there. Note, that having "=" sign in front of dimension/field name will be treated like calculated dimension so make sure there are none in your table.