π§ How to keep Account lean in Dataverse?
Inheritance is not so useful in the OOP realm! π₯Bold statement, but why?
Inheritance has a rigid structure, a strict hierarchy that proves difficult to change.
Often you need to adjust the full or part of the inheritance hierarchy to add a new type.
So, what’s the solution?
Composition! π Composition uses instances to build a type.
The same can be applied to the Power Platform / Dynamics 365, or more specifically, to Dataverse!
Avoid the temptation to cramp multiple types into one table, like Account.
If you start to see a lot of fields that only belong to one type, it’s time to rethink our design.
Try using Composition in Dataverse. Create a new table for your new type and link (Lookup) it to a Contact.
Much more flexible and helps to keep Account lean!
What do you think? π
