Common Data Services Default Solution is gone?

by Oct 16, 2023

Common Data Services Default Solution is gone?

Everything you do in Dataverse (Dynamics 365) outside of a solution is being ‘recorded’ in the Common Data Services Default Solution.

Very convenient! See the changes you forgot to add to your solution.

Nice for customers who don’t need a full ALM pipeline, which IMHO, is more often than not. I also use this method for my own small company.

I often rename Common Data Services Default Solution to a better name. For example, Dataverse Default Solution or ‘CustomerName’ Customizations.

I also tweak the CDS Default Publisher to get the preferred prefix.

But now we have a new feature in Preview:

Preferred Solution!!!

When you enable this feature, you can change the solution than going to contain the changes you make outside of a solution.

Perfect! A nice feature that i am going to use a lot!

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/preferred-solution

#
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