Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
after updating to NPrinitng June 2019 (19.19.4.0) we have the issue that NPrinting is mixing up header and values of columns of QlikView tables.
In QlikView the order of columns of the straigt table is:
... (dim) - Betrag (calc) - KOAGR (dim) - KOAGRBez (dim)
There are no hidden columns in QlikView.
In NPrinting we had the same order, but NPrinting mixes the header and values. The values of KOAGR are in colum Betrag. And the values of Betrag are in KOAGRBez. Here a short example:
Betrag | KOAGR | KOAGRBez |
09 | Betriebsaufwand | -7.390 |
09 | Betriebsaufwand | -7.385 |
09 | Betriebsaufwand | -7.385 |
09 | Betriebsaufwand | -7.385 |
10 | Personalaufwand | -88.047 |
10 | Personalaufwand | -87.954 |
Do you have an idea how to solve this situation?
Thank you, reagards. Patrick
Hi @pwagner
Please note that if columns are manually shift in the QVW itself by dragging fields to different locations, this would cause the issue that you are reporting. ie: shift click on a column and drag it to a different position/column location.
In this case I would recommend that you:
Try the preview again...if it doesn't work and Ruggero's suggestion also doesn't work I suggest starting a support ticket as well.
Kind regards...
Hi,
Try to:
- install QlikView 12.20 or older
- use the table tag instead of column tags
- open a support ticket
Best Regards,
Ruggero
Hi @pwagner
Please note that if columns are manually shift in the QVW itself by dragging fields to different locations, this would cause the issue that you are reporting. ie: shift click on a column and drag it to a different position/column location.
In this case I would recommend that you:
Try the preview again...if it doesn't work and Ruggero's suggestion also doesn't work I suggest starting a support ticket as well.
Kind regards...
Hello Frank,
thank you, your solution/workaround works.
Maybe you put this issue on the 'for development'-bucket list.
Best regards, Patrick
I will mention this to R&D again. However, this is a long running limitation which begins from QlikView where NPrinting is limited to using the originally cached results/default QVW properties. So without a fundamental change to the QV desktop coding, this most likely won't change for the foreseeable future. So following the steps I mentioned will be necessary at this point...sorry I couldn't give you better news on this.
This is not an issue with Qlik Sense From April 2019 an later releases by the way (fyi for Qlik Sense users).
Kind regards...