NPrinting - Section Access and On-demand Reports troubleshooting

[StefanE]

Hello Everyone,

I've got a question regarding Nprinting and the use of Section Access in On-Demand reports:

I tried to roll out an On-demand report where the (working) section access of the Qlik Sense App should be applied. It works for me, but not for "regular" users.

I checked if section access works, activated the button in connections,  checked if users are set up in Nprinting with a valid domain account, gave them permission to create On-demand reports in NPrinting security roles.

Generating reports works for regular users when section access is not applied in Nprinting connections. As soon as I activate it, "Request failed" appears for them. 

I have no clue what I could've missed when setting it up. If anyone has an idea or a checklist, let me know. 

Thank you very much and kind regards

Stefan

[StefanE · Accepted solution]

Problem solved, it seems:

So what I did next was, I set up a NPrinting publish task with the report and got this warning message:

Failed generation of report 6ef64bab-9122-4bd7-a732-73262d7dab1c for user 86ed6958-c631-455c-849f-762dc68842ab. ERROR: Exception during content resolution while processing request with id 61d979f8-542b-4f37-a15c-d97128365762. Check Engine logs for details. ERROR: The object O\MHqN is not present in the Sense App

Of course, the object is present in the App, but only in my sheet collection. I simply published the sheets containing the objects used for the NPrinting on-demand report, so the other users can "see" the objects too, and now it works for "regular" i.e. non admin users.

[Frank_S · Accepted solution]

That is correct.
It is required to use published app (and app objects) where section access is concerned.

https://help.qlik.com/en-US/nprinting/May2023/Content/NPrinting/DeployingQVNprinting/Section-access.... 

Connecting to Qlik Sense apps with section access

Requirements

The Qlik Sense app must be published. For more information, see Publishing.

All report recipients must have permission to access the Qlik Sense app.

Section access must be configured accurately in the load script.

[StefanE]

Hi Frank, 

The app was published, of course. The requirement should specify more clearly, that the objects used must be published in the community. For me, publishing a sheet within an app is a separate requirement than publishing an app. Anyways, it now works and thanks for your reply!

[Frank_S]

Exactly @StefanE 
I am getting the documentation fixed.

Cheers!

[StefanE]

Thank you very much, Frank!

Kind regards

Stefan

[Frank_S]

My pleasure @StefanE 

Have a great weekend!

[Lech_Miszkiewicz]

Hi @StefanE 

I am glad you found a solution however that should be a lesson to everyone that building NPrinting reports based of personal or community sheets is simply "big NO" and bad practice. Just as minimum standard you should always build your reports based on Approved/Base sheets. That way when migrating apps, exporting & importing etc you will not loose content which your report is based on. Also people come and go - often when someone leave company such persons personal sheets are deleted. 

I can carry on giving you examples of what else it can break but that is not my point - the point is to always follow good standards when developing. 

Now - as in your case there is nothing wrong preparing everything in your personal sheet, however production deployment should be based on approved sheets.

cheers