Delta Sharing connector - Losing credentials with every scheduled refresh on PBI Service

[HeleneNov]

Hi,

We're using the Delta Sharing Connector (for Databricks). It works well, until we upload files with different delta sharing sources (diferent bearer tokens) in our capacity, on different workspaces. Once uploaded, we add the credentials and we can refresh manually each dataset, but when we try and schedule the refresh of these different datasets (we chose different refresh times), we get this error:

"Data source error: Expression.Error: The key didn't match any rows in the table.. Key = <ccon>[Name = “xxxxxx]. Table = #table({"Name", "id", "Data", "ItemKind", "ItemName", "IsLeaf"}, {}). </ccon>;The key didn't match any rows in the table.. The exception was raised by the IDbCommand interface. Table: factXXX."

Once we get the error, in Settings --> Credentials, we have to re-paste the bearer token for each dataset source. Then manually we can refresh, but the next scheduled refresh, we get the same issue.

It seems to me PBI service is mixing up the credentials between the different datasets.

Can you help us with this? 

Thanks

[gharvisit]

It appears that you're encountering an issue with the Delta Sharing Connector in Power BI Service where credentials are being lost or mixed up when scheduling refreshes for datasets from different Delta Sharing sources with different bearer tokens. This can be a challenging problem to troubleshoot, but there are several steps you can take to investigate and potentially resolve the issue:

1. **Check Workspace Permissions:**
Ensure that the workspaces where these datasets reside have the appropriate permissions set up. Make sure that the credentials are configured at the workspace level rather than at the individual dataset level if you want them to be consistent across all datasets in that workspace.

2. **Workspace Isolation:**
Consider isolating datasets from different Delta Sharing sources into separate workspaces. This can help prevent credential mix-ups and conflicts between datasets.

3. **Credentials Management:**
Review how you are managing credentials for these datasets. Instead of manually pasting bearer tokens each time, you might consider using Power BI's built-in credential management options, such as Service Principal or Organizational Account, depending on your authentication method.

4. **Scheduled Refresh Timing:**
Check if there are any overlapping refresh schedules for these datasets. If multiple datasets are set to refresh at the same time, it might lead to conflicts in accessing resources.

5. **Data Source Configuration:**
Verify that the data source configurations for each dataset are correct, including the bearer token. Ensure that there are no typos or issues with the token itself.

6. **Logs and Diagnostics:**
Monitor the refresh logs in Power BI Service to gather more details about the error. This can help pinpoint the exact issue or any patterns that might be causing the credentials to mix up.

7. **Contact Support:**
If the issue persists and you cannot identify a resolution, it might be worthwhile to contact Power BI support. They can provide more specific assistance and investigate the issue further.

8. **Update Connector and Power BI Version:**
Ensure that you are using the latest version of the Delta Sharing Connector and Power BI Service. Sometimes, updating to the latest versions can resolve compatibility issues or bugs.

9. **Community and Forums:**
Search Power BI community forums or other relevant online communities. Other users might have experienced similar issues and could provide insights or workarounds.

Remember to carefully manage your credentials and data source configurations, and consider separating workspaces or using dedicated service principals for each data source to prevent conflicts. Additionally, keep an eye on any updates or announcements related to Delta Sharing Connector and Power BI, as issues like this may be addressed in newer releases.

[HeleneNov]

Hi Gharvisit, thanks for the message. Sadly the datasets are all already configured with their own set of credentials from the start. But the error is still there when we do the schedule refresh on PBI service.

The error message is the one I put in the first message.

Thanks!

[gharvisit]

It appears that you are encountering an issue with Power BI Service mixing up the credentials between different datasets that use different Delta Sharing sources. To resolve this issue, you may need to ensure that each dataset is configured to use its own set of credentials.

One possible approach to accomplish this is to configure each dataset to use a separate set of credentials. You can do this by following these steps:

1. In Power BI Desktop, go to "Edit Queries".
2. Select the dataset that you want to configure with its own set of credentials.
3. In the "Home" tab, select "Transform Data".
4. In the "Transform Data" window, select "Data Source Settings".
5. Select the data source that you want to configure with its own set of credentials.
6. Click "Edit Credentials" and enter the appropriate credentials for that data source.
7. Click "OK" to save the changes and close the "Data Source Settings" window.
8. Save and publish the changes to the dataset.

After completing these steps, you can configure each dataset to refresh on its own schedule. This should help to avoid any conflicts with credentials between different datasets.

If you are still encountering issues after configuring each dataset with its own set of credentials, it may be helpful to review the error message and any other logs or error reports for additional information that could help identify the root cause of the issue.

Airport details