Skip to main content

Notifications

Announcements

🌸 Community Spring Festival 2025 Challenge 🌸
Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id : pcAOTkwXibG4dgMjuE7CAF
Power Platform Community / Forums / Power Automate - Building Flows / New Dataverse "When a ...
Power Automate - Building Flows
Suggested answer

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

Like (1) ShareShare
ReportReport
Posted on 27 Jan 2025 17:28:37 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:
Licensing
  • Youcef Doumandji Profile Picture
    Youcef Doumandji 6 on 03 Mar 2025 at 09:28:03
    New Dataverse "When a row is selected" fails for licensing reasons?
    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
  • Suggested answer
    Ravi-Prajapati Profile Picture
    Ravi-Prajapati 409 on 22 Feb 2025 at 06:48:04
    New Dataverse "When a row is selected" fails for licensing reasons?

    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.
  • Michael E. Gernaey Profile Picture
    Michael E. Gernaey 39,182 Super User 2025 Season 1 on 22 Feb 2025 at 05:14:39
    New Dataverse "When a row is selected" fails for licensing reasons?
    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!!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

🌸 Community Spring Festival 2025 Challenge 🌸
Welcome to the Power Platform Communities

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Markus Franz – Community Spotlight

We are honored to recognize Markus Franz as our April 2025 Community…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 146,518 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 65,710 Most Valuable Professional

Leaderboard

Featured topics

Start and wait for an approval action

Product updates

Microsoft Power Platform Community release plans