Events
Powerful Devs Conference and Hack Together
Feb 12, 11 PM - Feb 28, 11 PM
Join the online conference and 2-week hackathon to explore building powerful solutions with Power Platform.
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We recommend that you create a solution to manage your customizations. By using a custom solution, you can easily find just the solution components you've customized, consistently apply your solution publisher prefix, and export your solution for distribution to other environments.
If you don't use a custom solution, you'll be working in one of these default solutions in the unmanaged layer:
There are a few reasons why you shouldn't create apps/flows and make customizations in either of the default solutions:
The default solution in the Power Platform is the Common Data Service Default Solution, which is associated with the Microsoft Dataverse Default Publisher. The default publisher prefix will be randomly assigned for this publisher, for example it might be cr8a3. This means that the name of every new item of metadata created in the default solution will have this prepended to the names used to uniquely identify the items. If you create a new entity named Animal, the unique name used by Dataverse will be cr8a3_animal. The same is true for any new fields (attributes), relationships, or option-set options. If you'll be customizing this special solution, consider changing the publisher prefix.
Events
Powerful Devs Conference and Hack Together
Feb 12, 11 PM - Feb 28, 11 PM
Join the online conference and 2-week hackathon to explore building powerful solutions with Power Platform.
Register now