Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
Gandhia
Helper II
Helper II

Problem with dataflow and/or Expression.Error: The key didn't match (DATASET DOESN'T REFRESH)

EDIT:
The error is:

Expression.Error: The key didn't match any rows in the table.
Details:
Key=
workspaceId=xxxyxxxy-yxxx-xyxx-yyyyyyyxxxxxxxyy (anonymised, where x = number, y = letter)
Table=[Table]


I still have a problem mentioned here:
Expression.Error: The key didn't match any row... - Microsoft Fabric Community

The problem appears when there have done some changes in data source. The strange thing is that the report still receives data, so it works in part. Probably one of the columns is broken

In my best guess or solution at the moment is that there is dataflow which isn't connected (or connected correctly) to my report.

In the Power BI Service (report's prod workspace) there is a lineage view and when I look at it, there are a couple of data sources. One can be found in desktop, the other not (I mean when doing source --> Data column Folder --> Continue --> There is a list of workspaces / dataflows (columns: workspaceId, workspaceName, workspaceType etc.) that I have access to (or what can be used in report, I'm not sure?) but there are no this other dataflow that I need.



SO: Does anyone know, why there is not this other dataflow, because it should work.
And I have tried data source settings --> global permissions --> clear permissions and new source --> dataflow --> log in --> but it is NOT there either.

Do I need to have dataflow available on my desktop (i.e. permissions, or whatever?) for the report to work correctly and the error to disappear? Anyone have any guesses or knowledge of a solution to the problem?

Could someone please help me that I can solve it before xmas 😄 

Thank for your time and thanks in advance!

Greetings,
Gandhi

 

1 REPLY 1
sergej_og
Super User
Super User

Hey Gandhi,
when changes on your source caused this issues...
 - check the column names after changes are applied
If that often the case you can apply the naming of your columns in your model by the order of the columns coming from the source. Not relying on the namings from the source.

What do you think?
Is it worth a trial?

I solved many times issues like this using this approach.

Regards

Helpful resources

Announcements
Sept PBI Carousel

Power BI Monthly Update - September 2024

Check out the September 2024 Power BI update to learn about new features.

September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

Sept NL Carousel

Fabric Community Update - September 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors