topic Re: Cycles with Multiple Connections in Qlik NPrinting

Cycles with Multiple Connections

lwestmaas — Tue, 09 Nov 2021 22:16:15 GMT

Hello,

We are having an issue with an NPrinting application that needs to refer to an ID number that exists in multiple Qlik Sense applications connected to the NPrinting application.

Examples:

Terminology:
- Qlik Apps: Qlik App A, Qlik App B
- Connections: Connection A, Connection B
- Units: Building 1, Building 2 identified by [Building Number]
Example 1
- Setup: Cycle through [Building Number] in Connection A, no cycle in Connection B
- Result: Two reports, one for each [Building Number].
  - Report 1: Building 1 data from Qlik App A, but data from Qlik App B reflects the entire model with no filters
  - Report 2: Building 2 data from Qlik App A, but data from Qlik App B reflects the entire model with no filters
Example 2:
- Setup: Cycle through [Building Number] in both Connection A and Connection B
- Result: Four reports.
  - Report 1: Building 1 data from both App A and App B (good)
  - Report 2: Building 1 data from App A, Building 2 data from App B (bad)
  - Report 3: Building 2 data from App A, Building 1 data from App B (bad)
  - Report 4: Building 2 data from both App A and App B (good)

Obviously what we want is for only one Building's data to be present in any given report.

So far the best solution we've come up with is to create the reports separately and combine them with python after the fact. (There are too many to do manually.)

Is there a way to force Connection B to respect the [Building Number] being cycled through in Connection A? Perhaps by building a variable into Qlik App B?

This post from December 2019 indicates this is not possible, but hoping against hope that there has been a change in status since then.

Thank you in advance!

Re: Cycles with Multiple Connections

Lech_Miszkiewicz — Tue, 09 Nov 2021 22:39:08 GMT

Hi,

No, this is not possible.

You will not be able to use: Cycles, Levels or Pages which use field(s) from 2 different connections in any logical way as there is not "Linked Fields" feature in NPrinting: https://help.qlik.com/en-US/nprinting/May2021/Content/NPrinting/Migrate/Before-you-migrate.htm

Unfortunately this very much needed and useful feature will not be developed as idea was declined (due to technical reasons... which i think is weird given that we live in 21 century, but anyway)

https://community.qlik.com/t5/Suggest-an-Idea/Generate-a-Report-from-Qlik-Sense-App-A-Filtered-based-from-Qlik/idi-p/1677485

For now my advice is to create single Qlik Sense app which will support data from both connections.

In regards to your suggestion to use 3rd party tools to merge reports - I can only say that there you can only rely on your own skills and since it is not NPrinting feature I dont want to comment on it.

Re: Cycles with Multiple Connections

lwestmaas — Wed, 10 Nov 2021 15:14:22 GMT

Thanks for the response. That's what I feared.

To any Qlik employees reading, this capability is highly desired as without it the ability to use multiple connections in the same NPrinting app is severely limited - without it, the extremely useful cycling function is basically pointless in apps using multiple connections.

Re: Cycles with Multiple Connections

Ruggero_Piccoli — Wed, 10 Nov 2021 15:47:20 GMT

Hi,

In the Ideation community there is the official answer about Linked Fields https://community.qlik.com/t5/Suggest-an-Idea/Generate-a-Report-from-Qlik-Sense-App-A-Filtered-based-from-Qlik/idi-p/1677485 from the product manager.

Best Regards,

Ruggero

Re: Cycles with Multiple Connections

jonvitale — Wed, 10 Nov 2021 16:59:47 GMT

The idea that it "can't be done" is such an incredible cop-out. Of course it can be done, if there is will to do it. Well, if anyone asks me to recommend NPrinting, I will say, "I don't think they are putting any effort into the product, so I wouldn't recommend using it."

Re: Cycles with Multiple Connections

Ruggero_Piccoli — Thu, 11 Nov 2021 10:20:09 GMT

Hi,

There are technical reasons, explained in the anwer under the idea, why it cannot be implemented. As per @Lech_Miszkiewicz the solution is to create a single app or document with all data. We also suggest to create apps only for reporting so the suggestion is to create an app only for reporting with all data needed.

Best Regards,

Ruggero