DateFormat not Obeyed Using Same Alias as Source From Resident Load

The DateFormat number interpretation variable can be used to set the format for date used in the application. It was reported that when a resident load is used and the Set DateFormat is applied to change the format of the date for the new table, the DateFormat change fails to properly adjust the display when the field is given the same alias as the source table for the resident load.

Environment:

• All versions of Qlik Sense

The following script can be used to illustrate this behavior:
SET DateFormat='YYYY-M-D';
DateTable1:
LOAD
date(today()-1, 'YYYY-M-D') as _Yesterday,
RecNo() as Num
autogenerate 1
;

SET DateFormat='M/D/YYYY';
DateTable2:
Noconcatenate
Load
Date(_Yesterday,'M/D/YYYY') as _Yesterday,
Date(_Yesterday,'M/D/YYYY') as _Yesterday_01
Resident DateTable1;

DROP TABLE DateTable1;

Exit Script;

One would expect that both columns in DateTable2 should have the DateFormat which was applied for that load, M/D/YYYY.
The actual result is that the two columns have different date formats. The column with the same alias as the source table does not get the new format applied.

This is working as designed.

This is the intentional and expected behavior with formats of key fields and derivate fields where the fields that are being formatted are not renamed, thus retaining the previous format. Avoid formatted numerical fields as key fields if the resultant field could potentially contain more than one format. In this case, the first format encountered will always be used.

Workaround:

• The workaround for this behavior is to give the columns a new alias which is not the same as the one used in the source table.