Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi!
We have a September Nprinting version and recently updated to April Qlik Sense version. Until the upgrade, all the Excel Nprinting reports were ok. After the upgrade we have an issue with columns order.
The object in QS, on which the report is based is a straight table with dimensions and measures. However, those are in "random" order, meaning we have couple of dimenstions first, then couple of measures, then again dimensions, measures etc - not having firstly all dimensions, then all measures. E g. columns like:
Country | Number of inhabitants | GDP | Capital | Currency | Number of cities | Number of unemployed people |
---|---|---|---|---|---|---|
Dimension | Measure | Measure | Dimension | Dimension | Measure | Measure |
Then the object in NP is also a straight table, created from the columns of the above object (it's not added as a whole table object but column by column, because of different color formating needed etc.).
E.g the Nprinting template looks like is:
Country | Number of inhabitants | Capital | Number of cities |
---|---|---|---|
<Country> | <Sum(Nr_of_I)> | <Capital> | <Count(City)> |
The columns in the output excel report are completely mixed, having the correct header, but the information under is completely mixed, eg.:
Country | Number of inhabitants | Capital | Number of cities |
---|---|---|---|
France | Paris | 65 233 271 | 926 |
The solutions we have so far are:
BUT, the Nprinting environment we have is quite a big one (there is both a lot of reports to use the solution 1) -> we would need to adjust a lot of templates, and a lot of objects to use the solution 2)-> we would need to adjust a lot of object, then update the objects in NP templates).
Does anybody have any ideas why is this happening and maybe another solution? Thank you in advance.
Hi,
I suggest to create a new conversation because it is a new and different problem. Please post also some screenshots so we can better understand the problem.
Check that the source table has hide columns or conditionally displayed one or calculated etc.
Best Regards,
Ruggero