Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
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: 
Mauritz_SA
Partner - Specialist
Partner - Specialist

NPrinting dynamic references to Qlik Sense objects

Hi there experts

Background:

We are in the process of replacing Microsoft SSRS (SQL Server Reporting Services) reports with NPrinting reports. We have many different clients (more than 100) and we have a SQL Server DB for each client (moving to PostgreSQL which is why we need to replace SSRS). We recreate some of these SQL Server tables in a client's DB locally on our server in qvd format, and we then create a 'reporting layer' which is basically just a transformed version of some of those tables which are used in apps - we do this for each DB. We then have Qlik Sense Streams for each client with a list of standard apps for each which reload from the folder containing the data in qvd format for that client.

Question:

We would like to create standard NPrinting reports which can be used by all clients with the standard (Qlik Sense) apps as reference. With my limited knowledge of NPrinting it seems as if we have to create new references to the objects for each report (in the report itself) and we cannot simply reference the Qlik Sense app which is the source for the NPrinting report. In other words, if we reference table/object abcdefgh123 in the report for Client_A and we need to use the same report for Clien_B, we need to replace the reference to abcdefgh123 with (for example) 637hbg78dfg890. Is that correct?

 

For example, in Qlik Sense we could have a table like "Sales for current month" in a standard "Sales" app which is loaded for each client (but it reloads with the specific client's data). If I want to create a Sales Report in NPrinting, would I need to replace the reference to the "Sales for current month" QS table/object every time I want to load the report for a new client? Or is there a way I can just point it to the new client's Sales app (its ID for example)?

 

I know the problem can possibly be solved by creating one Sales app with the data for all the clients and then using filters and/or section access, but this app would simply be too big as a client can easily have more than 10 000 000 rows in their individual Sales app. I guess if there is a way in which I can pass variable's (with the object IDs) into the report that would already help a lot. As I can configure it once and not have to rely on developers to replace object IDs in the reports themselves.

Let my know if anything is unclear and I will gladly elaborate.

Any help or suggestions would be greatly appreciated.

Regards,

Mauritz

Labels (1)
3 Replies
Eva_B
Employee
Employee

Hello Mauritz,

I wanted to see if I could assist as I have seen no one answered your question.

Qlik NPrinting can have a Report with Multiple Connections. The process on how to do this is found here:

https://help.qlik.com/en-US/nprinting/February2019/Content/NPrinting/MultiDocument/Excel-Reports-wit...

Would this assist with what you are trying to achieve? 

Do you plan on using the latest version of Qlik NPrinting? 

Regards,

Eva

Mauritz_SA
Partner - Specialist
Partner - Specialist
Author

Hi Eva

Thank you for the reply. No, I wasn't able to find a solution. From what I have read, it seems like my requirement cannot be addressed by NPrinting. We are not currently busy with NPrinting (focusing on content in Qlik Sense first), but I will keep this thread open for when we start working with NPrinting again closer to the end of the year.

Regards,

Mauritz

Ruggero_Piccoli
Support
Support

Hi,

Maybe this article could help you https://community.qlik.com/t5/Qlik-NPrinting-Documents/Dynamic-Links-in-Qlik-NPrinting-Reports-to-Se...

Best Regards,

Ruggero



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.