Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

Issue Regarding Power BI service

My scenario is : I have "NRPPartClassification" this file earlier with three column "PART_NO","PART TYPE" and, "MAJOR PARTS" so my requirement is replace this file with NRPPartClassification(ER1+ER2)...
  • bhanu_gautam's avatar
    1 year ago

    Anonymous 

    The key didn't match any rows in the table" typically indicates that the Power BI service is unable to find the file at the specified location during the scheduled refresh. This can happen due to several reasons, such as changes in the file path, file name, or access permissions. Here are some steps to resolve this issue:

    Verify File Path and Name: Ensure that the file path and name specified in your Power BI query match exactly with the file stored in SharePoint. Even a small discrepancy can cause this error.

    Check Access Permissions: Make sure that the account used for the scheduled refresh has the necessary permissions to access the file in SharePoint. Sometimes, permissions might be different for the desktop and service environments.

    Update Data Source Credentials: Go to the Power BI service, navigate to the dataset settings, and update the data source credentials. This ensures that the service has the correct credentials to access the file.

    Reapply Query Steps: Open the Power BI Desktop file, go to the Power Query Editor, and reapply the steps to ensure that the query is correctly referencing the new file. Sometimes, reapplying the steps can resolve any underlying issues.

    Check for Case Sensitivity: Ensure that the file name and path are correctly referenced with the correct case (uppercase/lowercase) as SharePoint can be case-sensitive.

    Test Connection in Power BI Service: In the Power BI service, test the connection to the data source to ensure that it is working correctly.