You’re offline. This is a read only version of the page.
Announcements
16
Hi all,
I’m working with Dataverse/Dynamics 365 SharePoint document management (server-based integration).
I want to store documents in different SharePoint sites (and potentially different document libraries) depending on the record’s Business Unit (BU).
When an Opportunity is created, I want the Opportunity’s Document Location to point to a BU-specific SharePoint site (e.g., BU-A → Site A, BU-B → Site B), instead of using the single default site/library created by the Document Management Wizard.
The entity (Opportunity) is enabled for SharePoint document management via the Document Management Wizard.
On Opportunity creation, I run a Power Automate flow that creates a sharepointdocumentlocation record (Document Location) and tries to set:
Parent Site or Location → a BU-specific sharepointsite record
Relative URL → e.g., Shared Documents/<some folder> (or I create hierarchical locations: library → BU folder → record folder)
Even though I create a Document Location pointing to the BU-specific site, the model-driven app still throws errors related to the default document library configured by the wizard, for example:
“Document library ‘’ has been renamed or deleted from SharePoint site ‘’. Rerun the document management wizard and try again.”
Also, if I try to set a path like Shared Documents/Test in Relative URL, I get an error that / is not allowed in folder names (so I understand I must create hierarchical document locations instead of using a slash path).
Is it supported to route document locations per BU to different SharePoint Sites (different sharepointsite) for the same Dataverse table (Opportunity) while still using the out-of-the-box Documents grid?
If yes, what is the recommended configuration/pattern to do this safely (wizard settings + creating sharepointsite and sharepointdocumentlocation records)?
Does the Documents grid always validate the wizard’s default site/library first (making a “default” library mandatory to exist), even if a record has a custom document location pointing elsewhere?
Are there any official docs or supported samples for “multiple SharePoint sites per entity based on BU” using server-based SharePoint integration?
Environment details (if helpful):
Platform: Dataverse / Dynamics 365 model-driven app
Automation: Power Automate creating sharepointdocumentlocation
Mapping: BU → SharePoint Site/Library
Any guidance, supported patterns, or documentation links would be greatly appreciated.
Thank you!
Share
Report
All responses (
Answers (
