Sharepoint Refresh - Key not Matching Row -

[Anonymous]

I have a Dashboard that we use, that is connected via Sharepoint, and both datasources are saved on the Sharepoint site.

We move Dashboards through to a 'DEV' space on sharepoint to test issues like this before publishing. The main issue here is that when I refresh the dashboard locally on my Desktop it works perfectly fine, no query errors and no errors at all. Refreshes using the data sets that are saved on the Sharepoint so there is no Source errors.

It is only when I try and refresh the Report on Sharepoint do I get the below error. I have followed all the community solutions aswell as PBI Architechts on our team and we are all stuck right now.

Error Code here with redacted names: {"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":"[Name = REDACTED NAME", Folder Path = \"REDACTED SHAREPOINT NAME Documents/PowerBI Data Source - Findings/\"]"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.Table","detail":{"type":1,"value":"#table({\"Content\", \"Name\", \"Extension\", \"Date accessed\", \"Date modified\", \"Date created\", \"Attributes\", \"Folder Path\"}, {})"}}],"exceptionCulprit":1}}} Table: REDACTED FILE NAME

[Anonymous]

Hi @Anonymous ,

The error message indicates that the key you specified in your query did not match any rows in the table. This could mean that the data source has changed or the query is incorrect.

1.You can try to edit the query in Power BI Desktop and make sure it is valid and returns the expected results. You can check the data types of the key column in both the data source and the report, and ensure that they match. Then, republish and refresh it again.

2. Another possible reason is that the gateway you are using to connect to SharePoint is not configured properly or is outdated. You need to install the latest version of the gateway and add the SharePoint source to it. You also need to enable the option to allow user's cloud data sources to refresh through this gateway cluster. 
3. A third possible reason is that your credentials for SharePoint are expired or invalid. You can try to reset credentials.

Best Regards,

Neeko Tang

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