topic Re: load issue in App Development

load issue

kmswetha — Fri, 06 Jan 2023 13:29:24 GMT

While loading below table with different rows, they are coming up as one after loading. One row is getting over-ridden by other.

Hash key is also same.

load * Inline [

Field A
2896-0003-01
2896-0002-30

]

Output

Any idea why is it happening?

Re: load issue

justISO — Fri, 06 Jan 2023 14:00:26 GMT

Hi, strange, but I believe Qlik is treating such string as date. Maybe try to convert it to text with something like:

load text([Field A]) as [Field A];
load * Inline [
Field A,
2896-0003-01,
2896-0002-30];

Re: load issue

Bill_Britt — Fri, 06 Jan 2023 14:26:03 GMT

Hi,

I think I would contact support with this issue. I loaded your data and when I go in table viewer, I see the same number twice.

Re: load issue

MarcoWedel — Fri, 06 Jan 2023 18:33:27 GMT

one example that confirms this string being interpreted as date:

table1: load *, Date(FieldA,'MM/DD/YYYY') as FieldAdate, Text(FieldA) as FieldAtxt, Num(FieldA) as FieldAnum Inline [ FieldA 2896-0003-01 2896-0002-30 ]

Re: load issue

kmswetha — Mon, 09 Jan 2023 07:04:30 GMT

Though it is date a unique number has to be generated internally while loading right? I've checked for 2022-0002-30 and 2022-0003-01 and they seem to be generating different unique number when converted to data and even if not convert they load.

Re: load issue

Oliver_F — Mon, 09 Jan 2023 11:56:58 GMT

as it was already proven by @MarcoWedel that it is interpretated a date, my assumption is that qlik uses first of march as a substitution for the 30.2. because february has only 28 (or 29) days. Therefore both strings get the same integer/date value.