Using Display Names vs. Logical Names

[bfing]

I have a scenario where I ClearCollect data from a CDS entity so that I can use it locally within the app.  On a given screen, I have a Gallery to view the collection records, a Display Form to see selected record details, and an Edit Form to input/modify child record data of a related entity.  To drive the functionality, rather than using the Gallery.Selected identifier, I'm using a context variable defined as follows:

Gallery.OnSelect = UpdateContext({locCurrentItemRecord:ThisItem})

After setting up the screen and controls referencing Display Names (e.g. locCurrentItemRecord.Name, locCurrentItemRecord.Level, etc.) and getting the screen to function exactly as intended, I began to work elsewhere in the app.  When I came back to this screen, I saw an "Invalid Argument Type" error at each use of the context variable.  Specifically, the identified field name had the red underline and when you hover over it it says "This identifier isn't recognized".  When I changed the Display Name to the Logical Name, the error clears and the screen continues to function as it did previously.

I am curious what is triggering this change in operation of the screen and the previously functioning expressions?  My understanding is that there is mapping that occurs in the background that permits the use of Display Names.  Is this not the case with collections?  Should I proceed, when using collections, to simply reference the Logical Name the first time, so I don't have to go back and change this?

It may be worth noting that I'm supplementing the CDS data on the initial ClearCollect by using the AddColumns.  Thanks in advance.

[Anonymous]

Hi, we also use logical name in our formulas, for example in the below formula we use domainname instead of UserName. Reason is that we import our solution globally and for example in another region database this field is not UserName but its Gebruikersnaam and breaks the app.

Previously after the import in any environment the logical name is still in the formula but recently the behavior changed. After the import we noticed that the formula is updated to the name in the specific environment...

So when we import our solution with domainname in the formula in a US dataverse enviroment it replaces domainname with UserName and for a Dutch dataverse environment it replaces domainname with Gebruikersnaam as shown in the picture.

Not sure why but the new behavior still works, we only need to double check before exporting from our development environment that it still holds the logical names because for some reason its sometimes updated.