Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
subash29
Contributor III
Contributor III

Npritning update in pixel perfect Report Not working

Hi,

We are using the Pixel perferct report in our project.

We have created some templete based on Qliksense meta data and created some tables and charts using Nprinting objects.

We have created the level in year and created the tables to bind the year dimention data in tables records.

It working fine previously but after we did some change in  qliksense objects  and we have updated the objects in nprinting also.

After those changes the year field not binding in nprinting reports.

we didnt change in datamodel level,but we cant able to find why year data is not rendering in pixel perfect report.

we tried the same object in excel templetate it work fine.

Please provide some suggesion to resolve the reports need to work in pixel perfect.

QS server version is 12+

QNprinting Version is 18.02

1 Reply
Ruggero_Piccoli
Support
Support

Hi,

It is right. You changed the original Qlik Sense objects, so maybe you deleted the columns used in the PixelPerfect templates or similar changes. This caused the un-binding of the Qlik Sense objects and fields from the templates so Qlik NPrinting doesn't know any more where to find the data.

So:

  1. Complete all the updates you need in your connected Qlik Sense apps
  2. Re-generate the caches of all the connections
  3. Open your PixelPerfect templates
  4. Click on the smart tag (the small arrov > in the upper right corner) of all cells that loosed the data bining
  5. Set the Data Binding again by opening its dropdown menu
  6. Do these steps for all fields in all your templates

Best Regards,

Ruggero

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

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.



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 with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.