Dataflow connection only finding production workspace in Deployment Pipeline

[RandyPgh]

Environment: Power BI February 2024

Throughout 2023, our reports accessed the Development workspace of a Deployment Pipeline. This allowed us to make a dataflow change in development, test it in a development report, publish the report to development, and then deploy them all up the chain from dev to test to prod.

Starting around the new December 2023 release, our Desktop reports were getting the error "the key didn't match any rows in the table." Clicking on Navigate's settings, we were only given the choice of the production workspace. Assuming that this might be fixed in a later version, I used production to complete my tasks. However, having just installed the February 2024 release, I continue to see this issue. 

Has anyone else experienced this? Do you have suggestions for connecting to our development dataflows?

[RandyPgh · Accepted solution]

Problem solved. In Desktop, the Data source settings for Dataflows had been changed to use a service account that only had production access. Changing it to a different account solved the issue.

[v-xiandat-msft]

Hi @RandyPgh ,

You can try this:

• Open your Power BI report and go to the Query Editor.
• Locate the query that’s causing the problem (it will likely have a warning symbol).
• In the Applied Steps pane on the right, find the source step for that query.
• Adjust the formula to correctly reference the data.

Below is the post will help you:
Solved: how to resolve Power BI error - the key didn't mat... - Microsoft Fabric Community

Best Regards,

Xianda Tang

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