Remember that NPrinting is a static reporting tool which means that you build template and NPrinting is producing report based on the template (say your report has column A,B,C,D)
What you are doing? You are taking of from your static template one of the columns (For example column D), so NPrinting is throwing an error as it is looking for it.
To summerize - what you are doing will not work in NPrinting!
As a alternative you can do few things:
- Use one column which will be always ON (there will not be a condition on "Conditional" for expression) and tailor your condition in Label and Expression itself
- Create another table in QlikView which will have alternate expression (also without conditions) and create another NPrinting report for it
Now down to your question about error analyzing?
Well - If you build reports accordiung to all NPrinting rules and limitation you will not have errors and you will not have to analyse them. There is not a tool or library of errora vailable unfortunately as mostly errors are specific to environment where your NPrinting is running. There is help document which handles some of the generic errors and expalins them: https://help.qlik.com/en-US/nprinting/June2017/Content/Troubleshooting/Troubleshooting.htm
NPrinting is not a tool which you can learn on your own mistakes (unless you have lots of time and passion). You really need to know what you are doing or get somebody who knows to do it for you! To building NPrinting reports you need to have very good knowledge of QlikVIew development and NPrinting development as very often you have to tailor your Qlik application to achieve expected effect in NPrinting.
Your example is a great example where you were not aware that conditional hide/show for measure is not supported option in NPrinting.
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 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.
you can go through ALL topics here to start with:
regarding NP17 i learned everything from official help document. It just takes time to go through everything.
I am not aware of any source of such information. There are some top level information in help document.
Unsupported QlikView documents
Before you create a connection to a QlikView document, ensure that the QlikView document does not use any of the following:
- alternate states
- sheet and document triggers
- Always one selected list box property
Qlik NPrinting cannot modify or remove these options. As a result, Qlik NPrinting may not have access to the enitre dataset of the connected QlikView document during the cache generation process, and while generating reports.QlikView documents that use these features, are not supported by Qlik NPrinting.If you want use QlikView documents with these unsupported features, do the following:
What i can list is that following are not supported:
- triggers - they may work (i used them in NP16 but i do not recommend them
- actions - as above
- hide/show (conditional) of object , dimension and measure - that is understandable once you think of it
- alternate states - not visible
- horizontal in Straight table (it will not apply horizontal view)
- dimension limits (i found it unpredictable)
Rest is just experience with report templates in general (not only Qlik) but for example crystal report and knowledge from training.
I always say that NPrinitng requires a lot more knowledge than QlikView or Qlik Sense as you need to understand source and reporting tool at the same time.