Apply map not working as expected in May 2024 patch 11

[smandar91]

Hi Qlik Team,

I was playing around with basic syntax of Applymap in Qliksense enterprise May 2024 patch 11.

Following codei tried to run :

Map_Account:

//Mapping

LOAD

    Account_Id,

    _Account_Name

    FROM ['$(vPBCRMEntityNew)'GBL_CRM_Account.qvd](qvd);

Test:

Load

applymap('Map_Account',Primary_Account_No)                               as [Account Name]

FROM ['$(vPBCRMEntityNew)'GBL_CRM__Di.qvd](qvd);

Ideally it should fail as mapping syntax is commented, but it works without any error of mapid not found.

Any reason for this unusual behaviour?

[JandreKillianRIC]

Hi @smandar91 

I see what you are saying, Its as if Qlik already "creates" a mapping table based on the table only having 2 columns. The only difference I am noticing is that if you don't use "mapping" prefix the table isn't dropped automatically. 

Regards Jandre

[smandar91]

Okay, does that mean mapping syntax is not needed anymore if i have table with just two columns? Is this new feature I'm not aware of or it's a bug in updated Qlik version? I tried same code in prod environment where Feb 2022, patch 14 is installed its fails with mapid not found error.

[JandreKillianRIC]

Hi @smandar91 

Great question. As mentioned - The Mapping prefix just looks like it would drop the table automatically. Seeing nothing in the documentation. 

Regards Jandre

[Or]

I don't remember seeing this documented (though it may have been), but I think this was changed at some point around late 2023 / early 2024. As @JandreKillianRIC suggested, using ApplyMap will work on a regular Load as long as that table has exactly two fields. The original table will not be dropped. This is the case in Qlik Cloud as well.

[smandar91]

Okay, this is something new to me. I haven't seen this documented anywhere .

[Or · Accepted solution]

Nor have I, but it definitely wasn't the case up to May 2023, and it's definitely the case in May 2024 based on your testing, and it's definitely the case in Cloud now, so we have a pretty good triangulation of this being a stealth change (intentional or otherwise) in late 2023 / early 2024.