Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

we encountered an unexpected Error when opening a dataflow

Unable to open a dataflow for editing.

Get the Unexpected error

and the "In progress" Wheel at the Mashup Text

 

The Dataflow Refreshes and I Can Access the Data Through PBI Desktop. 

 

However, this error Prevents me from working on or editing the Query 

I was able to Export the Flow - An Inport it into a new Workspace - I get the same Error

  • Anonymous's avatar
    Anonymous
    5 years ago

    I have discovered a Work Around

     

    Instead of selecting Edit Tables (and getting the error) select Add Tables, add a Blank Query (power Query) you can then Save and It appears to restore Its self

     

    you can then Go in and Delete your bank query Subsequently

  • Anonymous's avatar
    Anonymous
    5 years ago

    All Connections were to the gateway,

     

    However I Too have not seen this reoccur in the last day or so - Seems Resolved 

6 Replies

  • Hey Anonymous ,

     

    I recommend opening a support ticket with MSFT.

     

    Regards,

    Tom

  • Anonymous's avatar
    Anonymous
    Not applicable

    I have discovered a Work Around

     

    Instead of selecting Edit Tables (and getting the error) select Add Tables, add a Blank Query (power Query) you can then Save and It appears to restore Its self

     

    you can then Go in and Delete your bank query Subsequently

  • I getting this too. Same workaround. 
    But have to add table each time i want to edit the dataflow. So the workaround is not fixing the root cause.

    • ChrisBurgessACT's avatar
      ChrisBurgessACT
      Frequent Visitor

      Interesting in my case it appears to be 'erroring' when trying to open Dataflows that are not using a gateway (eg datasource https://api.powerbi.com/v1.0/myorg/admin/datasets), but happy to open/edit any dataflow that uses gateway.
      Furthermore i can open/edit a gatewayless table dataflow by choosing one of the older table (queries) as entry point, rather than a newer (created) table as a entrypoint - no erroring.
      So it appears to be affecting Dataflow tables created since last week where the dataflow does not use a gateway??
      Anonymous can you tell me your gateway/table scenario results?

      • Anonymous's avatar
        Anonymous
        Not applicable

        All Connections were to the gateway,

         

        However I Too have not seen this reoccur in the last day or so - Seems Resolved 

  • Looks like this has been resolved by MS.
    No more unexpected errors. Nil code or environment changes this end.