Nprinting wrong columns order in table with expressions and dimensions

[Anonymous]

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:

1. Add whole table as an object to Nprinting -> then the columns and data order is ok
2. The object in QS must have first listed the dimensions, then expressions -> then no matter the order is in Nprinting report, it still works even though adding the columns one by one into the NP report.

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.

[Lech_Miszkiewicz]

Hi Simona,

this looks like similar topic to this one:

NPrinting Table Excel Template returns the wrong columns after June 2018 Release

lets make Qlik aware of this issue ASAP - log a case.

rpc‌ - is this known issue or registered bug?

cheers

Lech

[Anonymous]

Hi Lech,

yes, it's exactly the same issue, I somehow haven't found it even though I was looking for similar issues, so thank you a lot. I'll comment there.

Thank you

[Ruggero_Piccoli · Accepted solution]

Hi,

Please update to latest version June 2018 and test if the issue appears also with that version.

We fixed similar bugs.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.

[mkas0001]

Hi,

I have the same problem with NP 16.7 and QV 11.20.

[Lech_Miszkiewicz]

What is your qv SR?

[Lech_Miszkiewicz]

By the way, since it is QV and NP16 then it is likely you have some hidden colums or maybe conditional hide show on them which then is not controlled properly when moved to NPrinitng template

[Ruggero_Piccoli]

Hi,

Qlik NPRinting 16.7 is a completely different version than the one in the original post so if you need help please open a different conversation.

I agree with lech_miszkiewicz‌ you could have hidden columns in the source. I suggest also to upgrade to 16.8.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.

[mkas0001]

Thanks a lot. It was good advice

[pwagner]

Hello @Ruggero_Piccoli 

We face this issue in NPrinting 2019 19.19.4.0 again. 

Any idea what to do solve this issue?

Best regards, Patrick