New Dataverse "When a row is selected" fails for licensing reasons?

(1) Share

Report

Posted on by jzimmermancase

367

I tried building a workflow using the new (not "legacy") version of Dataverse "When a row is selected."

When I try to run it from a model-driven app, I get the following:

Time: "2025-01-27T17:14:38.809Z"

Session ID: cebf64e0-dcd1-11ef-be20-7dbee7615808

x-ms-client-request-id (Client->Backend Request Header): 5d2e12c0-b432-4144-aecd-3f15cf463982

Error: Flow could not be activated because you need a [Power Automate Premium license](https://go.microsoft.com/fwlink/?linkid=2297915) or other license that includes premium connectors to save this flow with connection: ''

I do not get this when I use the "legacy" version. My account is licensed with PowerApps and Power Automate Per User.

Also, wow, Power Platform forums---I can't sort search results by most recent?

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Michael E. Gernaey 53,335 Super User 2025 Season 2 on at

Like (1)

Report

Hi

I have seen this before due to the legacy connector... yeah I don't count that one.

So if you look at your licenses you need an actual Dataverse covered one. Can you verify exactly which ones you have. Unfortunately just saying PowerApps and Power Automate per user can be... tricky due to how they are structured.

I would say one quick test. Can you go and create a brand new flow that uses the Dataverse Connector, with a Connection you created yourself. Not in the Flow, but just go create a Connection with your account. See if that works or not.

It will help figure it out.

Thanks!!

Was this reply helpful? Yes No
Suggested answer

Ravi-Prajapati 416 Super User 2025 Season 2 on at

Like (0)

Report
The issue you're encountering is due to the new version of the "When a row is selected" Dataverse trigger being categorized as a Premium connector, while the legacy version did not enforce this requirement in the same way.

Possible Causes & Solutions

1. Verify Your License

You mentioned you have PowerApps and Power Automate Per User licenses.

Check if your Per User license includes premium connectors (some lower-tier plans only include standard connectors).

Go to Power Automate > Settings > View My Licenses to confirm if you have Premium access.

2. Re-authenticate Your Connection

In Power Automate, navigate to Data > Connections.

Locate your Dataverse connection and see if it has a warning symbol.

Try removing and re-adding the Dataverse connection.

3. Check Your Environment & User Access

Some environments (e.g., Sandbox) may have different policies applied.

Ensure your security role in the model-driven app includes the correct Dataverse table permissions.

4. Use a Workaround (If No Premium License is Available)

Since the legacy trigger works, you might want to:

Stick with the legacy trigger for now.

Consider using a manual button trigger in the model-driven app that calls a cloud flow via Power Automate HTTP Trigger (if available in your plan).

Final Thoughts

The new "When a row is selected" trigger is now classified as Premium, requiring a premium license.

The legacy version does not enforce this check in the same way.

Try re-authenticating or checking if you need a higher-tier license.

If you don't want to upgrade, stick to the legacy version or use a manual trigger workaround.

Was this reply helpful? Yes No
Youcef Doumandji 6 on at

Like (0)

Report

Hi,

I had the same issue as exclusively using the "old" designer. I tried it on the new disigner and it worked fine even after switching back to the "old" designer.

Hope this helps.

Youcef

Was this reply helpful? Yes No