🧐 How to keep Account lean in Dataverse?

by Dec 5, 2023Shorts

🧐 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? 💭

Remy van Duijkeren

Remy van Duijkeren

The Marketing Developer

I build automation and integrations that remove the annoying stuff—using Power Platform, Dynamics 365 & Azure.

Get My Thoughts on Automation & Development

Join my personal newsletter and get practical insights on building faster, integrating smarter, and removing friction in IT systems — especially on Power Platform and Dynamics 365.

Related

Hourly billing is nuts.

Hourly billing is nuts. Because the slower someone works, the more you pay. And the faster someone is… the more they get punished. Great system,...

read more