Power Platform Community Forum Thread Details

What can you do in an environment with no Dataverse database enabled? It's my understanding that without it, you can't create Solutions, which makes ALM, connection references, environment variables, managing dependencies, and general organization very, very difficult (or impossible?)

And how can I articulate the difference between enabling a Dataverse backend for an environment and allowing users to have premium connections to Dataverse tables? Is there some documentation that clearly spells this out? There are some in my organization who want to create environments named after stages of ALM (such as "UAT" or "PROD") but then take away the mechanism that would allow us to actually package and deploy solutions from one to the other. Is this as crazy as it sounds?

You can have a database-enabled environment that still restricts access to the Dataverse premium connectors in Apps and Automate, correct?

Categories:

General topics

Just and example from where I am as an end user.

Our organization has dataverse tables and I did not have a dataverse premium connector a few years ago, so I never looked at them. But I did try to create tables and it never worked, so I figured I just didn't have the privileges.

Once I got the Dataverse premium connector I can connect to the tables, but if I don't have permissions, then I can't get the data. However, I use the Dataverse for Teams in a Project Environment no problem. I use Dataverse for Teams all of the time, but I can't use the Dataverse in our Production Environment.

I will say I think it is odd how the Dataverse functions. For example, in our production (Non-Teams) environment, I have the ability to create and load a dataverse table. However, I'm not able to look at anything within the table, edit the table, nor am I able to delete the table. If I use the premium connector to the table that I created, it will fail my flow for lack of privileges.

It seems like our IT has it set to where any table in the dataverse does not have end user permissions to view or edit, but for some reason I can still create one even though I can't do anything with it.

Don't think this answers your question, but just giving an example. We have dataverse, I have a premium connector, I can't do anything to the tables in the production environment because I don't have privileges.