NPrinting ERROR: Not a legal OleAut date

[magnus_pm_olsso]

I am experiencing a very strange error when trying to build an NPrinting Excel report. I am getting the attached error message (Not a legal OleAut date).

The absolutely strangest thing is that the error seems to be dependent on the contents of the table in the Qlik Sense app. Using the exact same report design (same expression) I can get the report to run. All is the same, just changing the underlying App script to get other content.

In this case it is an inventory report, if I just change the app script to display another warehouse everything runs.

I am completely lost and cannot fins a workaround. I have even tried to build a whole new app but as soon as I try to display this certain warehouse info I get the error.

Any help is appreciated...

Thanks

Magnus

[balabhaskarqlik]

May be when loading data from Data source, try like this: change the Date format in qlik sense.

Table:

Load Date,Name;

SQL

Select

     to_char(Date,'DD/MM/YYYY') as Date,

     Name

From ABC;

[magnus_pm_olsso]

Thanks for the hint, unfortunately the app or object doesn't even contain any type of date...

[magnus_pm_olsso]

Some further information on this issue. It seems like it has to do with a numeric field called "QtyOnhand". If I remove this field from the report, it runs without issues.

As I said, there are no dates at all in the report so the error is EXTREMELY strange. Any help would be so appreciated, I am getting nowhere with this.

[jfkinspari]

Hi Magnus

Did you find the reason for the error?

I'm also seeing it for a table object.

[iam_hari]

Hi Magnus,

Might sound a bit strange...but here is what worked for me.

In my case i had the same error, 1 dimension and 18 measures in a straight table.
I replaced the dimension with another random one, and,,,,, it worked again.
So in the end i made a duplicate from the original dimension and renamed it slightly and it works....

Not the cleanest solution but it worked for me.

good luck!

version: Qlik Sense Enterprise & Qlik Nprinting September 2018

[czm · Accepted solution]

Hi Magnus,

unfortunately this is a bug of Qlik NPrinting September 2018 (also the Technical Preview is affected) that could arise with some localization settings (a double number could be wrongly interpreted as a Date, depending on the digit separator used). We are going to release a fix for this issue in Qlik NPrinting September SR2 (and it will be present as well in upcoming Qlik NPrinting November 2018).

Best regards
Carlo

[tversweyveld]

Hi,

Do you know when SR2 will be released?

Thanks!

[czm]

Hi,

I don't have any date to share at the moment unfortunately, but I suppose (just a personal educated guess) it will be available within the end of next week, depending on if we will address also another issue with it or not.

Thanks
Carlo

[jorgecelis]

Hello,

The same problem, a simple solution that I found is in the graphical layer of Qlik Sense, go  to the graph that is failing, next go to each measure, and go to the "Number Formating" option, and select "Money" (all the measures that have the graph), then go to Nprinting and update the cache of the application that is failing, if the report is make from Pixelperfect should generate without any problem, if the report is in Excel then we go to edit the report, next select object table and deactivate the flag "keep source Formats", then apply the format to each measure as required, after this should be generated without any problem.