Dataverse Entity Naming Best Practices

(1) Share

Report

Posted on by AZWildcat1290

Hi everyone!

We are in a situation where we are rebuilding our system and trying to come up with a best practice when creating entities. We have run into issues in the past where we would create an entity and then later on install an add on from Microsoft which has the same entity name for example Time Entries which is included in Project Operations and Field Services. Has anyone come up with any best practices for their company when it comes to naming entities to avoid this situation? Duplicate entity names make it really hard when it comes to doing searches and reporting in Dynamics and Power BI. One of my team members suggested we tack on the solution name either before or after the table name. Pros and cons of doing this? Or do you have any other suggestions?

Thank you for the help!

Categories:

Customization / Solutions / SDK and API

Dynamics 365 Administration

All responses (2)

Answers (0)

AZWildcat1290 47 on at

Like (0)

Report

Dataverse Entity Naming Best Practices

Hi,

To update this post as I got more information yesterday the ask is more of is there a way to show the name field vs the display name to the backend users no matter what system they are using ie running reports, flow, powerbi? Or is it possible to have a custom display name where we can set it to the Display Name with an * at the end for example Time Entry*. We dont necessarily want end users to see the * but for the backend users it would be super helpful to know which fields are custom...

Thanks!

Stephanie
Suggested answer

Dengliang Li Microsoft Employee on at

Like (0)

Report

Entity Naming Best Practices

Hi,

When creating a custom entity, the logical name is automatically prefixed with the solution. However, the display name can be repeated.

Yes, you can add a custom prefix to the display name of an entity.
If you have two custom entities with the same display name, you can add a prefix based on their specific purpose to make the name clearer.

Best Regards,
Dengliang Li