Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QlikView decides to consolidate wrong data? bug??!

I have two records:

2013-06-20 00:00:00.0000001733465
2013-08-06 00:00:00.000R001733465

When I want to show this in Qlikview Pivot or even just a normal List box, it just shows 0001733465!

When I show the dates it shows THE SAME NUMBER FOR BOTH DATES

WTF is going on? My boss just asked me if we can trust my data, and my data is fine, QlikView is screwing around and this is a serious issue!

Labels (1)
13 Replies
jonathandienst
Partner - Champion III
Partner - Champion III

By the way, QV will have correctly loaded two rows, so Count(CALLNBR) should be two and Sum(CALLNBR) will be the same of the two.

Jonathan

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
Miguel_Angel_Baeyens

Yes, that's pretty much it.

The variables at the beginning of the script tells QlikView how to load locale settings for dates, numbers and currency. In my case, although I'm Spanish, but my OS is in American English, MoneyFormat reads:

SET MoneyFormat='$#,##0.00;($#,##0.00)';

You can see the differences in the attached QVW above.

Moreover, if you change the load order, as both are numeric values, QlikView will show whatever comes first: the value starting in "0" or the one starting by "R".

So it was not QlikView messing anything, after all...

Miguel

Not applicable
Author

The R has nothing to do with currency, but I won't be surprised if this is why Qlikview is acting strange, let me check this

Not applicable
Author

I could only mark 2 answers as helpful, but this was also helpful. Thank you!