Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Strange error when publishing dataset. When publishing from desktop it reports success, but when I look at the service it reporting an error like below:
The table being reported is different every time I try and publish or the scheduled refresh occurs. I have gone through the data model at length in desktop and see no credentials issues, no errors in power query, no problems reported in the model view, and no DAX issues on calculated columns or measures.
Have checked with my IT department and they claim they updated the gateway recently. I have re-attached the gateway to my scheduled refresh and double checked the credentials in the service and no problems there either - besides it seems strange that it would also happen on publish rather than manual or scheduled refresh from the service if it were the gateway.
Any ideas anyone?
Hi Im having the same issue, i recreated the view again, change view name, replublished it again, and still its showing this error
Data source error: | "{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The key didn't match any rows in the table."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Key","detail":{"type":1,"value":"[Schema = \"dbo\", Item = \"pbi_Shipmentst\"]"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.Table","detail":{"type":1,"value":"#table({\"Name\", \"Data\", \"Schema\", \"Item\", \"Kind\"}, {})"}}],"exceptionCulprit":1}}} Table: pbi_Shipmentst."
I have several reports using the same gateway with not issues, this is the only report having the problem. Any help will be appreciate.
Thanks |
Hi @Anonymous ,
Has your problem been solved?
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi,
What’s your data source? What’s your connection mode?
Have you configured the gateway for the data source correctly?
Does your data model contain errors?
Solved: Expression.Error: The key did not match any rows i... - Microsoft Power BI Community
Solved: Expression Error.: The key didn't match any rows i... - Microsoft Power BI Community
Have you updated the data source credentials in Service?
What's the version of Power BI Desktop and gateway?
Several users have encountered the same problem recently, which may be related to the software version. Please update Desktop and Gateway to the latest version.
Desktop: 2.87.923.0 64-bit (November 2020)
Gateway: 3000.66.8(2020-11-25)
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Apologies Lionel - been out sick for a while with the global nasty.
So on return to work I can see the problem still exists. To answer your questions:
Data source is SQL Server, Import mode
No errors in the data model when refreshed in Desktop
None of the links to other solutions for the "Key did not match" error seem to be relevant - all data sources, tables and views still exist and refresh fine in desktop
Gateway was configured prior to the error, and was working fine until we moved to Premium a couple of weeks ago. Connections have been tested and gateway has been upgraded recently (having the version checked by my admin), and credentials have been updated post-upgrade.
Looking at the desktop version it is running on September 2.85.985.0, so that will be my next place to review I think. I will check both the gateway version and upgrade desktop (a difficult task as my dev machine is locked down and upgrades need to be pushed by our IT team, so may take a couple of days).
Thanks for the ideas. Will update after these attempts.
Hi @Anonymous
The error indicates that it is missing a key in the table called Dim ProductCategory.
I would have a look at that.
Also if you can make sure that the Gateway Version installed is 3000.66.4
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.