vegaaltair
New Member
- Joined
- Sep 12, 2014
- Messages
- 9
Hi, I have a report accessing data via sql that refreshes successfully in the desktop app with no errors shown and works great. When it is published to the workspace it errors out and gives me the below error message but if this is accurate the key not found error would have to happen in the desktop app when a refresh occurs? When I look at the EOM account table, I cannot see anything wrong, and the "key" is populated on every row of the table.
At a bit of a loss as to what the issue actually is, I have checked credentials and the other table is accessed and works fine. Has anyone had this issue of refreshing not working in the workspace but is actually fine in the desktop app? not sure where I should be looking.
At a bit of a loss as to what the issue actually is, I have checked credentials and the other table is accessed and works fine. Has anyone had this issue of refreshing not working in the workspace but is actually fine in the desktop app? not sure where I should be looking.
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 = \"EOM Account\", Item = \"Account (DH)\"]"}},{"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: EOM Account.
Cluster URI: WABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net
Activity ID: fad667f3-327f-4a0f-8253-c2d48b7e64c0
Request ID: 4ed610af-b497-98a6-59da-2940a9279124
Time: 2024-06-04 00:44:58Z