topic Re: QlikView November 2017 Export to Excel in QlikView

QlikView November 2017 Export to Excel

Anonymous — Tue, 28 Nov 2017 11:08:08 GMT

Hello,

Just updated to QlikView Nomber 2017 release. I try to export dual fields into excel now they import as number and not text.

Do we have any setting to revert to export dual fields as text and not numbers?

Just as background we set some dual fields like Market Name so that we can sort them on the value instead of text.

I know the Easter egg function ExcelExportMixedAsText, It should export mixed values as text, this has now changed...

Best,

Matias Undurraga

Re: QlikView November 2017 Export to Excel

stevedark — Tue, 28 Nov 2017 11:24:28 GMT

Hi Matias,

I remember when the same bug slipped into QlikView some years back, for a service release or two.

Hopefully it will be resolved soon.

The thing that makes it complicated, I guess, is that Date fields are duals, and these should go into Excel as numbers, but every other type of dual you probably want the text to go across. I'm not sure how easy it will be for the developers to tell them apart. As you say though, it was working previously.

You may want to raise a ticket on this one through Qoncierge and point them to this thread, so it can get logged as an issue.

Cheers,
Steve

Re: QlikView November 2017 Export to Excel

Or — Tue, 28 Nov 2017 12:04:09 GMT

I noticed the same thing and reported it to my local Qlik partner already. Odd that this behavior's up again after being dealt with previously, but as you said, they probably already know how to fix it..

Re: QlikView November 2017 Export to Excel

npapapicco — Thu, 30 Nov 2017 18:07:02 GMT

Same issue here, last week I upgraded a customer installation and today they discovered the problem. I have raised a ticket of course. Waiting for a feedback from them.

Nicola

Re: QlikView November 2017 Export to Excel

npapapicco — Fri, 01 Dec 2017 09:29:25 GMT

Qlil support answered to my ticket raised yesterday with the akwnoledgement of the issue and with some workaround

1. This is a known issue for us. We have already created a bug for it: QV-12560, and the fix for this problem will be included in the upcoming 12.20 Service Release 1.

2. As for now, what you can do is:

- export the data to a csv file and then reimport to Excel

- downgrade to 12.10 SR8

Nicola

Re: QlikView November 2017 Export to Excel

stevedark — Fri, 01 Dec 2017 09:33:26 GMT

Thank you for sharing this update Nicola.

Re: QlikView November 2017 Export to Excel

igor-st80 — Fri, 15 Dec 2017 08:59:33 GMT

Before fix this problem, I use Easter egg function SendToExcelLegacyFormat=1 for export to xls instead of xlsx

Re: QlikView November 2017 Export to Excel

Or — Tue, 19 Dec 2017 11:08:42 GMT

Following up, SR1 has been released and the issue appears to have been partially handled.

Dates explicitly formatted as dates in script export correctly.
QlikView-generated dates (e.g. today() ) export correctly.
Dates read directly from a database (e.g. Oracle's SYSDATE) do not export correctly natively, but will export correctly if explicitly formatted as a date in a chart's Number settings.
Explicit Dual() dates (e.g. Dual(Today(), Today()) will not export correctly natively, but will export correctly if explicitly formatted as a date in a chart's Number settings.

So, in summary - if you format all your dates explicitly anyway, you're good to go. Otherwise, you may still encounter issues. I've reported the above to Qlik, so hopefully they'll finish the job on these exports in the next patch.