Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I'm using the function GetFieldSelections() in nprinting to show the selected filters in my qliksense app. Nprinting is only showing the selected values that contains data. Example: 2 filters period and country: if i select April 2019 for period and country US and Belgium as countries and there is only data for US in April 2019 the nprinting report will only show US. We need to display what is selected in the filters on the nprinting reports. When I use that same function in Qliksense it displays both countries .
It may not be in filter selections for many reasons:
these few are just from top of my head
You have never shown us how you create your NPrinting filter - maybe problem sits there?
I don't use a nprinting filter. It is an nprinting report on demand that is started from the qliksense app and should include the filters that are used in the qliksense app
Ok. Well - you should have said that you are using OnDemand in the first place as filters are passed differently there. That changes completly our conversation.
So in this situation OnDemand extension passes filters to NPrinting as an intersection of all applied filters. That is why you only see in your current selection box only values which are "GREEN" on your filter panes at the time when you generate report. In your case value "INVALID" is actually excluded from selection.
cheers
Lech
sorry that I forgot to mention that it is an on demand report. Is there any solution to show what is selected in nprinting?
well - it will no tbe possible to show that "INVALID" is selected but not available in current selection.
Instead you can change in Qlik Sense the way you present your current selections to only show actually available values.
For example like: Concat(Distinct INFORM_COMP_INFORM_COMP_TYPE, ', ')
Hi,
I did some tests and I always have the same results in the On-Demand generated report and Qlik Sense app.
Best Regards,
Ruggero
Hi Ruggero @Ruggero_Piccoli,
Try testing follwoing scenario:
Create an app which will have a dates and week day names like: Mon,Tue,Wed etc.
Then apply selcetions:
now - for this selection directly in Qlik Sense result of GetCurrentSelections function will be:
However if you run OnDeman report and have GetCurrentSelections NPrinting formula in it it will evaluate differently and it will show:
The reson for it seems to sit in how selections are passed and applied via API.
It would be great to hear your thoughts after this test.
Thanks
Lech
Hello! @Lech_Miszkiewicz ; @geertdeman ; @Ruggero_Piccoli
Just wanted to check-in and see if there is a solution to this problem ? If not, were there any alternate methods for this issue. I am having a very similar use case. Any help / insight would be much appreciated!
Thank you!
Hi,
I did some tests and I confirm that if you insert a GetCurrentSelections() function in a template when you generate the report in Qlik NPrinting you will see the full list of selected values. Instead the same report created via On-Demand will show only the intersection of the filters.
Best Regards,
Ruggero
@geertdeman @Ruggero_Piccoli @Lech_Miszkiewicz Thank you so much for your response!
I just don't want to give up on this ! 😔
Let me explain the objective and some of the options that I tried:
Report users would select a date range + other filters and then generate its corresponding report via NPrinting Ondemand Report Generation within QlikSense.
This works perfectly, but the main objective is we would also want to represent the start date and end date of the date range selected. But unfortunately, as discussed before, it just shows the start date and end date for which there is data.
For e.g., We select the date range in QlikSense as 1/1/2019 - 12/31/2019 for a UserID and generate the corresponding NPrinting report via OnDemand functionality. But, the start date and end date in the NPrinting report shows as 5/1/2019 - 5/30/2019; because there is data only for that date range. Unfortunately, that is by design.
Below are the options that I tried to circumvent this problem.
Ultimately, the user should only select the Date Range ONCE while in QlikSense to generate the NPrinting report via OnDemand, but, obviously that should not be the data islands StartDate and EndDate fields, because every single calculation becomes an unnecessary set analysis and the whole report becomes slow (because now the DateRange field is not filtering the records).
Any insight/direction would be really helpful. Thank you!