Unicode Character support in QlikEntity Nprinting report

[Aditya_Chitale]

Hi All,

I am trying to create a qlikentity nprinting report and setting the format to  CSV. But, in my qlik sense table object, some field headers have Unicode characters in their names. One of the headers is "Product – Delivery". Here the hyphen symbol differs from normal hyphen. (Normal: " - "   Special: " – "). 

In such cases, Nprinting randomly evaluates this symbol and shows garbage values in place of that. 

Any way to bypass this ? I tried using chr(8211) in QlikSense table heading but its showing garbage values again in output.

Regards,

Aditya

[Frank_S]

@Aditya_Chitale

Although there are no stated limitations, it is possible that you have encountered one.

• https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/QlikViewEntityReports/Create-Entity-...
• https://help.qlik.com/en-US/nprinting/Content/NPrinting/DistributionSchedulesAutomation/Report-outpu...

If you can provide an example file I can perform some tests.

For example, just export your Qlik Sense straight table as an MS Excel workbook and attached it here. 

*Redact/scramble the data if needed before sharing it publicly.*

Just need the header/column information and a couple of rows.

In the meantime, I suppose you can create a dedicated QVF for reporting purposes and remove the special chars from the header information in the load script so that there are no special chars in the column/headers.

ps: I am presuming you are running a currently supported version of NPrinting.

Kind regards...

[Aditya_Chitale]

Hi @Frank_S ,

Please find attached excel file. Refer column BP (Tax Code – Deliver). 

Nprinting version: May 2021 SR2.

QlikSense version: May 2021 Patch 9.

The character is visible in QlikSense table chart but evaluates as garbage value in Nprinting QlikEntity CSV report.

Regards,

Aditya

[Frank_S]

I've performed the test, reproduce what you are seeing and suggest as the quickest turnaround fix, that you update your source data so it is consistently using the standard (-) hyphen rather than the elongated hyphen ( – ) found in your source data as seen below. No issues if using the former but you do have issues when using the latter. I suspect there is no quick R&D fix for this so suggest using the workaround suggested here.

-

– 

The headers with the thinner hyphen work as designed as seen in the example below

Kind regards...

[Aditya_Chitale]

Hi @Frank_S 

Thanks for your reply, but I cannot use the normal hyphen as we are using this csv output to load data into other software. The software rejects the report as it finds the header different.

Regards,

Aditya

[Frank_S]

In that case I would suggest perhaps checking out this community forum discussion as there is a solution there using the load script editor.

It's a qlikview example but you should be able to accomplish the same with Qlik Sense.

https://community.qlik.com/t5/QlikView-App-Dev/Export-objects-to-CSV-using-macros-in-Load-script/td-...

If R&D comes back with any other ideas, I'll let you know here. (they are in Italy and most appear to be off this week due to vacations and national holidays.

Kind regards...

[Frank_S · Accepted solution]

Ok so the csv generated by NPrinting can be converted in excel to a suitable format.

For example 

• Open  blank excel workbook
• Go to the data tab
• Import from text or csv button

• Close and reload

The headers will appear as expected.
This was the suggestion from R&D and I hope it help you. I've tested with the output above and it works.

So if you are opening the csv with MS excel as I was, then you need to take this extra step to convert the headers. 

Kind regards...

[Frank_S]

https://community.qlik.com/t5/Official-Support-Articles/NPrinting-CSV-Qlik-Entity-Report-Headers-Con...