#12064 Support SharePoint paths containing hash and percent characters
SharePoint connector now supports file paths containing hash and percent characters by adding separate decoded-path APIs backed by ResourcePath endpoints, with a new REST Base Folder Path Format setting to control URL decoding behavior.
- 13files
- 8AL files
- 8objects
Pull request · merged into main (BC30) on 2026-10-07 by JesperSchulz · 13 files (+700 -23), 8 AL · feature · tier official · reviewed (checked by Opus)
What changed
- New decoded-path SharePoint Client APIs backed by ResourcePath endpoints handle names containing # and %
- The connector uses them for file upload, download, delete, listing and existence checks, and for folder operations
- New REST Base Folder Path Format setting defaults to URL (also for existing rows); Decoded Path keeps literal names like Reports%20Archive
- Existing URL-based public client APIs are unchanged and Graph accounts are not affected
- Attachment paths and filenames are never unescaped; only the base folder and the site prefix taken from the URL are decoded
- Behaviour changes for users or extensions.
AL objects touched
- Page 4580 “Ext. SharePoint Account”, External File Storage - SharePoint Connector: modified
- Table 4580 “Ext. SharePoint Account”, External File Storage - SharePoint Connector: modified
- Page 4581 “Ext. SharePoint Account Wizard”, External File Storage - SharePoint Connector: modified
- Enum 4580 “Ext. SharePoint Path Format”, External File Storage - SharePoint Connector: added
- Codeunit 4609 “Ext. SharePoint REST Helper”, External File Storage - SharePoint Connector: modified
- Codeunit 9100 “SharePoint Client”, System Application: modified
- Codeunit 9101 “SharePoint Client Impl.”, System Application: modified
- Codeunit 9110 “SharePoint Uri Builder”, System Application: modified
Context
- Work items: AB#647600, AB#651781, AB#651782
- Labels: AL: Apps (W1), AL: System Application, Team: Integrations
- Systems: platform, integration
- From the description: “This PR adds separate decoded-path SharePoint Client APIs backed by ResourcePath endpoints and uses them in the legacy connector”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).