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: 
lanlizgu
Creator III
Creator III

NPrinting Preview error

Hi, I am receiving the following error when trying to preview a NPrinting object:

The preview request failed with message: Object zzz of Sense App zzzz failed to render. ERROR: Navigator navigator=qliksense;proxyurl=zzzzz; appid=zzzz; identity=zzzz is stuck and can't be used anymore to resolve requests ---> Corrupt data [11]:Corrupt data(Column names are invalid)

Captura.JPG

This doesn't happen with other objects, so I understand that it is because I am doing something incorrectly with the column names, but I would like to know exactly what.

Thank you,

1 Solution

Accepted Solutions
lanlizgu
Creator III
Creator III
Author

Hi Ruggero,

I found out what the issue was. As I was developing this in another environment, when I migrated the App and reloaded it, I didn't figure out that I was not adding a column (as it was loaded in another layer). Once I migrated also the previous layer to this environment, the issue dissapeared, as the missing column is available now.

View solution in original post

2 Replies
Ruggero_Piccoli
Support
Support

Hi,

Try to regenerate the connection cache and check that all columns used in the template are still available in the source document. Maybe one ore more were deleted or changed the name.

If you are running a recent version you can use the Check Entities button in the ribbon bar to have some suggestions.

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.
lanlizgu
Creator III
Creator III
Author

Hi Ruggero,

I found out what the issue was. As I was developing this in another environment, when I migrated the App and reloaded it, I didn't figure out that I was not adding a column (as it was loaded in another layer). Once I migrated also the previous layer to this environment, the issue dissapeared, as the missing column is available now.