🧐 How to keep Account lean in Dataverse?

by Dec 5, 2023

🧐 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

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more