Connecting a document management system with ERP and Microsoft 365
Before: Documents, their metadata and approvals lived separately – in the DMS, ERP, SharePoint and SQL – and handoffs between systems were hard to keep consistent.
What was done: The systems were connected through a shared integration layer: document data is entered only once, and approvals and business-system actions are linked automatically.
Now: Document and business processes work together, and you can always see who did what and when as data moves between systems.
Problem
The systems could each perform their local task, but the handoffs between the DMS, ERP, SharePoint, Microsoft 365 and SQL were difficult to keep consistent.
Existing systems
- Document management system
- ERP / Business Central
- SharePoint
- Microsoft 365
- SQL Server
Constraints
- The integration had to respect existing system boundaries and identity-aware permissions.
- The legacy DMS exposed extension limits that required additive, scoped changes.
- Customer workflows, internal endpoints, proprietary binaries and raw SQL were excluded from public copy.
Solution architecture
Custom C# handlers and integration steps connect DMS and SharePoint operations with ERP-related workflow hooks and SQL/API boundaries. A separately scoped legacy-DMS extension adds traceable audit and reporting procedures with guarded validation.
Text alternative
- Business Central
- DMS
- SharePoint
- SQL
- Integration layer
- Workflow
- Power BI / AI
Implementation
The implementation connected document metadata, workflow handoffs and business-system actions through a dedicated integration layer. The legacy-DMS work used additive audit/reporting procedures and production-safe validation with rollback-minded change control.
Technologies used
- C# / .NET
- Document management system
- SharePoint
- Business Central
- SQL Server
- REST / HTTP
Outcome
- Connected document and business-system workflows through a dedicated integration layer.
- It is now visible who did what and when as data moves between systems.
- Extended a legacy DMS with additive audit and reporting support without exposing its internal platform details.
Lessons / reusable pattern
- The integration layer should make boundaries and failure handling explicit instead of hiding them in product-specific configuration.
- Legacy platforms can be extended safely when the change is additive, scoped and validated with a rollback-minded procedure.