When a Production database is restored to a UAT/Sandbox environment in Dynamics 365 Finance & Operations, SharePoint document management configurations—including those used for electronic reporting such as MT101 bank file generation—remain pointing to the Production SharePoint site.

As a result, non-production environments may still interact with Production SharePoint locations, which introduces a critical risk. In a recent scenario, a test payment executed in a UAT environment was processed through the bank because the SharePoint configuration still referenced the Production site.

Currently:

• The standard LCS database restore process does not allow execution of post-restore scripts automatically.
• There is no ability to exclude specific tables (e.g., DocumentDocumentURI) from the refresh.
• Customers must manually update SharePoint document links after each restore.

This creates a dependency on manual intervention and introduces a high risk of human error.