Introduction
“Unable to connect because this credential type isn’t supported for this resource. Please choose another credential type.” This issue arises when attempting to refresh queries within Power BI or Power Query from the Excel interface. It also occurs when users choose to log in using their organizational accounts. The occurrence of this problem can be attributed to various factors that disrupt the seamless execution of these actions.
When trying to refresh queries using Power BI or Power Query in Excel, encountering this error message indicates that the process was unsuccessful due to underlying obstacles. Similarly, when individuals opt for authentication through organizational accounts, this error can hinder their access attempts to the intended system or service.
Table of Contents
Solution – Unable to connect because this credential type isn’t supported for this resource. Please choose another credential type
Frequently, changes are made to the backend path or location of SharePoint by the Organization Admin. The primary reason behind this error is the accidental inclusion of unnecessary words in the designated source file path. These modifications are typically carried out by administrators who have the required privileges to configure the organization’s SharePoint environment.
To address this issue, follow these steps
- Open Power Query Editor: Begin by opening the Power Query Editor, where you manage data connections.
- Select Your File: Choose the file you want to work with from the list in the Power Query Editor.
- Check Source Path: Look at the source path of your chosen file. This shows where the file is stored in SharePoint.
- Remove Unneeded Words: Delete any extra words between “//www.sharepoint.com/” and “/sites/”. These words might have been added unintentionally.
- Success: After removing those unnecessary words, your file’s path will be accurate. You’re now set to proceed without errors.
Conclusion
To ensure error-free data access from SharePoint, it’s vital to consistently verify the source path. Even minor word additions within the path can trigger loading errors. Vigilance in scrutinizing the source path guarantees smooth file retrieval and uninterrupted workflows.
