Microsoft Dataverse, the Database Behind Power Platform Environments, Solutions and Apps
View All Tags
The app gets its home in this part: a Power Apps solution that holds the canvas app and three environment variables, which tell the app where its SharePoint data is. By the end, the app is created, connected to both lists and to Microsoft 365 user profiles, and ready for its first screen.
A canvas app that reads a SharePoint list normally has the site's address and the list built into it. Move the app to another organization and it still points at the old site. Environment variables fix that: the app asks the variables where its data is, and each environment gives them its own values.
A solution is the box you build a Power Apps app in, so that the app and everything it needs can move to another environment together. Every solution belongs to a publisher, and the publisher's prefix ends up in the name of everything you create. Ten minutes spent on both now saves renaming later, which often isn't possible.
Being a Global or Power Platform admin doesn't make you System Administrator of an environment's Dataverse. Microsoft stopped assigning that role to admins automatically. When you need it, you give it to yourself in the Power Platform admin center, in four clicks.
Power Apps solutions, the packages you use to move apps from one environment to another, are stored in Dataverse. Your organization's Default environment doesn't have Dataverse until an admin adds it. It takes a minute, uses storage Microsoft already gives the Default environment, and can't be undone.
You open a solution in Power Apps and a yellow bar across the top says One or more commands are unavailable due to your current privileges for this environment. Nothing is broken. Your Dataverse security role simply doesn't allow some of the solution's commands, so Power Apps hides or disables them.
You've just added Dataverse to your Power Platform environment, opened Solutions in Power Apps, and instead of a list of solutions you get We couldn't load your data. Try again doesn't help. The cause is a missing security role, and in the Default environment it usually fixes itself within minutes.
