“You say ‘Tomato’, I say ‘Tomato’ ” …a phrase better sung than read. No matter what label you wrap around a can of tomato soup – it’s still a can of tomato soup. In D365, buttons and headers have labels. The flexibility of having labels allows D365 to be useable in 46 different languages (including 9 types of English!). All the buttons are the same, but each has a set of language-specific labels. Custom labels can also be created through personalizations, then distributed to individuals or groups of users through saved views.
Personalize Labels
Right click on the desired button or header and select Personalize.
The label name will appear in the white field of the personalize box.
This text is editable, edits will change the label presented to the user.
These personalizations can be saved as a view (note the asterisk after “Standard view” in the last image) and the view can then be used individually or published to other users as desired.
Is This a Good Idea?
Well, maybe.
Without personalizations, label changes are a development task. A developer has to update the label file. That code has to get promoted up to the production environment. These changes then affect all system users of that language Want a label for only some users of that language? – just create a 10th version of English…then have that subset of users change their language preference. Personalizations is clearly a lighter touch for changing the name of a button.
But what is the purpose of a language? Common language facilitates communication. When I point to a can and tell you “tomato soup”, it’s only helpful if you also know it as “tomato soup” (Gazpacho…What’s that?). If sub-groups start referring to something by a new name, it can be difficult to talk about it across the whole organization – or describe to support technicians.
If Bob wants to rename the “Adjust transactions” button to “Bob’s Oh-no Button,” and have that on his own view…good news! That functionality exists.
Bob will have trouble describing “his” button to other members of that organization that know it as “Adjust transactions” in the standard view.
Clicking Bob’s Oh-no Button will still take Bob to the same Adjustments form (remember, this is the same button for everyone, only being viewed with a different label).
However, if accommodating a special request like this can facilitate change management, or win Bob as a champion of D365 throughout his organization, the exercise might be worthwhile.
So, Maybe.
iamJoshKnox 
Pingback: Create a New Field – Personalization | D365 Platform | iamJoshKnox