Comments
This feature would help my organization protect data from accidental mistakes. Allowing a developer to modify the default behavior on a page is helpful, but it limits who can use this feature. I believe this should be a configurable setting that is available as a personalization. That would enable each user to turn it on/off as needed for their work or to be used as part of a Profile (Role). Enabling this feature in a Profile (Role) would be how we implement it on our key master data pages.
We've tried to work around this by creating separate views, after creating columns for specific languages, and putting the different language in the view, and then qualifying the view by a specific security role, which is also assigned to a user. However, since the "Name" column is the lookup value, there needs to be a default view for lookup. The security role setup did not impact the view used as the default so even though the security role didn't grant access to the view, somehow we still had access to the view. There is no fallback view in the configuration like with forms that have security roles assigned. Even with java script to switch the view, the "Name" is still the display name. The solution needs to translate the data on the fly based on the user's language and not display the base language.