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: 
212040
Contributor II
Contributor II

Nprinting report values not matching with qliksense app

I am trying to generate on demand report using nprinting but what I noticed nprinting report values and qlik app values are not matching I tried all options but not able to resolve like checked app id reload metadata object id etc.

Labels (1)
15 Replies
212040
Contributor II
Contributor II
Author

But what I can see is that some values in that column are matching but some values are not matching strange 

Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

In that case it can be matter of selections you are applying to the report when you are generating it. Applied filters are creating intersections of possible values and based on those your app gets filtered. 

Given that your measure has set analysis to ignore selections it may behave different as after applying filter using OnDemand the scope of data used to produce report may change creating different total then the one you have in your Qlik App.

Those kind of issues I usually troubleshoot by creating simple table with data and creating each component of the measure as individual column and then creating simple table extract in NPrinting for testing. Have you done this kind of exercise already? That would help you identify which component of your measure does not work as you expect.

cheers

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
212040
Contributor II
Contributor II
Author

Thanks will try out with this also

212040
Contributor II
Contributor II
Author

Hi I tried with creating measure component separately still with variable replacing the formula no luck 

Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi @212040 

so, have you tried what i suggested previously (as per screenshot below)?

Lech_Miszkiewicz_0-1754567108229.png

 

As I said earlier - the way to troubleshoot things is to break things down to individual pieces and removing any components which can cause issues. I have already told you to remove variable and replace it with $ sign expanded variable (as shown in image above). 

My way of dealing with this would be creating a table with 2 expressions (2 columns).

1 column - expression: Count({<PolicyNo=>} B2BID) 

2  column - expression: $(=Count({<PolicyNo=, Outcome=>} DISTINCT B2BID))

Those 2 expressions are what you are saying are components of the measure which does not calculate properly. Just create object with those 2, create 1 slide report in NPrinting and see what it produces! Can you see what is not working?

By breaking it down to numerator and denominator being in separate columns you should be abble to see what is not working. 

You dont need your denominator to be variable so why do you bother as it can be $ sign expanded expression which yields the same result!

I am sure there is something odd in the way this behaves in your app but I cannot tell you why as I am not there with you, I am not seeing your screen and I am not mindreader so based on the information provided this is all I can suggest. 

I forgot to ask that earlier: Does this app have section access?

cheers

 

 

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

You say:

 

Hi I tried with creating measure component separately still with variable replacing the formula no luck 

You dont need variable for that - so why bother? Just use expression as I suggested earlier!

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.