topic Re: NPrinting May 2022 version missing CSV option for QlikEntity Reports in Qlik NPrinting

NPrinting May 2022 version missing CSV option for QlikEntity Reports

QlikEnth1 — Fri, 15 Nov 2024 21:39:29 GMT

The recent Qlik NPrinting Version MAY 2022 upgrade is missing some features that lets us to create reports in CSV format for QlikEntity Reports. Please find attached email with Screenshots for your reference. The QlikEntity screenshot was taken after the upgrade was done which should showing all the Output formats. Please let me know if you have any questions.

Re: NPrinting May 2022 version missing CSV option for QlikEntity Reports

David_Friend — Fri, 21 Apr 2023 17:35:21 GMT

@QlikEnth1 I've got your support case you opened for this, also can you post some screenshots here to illustrate the issue?

Re: NPrinting May 2022 version missing CSV option for QlikEntity Reports

Lech_Miszkiewicz — Fri, 21 Apr 2023 17:39:49 GMT

There are no attachments added. Are you sure you use straight table native Qlik Sense object in your report as only those will support that format?

Re: NPrinting May 2022 version missing CSV option for QlikEntity Reports

QlikEnth1 — Fri, 21 Apr 2023 19:18:23 GMT

Attached are the only options we have in dropdown list after Upgraded

Re: NPrinting May 2022 version missing CSV option for QlikEntity Reports

Frank_S — Fri, 21 Apr 2023 21:39:47 GMT

@QlikEnth1

Please note that if you are trying to export an entire sheet you will only have the output formats that you described.

This is also what I have if I try to export an entire sheet entity.

Otherwise, please choose a straight table to see the csv export option as expected.

Results when selecting a chart object (NOT a sheet object). See image below:

Re: NPrinting May 2022 version missing CSV option for QlikEntity Reports

QlikEnth1 — Mon, 24 Apr 2023 13:05:55 GMT

Thanks Frank, i will update accordingly

Re: NPrinting May 2022 version missing CSV option for QlikEntity Reports

QlikEnth1 — Fri, 28 Apr 2023 18:35:19 GMT

Hi,

I Have Updated the Info to Our Internal Team and Issue Seems to be resolved.