An extrovert by nature, Atul has been sharing his opinions and views on various social network platforms. He always had been thinking about having his own platform and here it is. Creative and tech-savvy Atul has a good sense of humor and when he is not programming or writing blogs or traveling, you can find him cooking, Netflixing or sleeping.
Latest posts by Atul Sharma (see all)
- RISE FROM THE ASHES – Sanjib Nandi - November 1, 2021
- साथ में मेरे दोस्त खड़े थे - August 1, 2021
- BenchmarkDotNet: Advanced Features - June 20, 2021
When we create a field in Dynamics CRM, We add Display Name and Name. This article talks about these different names and their use.
1. Display Name –
Display Name as Lable on Form
- This is used to show as a label on the form.
- It can be changed from field definition page anytime.
- It can be also changed from the Form customization.
- Beyond showing as a label, it has no further implication in the backend.
2. Schema Name –
- It is used to create Database table columns.
- These are mentioned while doing REST or oData Queries.
- Used in Early Binding.
- Auto created for the first time but can be changed there only.
- They can’t be changed once they are saved
3. Name –
- They are also known as Logical Name or Attribute Name.
- It comes with all lower case and auto-generated in the backend.
- Used as Attribute name in JavaScript programming, using Xrm.Page object.
- Mostly used with CRM SDK Development.
- This is the unique name of the class or property created in the Web Services Description Language (WSDL).
Name (Schema Name) created and can be changed before Save. Name (Schema Name) created and can NOT be changed after Save.
As you noticed here, Name field mentioned in Pascal Casing (ClientSource) or Camel Casing (bats_ClientSource) automatically converted to all lower case.
Finally, this how it looks like.
Name, Schema Name and Display Name
P.S. – This article is for beginners but the very basic concept of Dynamics 365 we normally ignore and fail to answer when experienced
