Solved: QV showing incorrect values - load. Bug ? - Qlik Community

Report Inappropriate Content · ‎2012-12-04

I have just discovered that in some cases - haven't figured out when and why - QV shows incorrect values. E.g. take an id from another case_id.

Anyone experienced anything similar. Is it a bug ? Is there a fix. I'm still on 8,5.

I enclose an application to clarify.

Report Inappropriate Content · ‎2012-12-04

I'm using QV11 SR2, and at first sight it seems strange indeed... I'll have to think about it for a while to see why it is (if there is a reason at all).

So I think things are not changed in v11SR2

#Edit, when you put the function text() around your fieldnames, the problem is gone...

So the issue is in the fact that it gets converted to numeric/int...

     Load text(Case_id) as Case_id,     (Ref) as Ref inline [
    Case_id, Ref
    6132398, '115154'
    2628159, '2215-0004-12'
    1519326, '26-59-8'
    2931587, '12548'
    6982151, '1515'
];

I cannot really judge whether it is a QV-bug... My opinion would be yes (but perhaps that is too easy). I would say Qlikview should consider the data in the column Ref, and when it does not have only numerical characters, then evaluate it to text and not to numeric/integer

View solution in original post

Report Inappropriate Content · ‎2012-12-04

I'm using QV11 SR2, and at first sight it seems strange indeed... I'll have to think about it for a while to see why it is (if there is a reason at all).

So I think things are not changed in v11SR2

#Edit, when you put the function text() around your fieldnames, the problem is gone...

So the issue is in the fact that it gets converted to numeric/int...

     Load text(Case_id) as Case_id,     (Ref) as Ref inline [
    Case_id, Ref
    6132398, '115154'
    2628159, '2215-0004-12'
    1519326, '26-59-8'
    2931587, '12548'
    6982151, '1515'
];

I cannot really judge whether it is a QV-bug... My opinion would be yes (but perhaps that is too easy). I would say Qlikview should consider the data in the column Ref, and when it does not have only numerical characters, then evaluate it to text and not to numeric/integer

swuehl · ‎2012-12-04

2215-0004-12 is interpreted as April 12, 2215, which has a numeric representation of 115154.

You can call this QV-AI-running-wild a bug, I assume the developers think it works as designed.

Report Inappropriate Content · ‎2012-12-04

Interesting finding (I didn't have an idea where it came from). But in the table-viewer, I see that the field Ref has the tags numeric, Integer and not Date...

So IMO it is at least misleading :-).

swuehl · ‎2012-12-04

I am far from saying this is intuitive or not misleading.

I don't really know how (or based on what actions / informations) QV creates the tags, so I started not to heavily rely on them anyway.

It might seems kind of strange that QV interprets above as a Date even when the date format is set to something different (like in the sample).

I believe QV is always accepting ISO formatted dates (no, not always, try adding date#('2215-04-12') as Date to the INLINE LOAD, it will not parse the value as date, you need to add the format).

So, QV is sometimes accepting ISO formatted dates (even at places you won't expect it to do).

Sometimes I wish QV had an optional switch 'Disable all automatism'...

I think the work around is like you already stated above, use text() around the Ref field name.

Regards,

Stefan

Report Inappropriate Content · ‎2012-12-05

Thank you both for taking the time to think and analyse about this. You were spot on: text() did the trick.

swuehl: good spottet. I hadn't even thought about that.