Power BI Dataflows

[ruxandraalina]

Hello!

I have a bit of an issue with some dataflows and I was hoping someone could provide some insight. 

I have a client who created an Odata feed that extracts data from a ticketing system, which then I am using to create some dataflows in Power BI. The client has full control over the Odata feed and the ticketing system. 

When trying to do some more transformations in Power Query, I get an error that says "The key didn't match any rows in the table" for all 29 tables. When I click on "Go To Error", it leads me directly to the data source. 

What I've noticed is that if I try to recreate the data source from scratch and compare the new advanced editor script vs the original one, the workspake and dataflow IDs are completely different. 

In between now and the last time I've made any changes to the report (I'm talking about new measures here, no other changes), I haven't changed anything in the dataflows or in Power Query and everything worked smoothly last time. 

Weird thing is that I obviously cannot refresh anything in the Desktop version, but the refresh is working just fine in Service. Now I'm not 100% if the refresh is actually bringing new data or it is just running empty (latest available data is from around 15 hours ago, but I'm sure how often the Odata feed captures changes in the ticketing system). I also downloaded the reports from Service, but I get the same error in Desktop. 

I had the same issue a few months ago with the same report and I fixed it by replacing the original workspace and dataflows IDs with the new ones. I got the new ones by simply recreating the connection from scratch. 

I could do the same right now, but we are talking about 29 different queries in a single report + 2 more reports using the same dataflows with the same issue.

I would like to understand why this happened and find a more sustainable solution. 

Thank you!

Ruxandra

[ruxandraalina]

One more thing worth mentioning - the same Odata feed is used to create two different dataflows: one that I've previously talked about (used for reports in client's Service infrastructure) and another one used for reports in our own infrastructure. 

When checking, I've just realized that the report in the client's infrastructure somehow got mixed up with the dataflows from our own infrastructure, hence the "key did not match any rows" error I assume. 

But I have no idea how this happened. I'm currently logged in Desktop using client's credentials, but somehow Power Query accesses dataflows from our own infrastructure. 

[ruxandraalina · Accepted solution]

It was a matter of credentials getting mixed up...so the issue is resolved now.