ODS use current selections with multiple source connections

[dominicmander]

Hi all, I'm looking for clarification on the following please:

I have a stand-alone on-demand app, let's call it on_demand_request.qvw where users can make a selection in a field (product) and then request the generation of a report. In the request report extension object the 'use current selections' option is checked.

I have a corresponding nprinting nsq containing the task/report which is referenced in the above on demand app. This report uses connections to three different source qvws. I have set up a linked field for product for all three source qvws with 'keep matching values only' set.

My hope was that a user selects a product in the on_demand_request.qvw, clicks the generate report button, and a report is generated with data only for the selected product from all three source qvws. That, at least, is what I took away from this thread‌. However, this only seems to be the case for the first qvw ... objects from the second and third qvws return all data, not the selected product.

Am I missing something here?

(using NP 16.7)

Thanks!

edit: added clarification that 'keep matching values only' is set

[Daniel_Jenkins · Accepted solution]

Hi Dominic,

What you experience is expected behaviour. More information and a possible workaround here: Re: selection not working in nprinting on demand with linked Field

HTH - Daniel.

[dominicmander]

Thanks Daniel,

Perhaps you could just validate the following for me to make sure I have understood correctly exactly what my options are before I try to figure out what to do next ...

Workarounds are:

1. Combine the models into one qvw, then I could use the 'use current selections' option.
2. Create a separate filter for each dimension value in any field I want to use across all three apps and apply these from the on demand app using the 'additional saved filters' option.

Unfortunately neither of these is looking very attractive right now:

1. Each qvw contains a different fact, each with 100s of millions of records. The models are separated to improve front end performance with document chaining between them.
2. Our dimension has nearly 7000 values so (assuming I am understanding the work-around correctly) that would require the creation and maintenance going forward of 7000 filters.

Is there a way to create filters dynamically similar to recipient import maybe? I can't find any information about this.

[dominicmander]

djk‌

Thanks for your earlier response to this question.

I have an additional question to those I asked before ... I'll summarise them all here to make it easier by having everything in one post:

1. Have I understood correctly that my two options are to either (a) combine the separate models into one qvw or (b) create a separate filter for each dimension value in any field I want to use as a filter across all source apps?
2. Is there any way to create filters dynamically similar to recipient import? Might we have some success by using dummy recipients to create the filters we need dynamically?
3. Thinking ahead to a possible upgrade to nP17 down the line, am I correct in my understanding that the separate filters workaround (option b above) could not be migrated because that functionality does not exist in nP17? Is there some equivalent functionality in nP17 that I am not aware of? Or might this be an argument for taking the single model workaround (option a above)?

Thanks again!

[dominicmander]

Hi rpc‌,

djk‌ directed me to a thread that you answered in his response to my question. Any chance you could help me with my follow-up questions above?

Thanks,

Dominic

[Ruggero_Piccoli]

Hi,

About no.2

You can import dummy users from an Excel file with related filters just to create the filters. I have not tested but I suppose that 7.000 filters will slow down the aperture of the .nsq file.

Note that is is not mandatory to import from an Excel, you could create a QlikView chart and import users and filters from it.

About no.3

Qlik NPrinting 17 can import users and filters but only from Excel file at the moment /February 2018). The structure of Excel file is rigid. refer to https://help.qlik.com/en-US/nprinting/February2018/Content/DeployingQVNprinting/Import-Users-Filters...‌.

Qlik NPrinting 17+ has APIs and you can create filters by using them https://help.qlik.com/en-US/nprinting/February2018/APIs/NP+API/index.html, not only by importing from an Excel file. There are not linked fields in Qlik NPrinting 17 but you can create a filter with fields and values from different connections to filters data from different .qvw.

Then you can write a custom software that run an On-Demand request by using APIs with the UUID of the filter related to the product you want the report.

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.

[dominicmander]

Got it. Thanks for getting back to me.