Troubleshooting in Power BI
Resolving global permission conflicts and routing corruption ('The key didn't match') in Power Query.
While clearing the “schema cache” (documented in section 02) resolves issues with modified columns, we occasionally face complete connectivity drops that prevent even visualizing Business Central environments.
This document details how to diagnose and resolve global credential corruption in Power BI Desktop.
Incident: “The key didn't match any rows in the table”
Sección titulada «Incidente: “La clave no coincidió con ninguna fila de la tabla”»Symptom
Sección titulada «Síntoma»When attempting to connect the native Business Central visual connector in Power BI for the first time, or when attempting to change environments (e.g., moving a report from Sandbox to Production), the following critical error appears before the API folders can be deployed:
Error: La clave no coincidió con ninguna fila de la tabla.(En inglés: The key didn't match any rows in the table)Root Cause Diagnosis (Global Permissions Mismatch)
Sección titulada «Diagnóstico Raíz (Global Permissions Mismatch)»This error is neither an AL code issue nor an API outage. It is an internal corruption of the Power Query routing engine (Navigation Path).
Power BI stores a navigation cache in our operating system that is strongly linked to our Azure AD OAuth token. If our token expires, if we change Windows users, or if we attempt to force an update in an environment where our local security signature no longer matches the cached Business Central path, Power BI does not know how to construct the folder tree and throws the “The key didn't match” exception.
DevSecOps Solution: Data Source Permission Reset
Sección titulada «Solución DevSecOps: Reset de Permisos de Origen de Datos»Restarting Power BI is not enough; we must manually destroy the access rights stored globally on our local machine.
- In Power BI Desktop, go to the File tab.
- Select Options and settings -> Data source settings.
- In the pop-up window, it is vital to ensure you are on the Global permissions tab and NOT on “Data sources in the current file”.
- We look in the list for any entry that contains:
Dynamics 365 Business Central- Paths starting with
https://api.businesscentral.dynamics.com... - References to
ODatarelated to our tenant.
- We select each of these entries and click the Clear permissions button at the bottom.
- We confirm the deletion in the dialog box.
- We close the configuration window.
Cold Reconnection
Sección titulada «Reconexión en Frío»Once global security has been purged, we click Get Data again and select our Business Central connection.
The system will recognize that it has no saved permissions and will open the Microsoft authentication popup (OAuth2). Upon logging in again, a clean token will be generated, and navigating through the API folders will work perfectly once more.
Power BI Troubleshooting Checklist
Sección titulada «Checklist de Resolución de Problemas en Power BI»- ✓ Credential Debugging: Purging the “Global Permissions” configuration to rule out corrupt or expired OAuth tokens.
- ✓ Clean Authentication: Forced logout and Microsoft Entra ID session restart to regenerate read tokens.
- ✓ Validation: Verification of the correct visual display of analytical folders in Power BI Desktop after reconnection.

