Is it possible to configure a custom LOV in a `.client` file so that only the description shows to the user, while the underlying ID/key (like a GUID) is still what actually gets saved to the database?

Q: Is it possible to configure a custom LOV in a `.client` file so that only the description shows to the user, while the underlying ID/key (like a GUID) is still what actually gets saved to the database?

Yes — add the hidekey = [true]; attribute to the LOV definition alongside its description expression; this hides the key/ID from the picker's displayed value while still using it as the value that's actually stored, which is exactly what's needed for LOVs backed by dictionaries with unfriendly keys like GUIDs.

Answer

Yes — add the hidekey = [true]; attribute to the LOV definition alongside its description expression; this hides the key/ID from the picker's displayed value while still using it as the value that's actually stored, which is exactly what's needed for LOVs backed by dictionaries with unfriendly keys like GUIDs.

← Browse Developer Studio, deployment, and upgrades questions