Every record entered into the Dataverse contains a unique identifier (a GUID). This number is not user friendly and not helpful when a user wants to look up and associated another record to the record they have in context.
Needless to say, the tables in Dataverse have the "name" field. The name field provides an opportunity to create a friendly name for each record.
On EVERY project when working with people who have never used Microsoft Dynamics 365 Customer Engagement or Dataverse, the NAME field becomes something that each struggle to get their head around.
- Why is it needed?
- Do I need to enter it?
- Can we default the name field?
- Does it need to be unique?
Always questions and often questions that are difficult to explain.
Some tables within the Dataverse set the name field to a "common sense" value, for instance the name fields for most all of the "Activities" tables are the subject line.
Is it needed? yes
Do I need to enter it? yes or
Can we default the name field? yes, many use a quick workflow to set it to a concatenated value
Does it need to be unique? no
Is it helpful for it to be unique? yes!
When you look at a list of records, it is always nice to have one column that is unique and that provides context and value to the end user.
If you are creating custom tables in the Dataverse, always consider the "NAME" field which is automatically created when you create any new table.
"The Primary Name Column in Dataverse is a human-readable field that acts as the default identifier for a record in the user interface. It represents the record in views, searches, and other UI interactions1. The field can be changed during table creation and is best set to something relevant such as Name, Title, Subject, or Label2. It is not the primary key field and can have duplicate values3."