Nme vs Developer name - which should be used for record type?
What is best practice for working with RecordType in Apex (using DeveloperName)? Why should I use SOQL with DeveloperName if I can do it without query using regular name:
Schema.SObjectType.Account.getRecordTypeInfosByName().get('xxx').getRecordTypeId();
vs
[SELECT Id FROM RecordType WHERE DeveloperName ='xxx'].Id;
Both Name and DeveloperName are changed when editing Name.
Name vs Developer Name
Name is the field that the user sees when they choose it on the screen (or on the Page Layout). Developer Name is the API name for the record.
This is very similar to the way the Label and the API Name work for fields and objects. Because of this, it is best practice to always use Developer Name, since it is less likely to change (and it is unique in the object). As a dev, you can easily rename the Name to adjust to changing business requirements, but need not rename the Developer Name and leave your code working just fine.
Per the Docs:
Developer NameRequired. The unique name of the object in the API. This name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. In managed packages, this field prevents naming conflicts on package installations. With this field, a developer can change the object’s name in a managed package and the changes are reflected in a subscriber’s organisation. Label is Record Type Name.
Name Required. Label of the record type in the user interface. Limit: 80 characters. Label is Record Type Label. You can read the entire explanation here, in SFDC documentation.
Answer (1)
Choosing between "Name" and "Developer Name" for a record type depends on the context and your specific requirements.
Name: The "Name" field typically represents the human-readable name of the record type. It's what users see and interact with directly in the user interface. Using the "Name" field can make it easier for users to understand and identify different record types.
Developer Name: The "Developer Name" field is often used behind the scenes for programmatic purposes. It's a unique identifier for the record type that can be referenced in code, integrations, or automation processes. The "Developer Name" field is generally more stable and less likely to change compared to the "Name" field.
Here are some considerations to help you decide:
User-Facing vs Programmatic Usage: If the record type name will be visible to users and you want it to be descriptive and easily understandable, use the "Name" field. If you need a stable identifier for programmatic use, choose the "Developer Name" field.
Localization: If your application needs to support multiple languages and the record type name needs to be translated, using the "Name" field might be more appropriate since it's user-facing and can be translated. The "Developer Name" field typically remains constant regardless of language.
Integration and Development: If you're building integrations or writing code that references the record type, using the "Developer Name" field can provide a consistent and reliable way to identify the record type programmatically.
In many cases, you may end up using both fields, with the "Name" field for user-facing purposes and the "Developer Name" field for programmatic references. It's essential to consider the requirements of your specific use case and how you plan to use and interact with the record types in your application.