topic Re: Dual() vs. Date() --> bug or feature?!? in QlikView

Dual() vs. Date() --> bug or feature?!?

Anonymous — Mon, 20 Mar 2017 19:29:50 GMT

Hello community,

here's a simple example:

LET var= Dual('TEST',42814);
LET var2= Date(42814);

LOAD '$(var)' - 5 as FIELD1 AutoGenerate 1;
LOAD $(#var) - 5 as FIELD2 AutoGenerate 1;
LOAD '$(var2)' - 5 as FIELD3 AutoGenerate 1;
LOAD $(#var2) - 5 as FIELD4 AutoGenerate 1;

Why is there a difference between FIELD1 and FIELD3?:

I would expect the same result for FIELD1 and FIELD3 --> either the dual() - value will be passed through or not.

In my eyes this is just inconsequential behaviour...

Any ideas?

(using QV 11.2 SR15)

Re: Dual() vs. Date() --> bug or feature?!?

swuehl — Mon, 20 Mar 2017 19:43:45 GMT

Format the date not the same way as your standard date format, so Qlik can't interpret the text expansion as date in your LOAD.

Assuming you are using german date format as default, try

LET var2= Date(42814,'MM/DD/YYYY');

Re: Dual() vs. Date() --> bug or feature?!?

swuehl — Mon, 20 Mar 2017 19:45:13 GMT

And yes, it's a feature:

Automatic Number Interpretation

Re: Dual() vs. Date() --> bug or feature?!?

Frank_Hartmann — Mon, 20 Mar 2017 19:48:41 GMT

LET var= num(Dual('TEST',42814));

LET var2= Date(42814);

LOAD '$(var)' -5 as FIELD1 AutoGenerate 1;

LOAD $(#var) - 5 as FIELD2 AutoGenerate 1;

LOAD '$(var2)' - 5 as FIELD3 AutoGenerate 1;

LOAD $(#var2) - 5 as FIELD4 AutoGenerate 1;

hope this helps

Re: Dual() vs. Date() --> bug or feature?!?

Anonymous — Mon, 20 Mar 2017 20:18:26 GMT

thank you for your answers.

So I will solve it like that:

LOAD dual('$(var)',$(#var) - 5) as FIELD5 AutoGenerate 1;