Best Practices when working with Dataverse

This post is part of the Dataverse series.


Create within a solution

Create tables in the base language

Set table Ownership correctly

Only activate features that you really need

Set table image

Be consistent in naming columns

Do not use Display name multiple times

Think about Global or local choice

Check existing column properties

Check and define Relationships


All parts of this series (21)
  1. 1. Copilot for Dataverse - New experience
  2. 3. Copy an existing Model Driven App
  3. 4. Editing Command Bar in Model Driven Appswith Power FX 2
  4. 5. Custom Pages in Model Driven Apps
  5. 6. Editing Command Bar in Model Driven Appswith Power FX
  6. 7. Dataverse Teams Integration - External Content
  7. 8. Dataverse Email Integration
  8. 9. Manage Polymorphic Lookups in Dataverse with XRM Toolbox
  9. 11. Mapping columns in related Many-to-Many tables
  10. 12. Mapping Lookup Columns
  11. 14. Best Practices when working with Dataverse
  12. 15. Create your own M365 Dev Tenant
  13. 17. Activate additional languages in Dataverse
  14. 18. Publishers and Solutions
  15. 19. Tables and Columns
  16. 20. Datamodelling in Dataverse
  17. 21. Introduction to Dataverse