SharePoint.Contents - Expression Error - Policy & Templates Folder Missing

Hi TotalAnonymous 
Thank you for contacting the Microsoft Fabric community forum.

The issue isn't related to access changes or the folder being deleted. The error occurs because the query tries to select a row that doesn't exist at the referenced level in SharePoint.Contents.

In SharePoint Online, “Policies & Templates” is a folder inside the “Shared Documents” library, not a top‑level node. SharePoint.Contents returns the hierarchy as it exists in SharePoint. If the lookup is done at the wrong level (for example, at the site root instead of within the library), Power Query returns: Expression.Error: The key didn’t match any rows in the table.

Also, SharePoint.Contents requires an exact match on the Name column, including special characters like &. If the M code uses "Policies and Templates" or searches at the wrong level, the lookup will fail, even if the folder is visible in SharePoint.

To resolve this, update the M code to use explicit table filtering on SharePoint.Contents instead of direct row navigation.

let

   Source = SharePoint.Contents(

       " https://xxx.sharepoint.com/sites/xxxx",

       [ApiVersion = 15]

   ),

   SharedDocuments =

       Source{[Name = "Shared Documents", ItemKind = "DocumentLibrary"]}[Content],

   PoliciesAndTemplates =

       SharedDocuments{[Name = "Policies & Templates", ItemKind = "Folder"]}[Content],

   Marketing =

       PoliciesAndTemplates{[Name = "Marketing", ItemKind = "Folder"]}[Content],

   CoreOfTheCore =

       Marketing{[Name = "Core of the Core", ItemKind = "Folder"]}[Content]

in

   CoreOfTheCore

After updating the query to use table filtering, the refresh should work properly without needing to switch to SharePoint.Files.

I hope this information is helpful. If you have any further questions, please let us know. we can assist you further.

Best Regards.
Microsoft Fabric Community Support Team.
 

Answer : 

• Sometimes SharePoint metadata changes behind the scenes (e.g., internal IDs or library refresh), even if the folder looks accessible in the browser. This can break the navigation record in Power Query. 
   
• Instead of relying on the folder name in the navigation step, try using the Path column from SharePoint.Files or SharePoint.Contents and filter by the full path. This makes the query resilient to renames. 
   
• If the folder is intermittently missing in preview, it could be due to throttling or sync delays. Add retry mechanism via a parameterized query or refreshing after a short interval can resolve it. 
   
• Check if the folder is part of a recently archived or moved document library. Even if the URL works, the API may not return it until indexing completes. 
   
• If performance is a concern with SharePoint.Files, you can still use it but apply an early filter on the Folder Path column before expanding. This limits rows and keeps refresh time reasonable. 
   
• Finally, confirm that your credentials are set to Organizational Account and not cached incorrectly. Re-authenticate if needed. 

Hi TotalAnonymous 

I wanted to check if you’ve had a chance to review the information provided. If you have any further questions, please let us know. Has your issue been resolved? If not, please share more details so we can assist you further.

Thank You.

Hi TotalAnonymous 

We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank You.