Forum Discussion

mattcarter865's avatar
4 years ago

New PowerPlatform Dataflow error when trying to refresh in Service

Per the recommendation from a recent release I have been using the PowerPlatform Dataflow connector in Desktop. It worked fine.

 

When I tried to do a refresh in the Service today on a new dataset I got this error

 

Underlying error code: -2147467259
Underlying error message: The key didn't match any rows in the table.
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.Key: [entity = "Date", version = ""]
Microsoft.Data.Mashup.ValueError.Reason: Expression.Error
Microsoft.Data.Mashup.ValueError.Table: #table({"entity", "dataCategory", "Data", "Tags", "ItemKind", "ItemName", "IsLeaf"}, {})
Cluster URI: WABI-US-EAST-A-PRIMARY-redirect.analysis.windows.net
Activity ID: bb2b0ba0-b6ff-4ec6-b3cb-e49cdae18ed8
Request ID: 25f9f9f4-a7bd-3174-1f5a-fe61beeee892
Time: 2021-09-14 18:41:56Z

This was my original M code (edited)

let
Source = PowerPlatform.Dataflows(null),
Workspaces = Source{[Id="Workspaces"]}[Data],
#"yyyyy" = Workspaces{[workspaceId="yyyyy"]}[Data],
#"xxxxx" = #"yyyyy"{[dataflowId="xxxxx"]}[Data],
Date_ = #"xxxxx"{[entity="Date",version=""]}[Data]
in
Date_

It looks like this part is what was causing the error

Date_ = #"xxxxx"{[entity="Date",version=""]}[Data]

 

I swapped to using the (legacy) Power BI Dataflow connector in Desktop and republished. Then it worked fine.

let
Source = PowerBI.Dataflows(null),
#"yyyyy" = Source{[workspaceId="yyyyy"]}[Data],
#"xxxxx" = #"yyyyy"{[dataflowId="xxxxx"]}[Data],
Date1 = #"xxxxx"{[entity="Date"]}[Data]
in
Date1

 

 

 

1 Reply

  • v-henryk-mstf's avatar
    v-henryk-mstf
    Community Support

    Hi mattcarter865 ,

     

    According to your description, it seems that the problem is caused by different versions. Try to set the version parameter in Date_ = #"xxxxx"{[entity="Date",version=""]}[Data] to the version number corresponding to the current pbi desktop, and then try again, whether it works.

     

     


    If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.


    Best Regards,
    Henry


    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.