Powerapp licensing - Premium APIs used by the app: shared_commondataservice

[issac_franklin]

I have created an app that process the data from Dataverse and the app is created by user A in a environment which is not a default one.

All the users in our tenant has O365 E5 license with Powerapp and CDS enabled. However, when user is trying to access the application it asks to enable the trial. When we try not to enable it, we get an error message as " user with object ID does not have a plan with sufficient policies to use premium APIs. Premium APIs used by the app: shared_commondataservice"

Licenses used : 

User A (Who is the owner of app) - Microsoft Business Basic, Power Automate Per User Plan.

All other users - Office 365 E5 license

Can someone help me here ?

@v-xida-msft Maybe you can help me 😉

[issac_franklin]

If you use Dataverse directly with the powerapps(Either to read or write), then there is no way you can escape this as far as I know.

You can still choose to use Dataverse if you have something intermediate and then copy the data from there to Dataverse regularly.

[SiobhanW]

So basically move the data between Dataverse and MS lists to store in Dataverse as it's large volumes but use MS Lists for the actual apps so that it avoids premium connectors. Or even multiple MS Lists that all feed into one table for analytics and storage but have the MS lists broken out to avoid the row limitations. 

We are developing several apps to streamline internal processes and create efficiencies, but premium licences across 800 employees at $20 per user per month, is just not commercially sensible. 

[issac_franklin]

Yeah, Maybe you can also give it a try to use Power Pages (Again depends on the budget)

[SiobhanW]

I think Power Pages, like Dataverse, fall into the premium connector buckets. We just really want a seamless database that isn't as buggy as Lists/Excel for actual manipulation by users in the app. Lists/Excel are fine if people just want to view information, but the moment you layer in any engagement with the data point, it opens you up to process breaking points. We've literally had the app work perfectly for one person but break for another, purely because the MS List has had a size or time out error. 

[chico]

seamless is going to cost money.

but like water and electricity, you can find other paths.

maybe some of your issues come with multiple people making changes at the same time.
not fun idea, but you can isolate changes in to a new sharepoint list.
have that "change list" monitored independently to process each change sequentially avoiding the collisions.
it can all still happen faster than an eye blink, just comes with an extra layer of complexity.

[SiobhanW]

Hmm, yeah we've developed a number of work arounds to solve for this, which does slow down the overall user experience, so I was hoping someone would have some idea of an alternate database that I could use. All databases seem to be premium connectors which is challenging. 

Not sure if PowerApps have considered a capacity licence for end users  that engage with apps with premium connectors (or even just the 1 premium connector- Dataverse) rather than a per user model. They have this for PowerBI and it means that we can develop and things are in fact accessible without becoming overly expensive. The fact that there is a user fee for each individual application is very restrictive. 

[LinTse]

Hi, @issac_franklin ,

Thank you for your information, I'm dealing with this issue right now.

Or maybe can use Dataverse for Teams to avoid the extra plan cost?

But still doubt it even choose DfT, cause I'm using Trigger flows "when a row is added, modified, or deleted".

[issac_franklin]

Hey,

Even if you use the DfT it wouldn't help you. The straight forward solution is to buy the PowerApps Per User license and have it assign to users who would be using the app (If the app is directly connected to Dataverse).

When you say, you have a trigger flow, does it connected to app directly in PowerApps ? or is it created separately from the app ? Maybe giving a bit of a background of the app would be really helpful 😉

[TomasG]

Hi @issac_franklin, 

I have the same problem as you describe.I read the whole conversation and it seems to me that the only way is to buy a license (premium - 20USD) for each user of the application?

Isn't it possible to bind the license to the application and not to the user?

Or if I create a model-driven application, can I avoid this problem? Thus, it would not be necessary to buy an individual premium license for each user?

[issac_franklin]

Per latest documentation, the only license that I could see is the one you have mentioned and app based license. (I really doubt if anyone would buy this expensive license)

I lost now. I would suggest you to get in touch with Microsoft guys for the right answer.