Qlik Sense Calculation Condition (Add-Ons --> Data Handling) function interaction with NPrinting
Hallo community,
i've recently added a "Calculation Condition" for each object in all (Qlik Sense-) apps that we have, so the Engine won't re-calculate tons of objects, as soon as i change a filter or switch worksheets.
Now we tried to use those apps for Report-Generation via NPrinting but it doesn't show my straight-tables anymore (although all necessary Filters have been applied). When i remove the Calculation Condition from the objects, it shows my straight tables in the NPrinting Reports though.
Does NPrinting support the feature "Calculation Condition" (under Add-Ons --> Data Handling)?
I did a check and the Calculation Condition are not supported. I open an new feature request.
I suggest you to clone the app and create one only for reporting so you can apply Calculation Condition to the app used by users and remove it from the one for reporting.
Best Regards,
Ruggero
Best Regards, Ruggero --------------------------------------------- When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
is calculation condition supported with QlikView? Asking as it was commonly used to save on calc time when used with NP16. also I know I can test it but I just want to hear whether it is officially supported...
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.
we actually already have seperate apps for reporting - but since each app is used for generating multiple reports and will be re-used for adding more worksheets and objects for future reports (when the datamodel fits the need), it's still annoying.
