Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I need some help in Nprinting.
I have 2 issues.
Originally, my clients developped an app with 12 tables.
Each tables contained a bunch of dimensions which were all identical and 2 measures which were almost identical. The only thing that changed was the content of the set analysis.
Thus, in order to simplify everthing, I created 2 master measures which contain set analsysis and the content of the set analylsis will change depending on a variable value which is changed by a button.
For instance, Button 1 set variable value to 1, button 2, value to 2,..
The idea is to have only 1 table and 2 measures to maintain and It works great in qlik sense.
Then in Nprinting, I created 12 filters such as this one:
I tried with and without the evaluate options checked.
I need to create an excel report with 1 sheet per table.
Thus, I called my table 12 times in my report and for each one, I define the filter matching the variable value:
I have 2 problems:
1. It works great for the 1st tables but all the other ones fail
2. In my report, I create a formula ReloadTime() to show the reload time of the QS app.
But ,from the moment, I run the report once, as mentioned before, it fails and then if I try to run it a second time, Nprinting mentions that there is a problem with the formula reloadtime(). This error stops if I reload the masterdata.
Can anyone help me on this?
Thanks
Gerald
Hi @glebret
Right.. I normally try to shorten number of dependencies. In your case there are really 3 levels and I would have just 1 level.
I would simply throw action to set value for vSetAnalysis as:
{<field1 = {'vvvv'}, filed2= {'hhhhhh'}>}
or {<field1 = {'ssss'}, filed3= {'jjjj'}>}
or any other set....
I would just set the required string for set analysis as variable value string (not as expression which evalueates to string!!)
As in if you have a button which changes variable between 1,2,3 etc... instead I would have button which sets {<field1 = {'vvvv'}, filed2= {'hhhhhh'}>} or {<field1 = {'ssss'}, filed3= {'jjjj'}>} etc..
That would be my 1st test... which then in NPrinting would also have variable filters which would set values as: {<field1 = {'vvvv'}, filed2= {'hhhhhh'}>} or {<field1 = {'ssss'}, filed3= {'jjjj'}>} etc..
If that wouldn't work then I would know that something is wrong....
Lastly - i dont mind externalised set analysis but I am unsure about how those work in NPrinting in conjuction with Qlik Master Measures. Strangely NPrinting had issues in the past with Master Measures not working (those issues were later resolved) but given the nature of the issue we experienced it was clear that Master Measures were not handled the same way as regular expressions - details here: https://community.qlik.com/t5/Qlik-NPrinting/Gauge-from-Qlik-sense-into-Nprinting/td-p/1839212
so to sum up:
cheers
HI @glebret
As long as I understand your methodology you just try to re-use the same chart 12 times and run it with 12 different variable filters. Those variable filters should then alter your set analysis hence chart should produce differently filtered data.
That by itself should not be a problem so if you are experiencing issues I would contact support and open support ticket.
Make sure you are on supported version and that you are running compatible configuration of Qlik Sense and NPrinting.
Hi @Lech_Miszkiewicz ,
You perfectly understood the methodology. I will then open a support ticket.
Thanks.
Hi @glebret
Sorry - one more thing you could explain to me: Is there any reason as to why you double expand your variables in your expressions $(=$(=vSetAnalysis))?
I have also seen that you have externalised set analysis outside the Master Measure?
thanks
Lech
Hi Lech,
the $(=$(=vSetAnalysis)) was the only way to make the vSetAnalysis.show the correct result when clicking on the buttons. I tried, without the $, without the =, with and without ''...
Here is how it works:
vxxxx = {<field1 = {'vvvv'}, filed2= {'hhhhhh'}>}
vyyyy= {<field1 = {'ssss'}, filed3= {'jjjj'}>}
.....
Then
vSetAnalysis = If(vMesure =1, vxxxx, If(vMesure=2,vyyyyy...))
And yes, since Qlik released the outter set analysis, I've been using it a lot. It's a big life changer!!!!
But once again, it works like a charm in Qlik Sense and I manage to have the first table working fine.
When I change the sheet orders in Nprinting, the first table always works.
Thanks.
Gerald
Hi @glebret
Right.. I normally try to shorten number of dependencies. In your case there are really 3 levels and I would have just 1 level.
I would simply throw action to set value for vSetAnalysis as:
{<field1 = {'vvvv'}, filed2= {'hhhhhh'}>}
or {<field1 = {'ssss'}, filed3= {'jjjj'}>}
or any other set....
I would just set the required string for set analysis as variable value string (not as expression which evalueates to string!!)
As in if you have a button which changes variable between 1,2,3 etc... instead I would have button which sets {<field1 = {'vvvv'}, filed2= {'hhhhhh'}>} or {<field1 = {'ssss'}, filed3= {'jjjj'}>} etc..
That would be my 1st test... which then in NPrinting would also have variable filters which would set values as: {<field1 = {'vvvv'}, filed2= {'hhhhhh'}>} or {<field1 = {'ssss'}, filed3= {'jjjj'}>} etc..
If that wouldn't work then I would know that something is wrong....
Lastly - i dont mind externalised set analysis but I am unsure about how those work in NPrinting in conjuction with Qlik Master Measures. Strangely NPrinting had issues in the past with Master Measures not working (those issues were later resolved) but given the nature of the issue we experienced it was clear that Master Measures were not handled the same way as regular expressions - details here: https://community.qlik.com/t5/Qlik-NPrinting/Gauge-from-Qlik-sense-into-Nprinting/td-p/1839212
so to sum up:
cheers
Going through your proposition, I did fix the problem.
Indeed, I am not sure whether it was the $(=$(... or the 3 level that caused the problem but I got rid of 1 level and it solved the problem.
Hence, I do use my 12 variables which contain 12 different set analysis, I still have 1 variable called vSetanalysis and my measures are still for instance$(=vSet_analysis) [NB Lignes].
However, i got rid of the variable vMesure and if vMesure =1....
Now my buttons just set the value of vSetanalysis with 1 of the 12 variables.
I also adapted the filter in NPrinting.
Everything works great now.
Thanks for your help.
Cheers
Gerald