Forum Discussion

DM474's avatar
DM474
Regular Visitor
11 months ago
Solved

Cannot edit a Dataflow

I am trying to edit a dataflow that just needs a new data connection. The error i am getting is 'This action cannot be performed by someone other than the dataflow owner.' The thing is the user I am logged in as IS the Dataflow owner. I did the whole Take Over several months ago. When I see the Dataflow in Power BI Service it shows me as the Owner.

 

In testing why this is the case, I even created a new Dataflow and got the same error when trying to add a connection to that. It isnt even recognising me as the owner of a Dataflow that I just created. 

 

Any ideas?

 

TIA! 

  •  for your replies, unfortunately I could not fix the issue. Rather the admin preferred to just create a new user acount and that one does work. Thanks for the help!

9 Replies

  • Hi DM474,

    Thank you GrowthNatives, for your insights.

    Even if you are listed as the owner, you may not be able to edit a dataflow if tenant settings restrict dataflows or if your account does not have the Environment Maker role. Please ask your admin to enable dataflows in the Admin portal → Tenant settings and verify your role assignment.

    Below is the link for you reference:

    Troubleshoot dataflow issues - creating dataflows - Power Query | Microsoft Learn

    Security roles and permission levels in standard dataflows - Power Query | Microsoft Learn

     

    Thank you.

    • DM474's avatar
      DM474
      Regular Visitor

      Thanks for your reply, I will check out the link you have provided and see if that helps. 

  • Hi DM474 ,

    If you’re seeing that error even though you show as the owner, a few quick checks usually solve it:

    • Workspace type & permissions 
      • Is the Dataflow inside a new Fabric (v2) workspace or a classic workspace?
      • In v2 workspaces, only Admins and Members can edit dataflows. If you’re a Contributor or Viewer, even as “owner” of that artifact, editing won’t be allowed.
        • Double-check your workspace role: Workspace > Access > your name > confirm it says Member or Admin.
    • Connections/credentials – Re-enter credentials under Manage connections and gateways. Old bindings can block edits even after Take Over.
    • Browser/session – Try InPrivate/Incognito to rule out cached tokens.
    • New workspace test – Create a new workspace, make yourself Admin, then create a test dataflow. If that works, it’s a role/connection issue; if not, it’s likely tenant-wide → raise a Support ticket.

    Hope this solution helps you make the most of Power BI! If it did, click 'Mark as Solution' to help others find the right answers.
    💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!
    🚀Let’s keep building smarter, data-driven solutions together! [Explore More]🚀

    • DM474's avatar
      DM474
      Regular Visitor

      Thanks for your response, I am trying your suggestions now. 

      • GrowthNatives's avatar
        GrowthNatives
        Super User

        Hi DM474 ,
        Glad to hear you’re trying out the suggestions! 
        Were you able to get the issue resolved after those steps? If not, just let me know where you’re still running into trouble and I’ll be happy to assist further.

         

        If my suggestion worked, please click Mark as Solution to help others find the right answers.

        💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!
        🚀Let’s keep building smarter, data-driven solutions together!  [Explore More]🚀

  • Shahid12523's avatar
    Shahid12523
    Community Champion

    Even if you're listed as the Dataflow owner, Power BI might block edits due to stale credentials, workspace role limits, or gateway restrictions. Try re-authenticating the data source, confirm you're a workspace Admin, and check gateway access. If it still fails, it could be a tenant-level bug or metadata sync issue.

    • DM474's avatar
      DM474
      Regular Visitor

      Thanks for your reply! Yes, that all lines up. I think you are right with the tenant level issue. 

  • DM474's avatar
    DM474
    Regular Visitor

     for your replies, unfortunately I could not fix the issue. Rather the admin preferred to just create a new user acount and that one does work. Thanks for the help!