Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
Check it out now!Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
So I have a dataset that is working in Power BI Service just fine. It is also working fine on my old laptop.
But all of my dataflow specific queries return an error when using Power BI Desktop on my new laptop.
New and old laptop have the same (latest) version of Power BI. I also tried other dataflow connectors, same result.
A simple query like:
let
Source = PowerBI.Dataflows(null),
#"23610782-1e92-4430-a29e-e19148e13999" = Source{[workspaceId="23610782-1e92-4430-a29e-e19148e13999"]}[Data],
#"fb6a16a9-7fdf-4c9f-9b15-430g9999dea0" = #"23610782-1e92-4430-a29e-e19148e13999"{[dataflowId="fb6a16a9-7fdf-4c9f-9b15-430g9999dea0"]}[Data],
step = #"fb6a16a9-7fdf-4c9f-9b15-430g9999dea0"{[entity="Source"]}[Data]
in
step
Returns always the same "The key didndn't match any rows in the table" error
Expression.Error: The key didn't match any rows in the table.
Details:
Key=
workspaceId=23610782-1e92-4430-a29e-e19148e13999
Table=[Table]
So I guess it's not a Power BI related issue, but I'm not sure what could cause this. Anyone has an idea?
Solved! Go to Solution.
Hi @PVO3,
Thanks for confirming that both laptops have the same culture settings and that you're using the same account. Since we've ruled out culture differences, let's check other possible reasons :
* Clear your Power BI Credentials and Reauthenticate. Go to File then Options and settings then
Data source settings. Now look for any PowerBI.Dataflows credentials, delete them, and
reconnect. You can also sign out of Power BI Desktop completely and sign back in which will
restart it too.
* Also check for Network or Firewall Restrictions, if your new laptop is on a different network, a
firewall or proxy might be blocking access to Power BI Dataflows.
* You have to manually verify workspace and dataflow IDs by going to Power BI Service, then go
to Workspaces and then Your Dataflow. Copy the workspaceId and dataflowId from the URL
and compare them with those in your query. If they don’t match, update your query
accordingly.
* You can also test with a different version of Power BI Desktop. Even if both laptops have the
latest version, some updates may behave differently. Try installing an older version of Power
BI Desktop and run the query again and see if it works.
* You can also enable tracing to get more details regarding the issue you are facing. Go to File
then Options and settings and again options and then Diagnostics. Enable Tracing, then try
running the query again. You can check the logs in stored in "c:\Users\(your
user)\AppData\Local\Microsoft\PowerBI Desktop\Traces"
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Thanks for your replies! Unfortunatly I am not able to find the issue.
I tried to check the culture with PowerShell but both laptops have the same culture.
@lbendlin the link you provided doesn't mention culture/setup? Can you please tell me more specificly where I could find this culture/setup difference?
I'm also using the same account on both machines. Both for service as for desktop.
Hi @PVO3,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.
Hello @v-mdharahman,
No, my issue is not resolved, like mentioned in my reply. I still have no idea where to look.
My current workaround is to keep 2 laptops around all the time.
Hi @PVO3,
Thanks for confirming that both laptops have the same culture settings and that you're using the same account. Since we've ruled out culture differences, let's check other possible reasons :
* Clear your Power BI Credentials and Reauthenticate. Go to File then Options and settings then
Data source settings. Now look for any PowerBI.Dataflows credentials, delete them, and
reconnect. You can also sign out of Power BI Desktop completely and sign back in which will
restart it too.
* Also check for Network or Firewall Restrictions, if your new laptop is on a different network, a
firewall or proxy might be blocking access to Power BI Dataflows.
* You have to manually verify workspace and dataflow IDs by going to Power BI Service, then go
to Workspaces and then Your Dataflow. Copy the workspaceId and dataflowId from the URL
and compare them with those in your query. If they don’t match, update your query
accordingly.
* You can also test with a different version of Power BI Desktop. Even if both laptops have the
latest version, some updates may behave differently. Try installing an older version of Power
BI Desktop and run the query again and see if it works.
* You can also enable tracing to get more details regarding the issue you are facing. Go to File
then Options and settings and again options and then Diagnostics. Enable Tracing, then try
running the query again. You can check the logs in stored in "c:\Users\(your
user)\AppData\Local\Microsoft\PowerBI Desktop\Traces"
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi @PVO3,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.
Thank you.
I'm sorry haven't found time to dig deeper. I already have this issue about 10 months and I haven't made any progress.
I'm using dataflows extensively because of their flexibility but they are my main source of issues.
Hopefully I'll be able to spend some time on it this week.
Hi @PVO3,
Thank you for following up with the conversation. I wanted to check if you had the opportunity to review the information provided.
If you are still unable to solve the issue you can reach out to Microsoft Support by raising a ticket with Microsoft Support.
Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you.
Thanks @v-mdharahman!
I think the clearance of credentials did the job. I tried reauthenticating before, but it didn't work. The full clearing seems to work a bit different.
Hi @PVO3,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like you are facing an issue where Power BI cannot find a matching entry in the queried data source. Please go through the points suggested by @lbendlin. Apart from the mentioned points you can also check for few more things like:
* Your Power BI Desktop may not be authenticated correctly for dataflows on the new laptop.
* Make sure you are using the same account in Power BI Desktop as in Power BI Service.
* Also check if your new laptop's user account has the correct permissions in Power BI Service.
* If none of the above work, Power BI Desktop logs may provide more details on your issue.
I would also take a moment to thank @lbendlin, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
It's a setup/culture issue on your new PC. https://blog.crossjoin.co.uk/2020/04/06/understanding-the-the-key-didnt-match-any-rows-in-the-table-...