Microsoft ERP Dynamics API Integration
Budget: $250 – $750 USD
My Microsoft Dynamics ERP environment needs a robust two-way API integration with a separate, already-running application. The goal is to automate the exchange of customer, financial, and inventory data so both systems stay perfectly in sync without manual intervention.
What I have
• Microsoft Dynamics ERP (core Finance & Supply Chain components active)
• Full API documentation for the external app
• Access to test and production instances on both sides
What I need from you
• Design and build the integration layer using the most appropriate Dynamics tools—OData services, Custom Connectors, or Azure Logic Apps—while respecting existing security policies and rate limits
• Map and transform customer, financial, and inventory entities between the two data models
• Implement error handling, logging, and retry logic so no transaction is lost
• Provide step-by-step deployment notes plus concise user-level documentation
Acceptance criteria
1. Creating, updating, or deleting a record in either system is reflected in the other within the agreed polling/window.
2. All three data domains (customers, financials, inventory) pass consistency checks with zero data loss in a controlled test cycle.
3. Clear rollback procedure documented for every release.
If your background includes hands-on work with Dynamics 365 Finance/Supply Chain integrations, RESTful APIs, and Azure middleware, this should feel familiar. Please outline your proposed approach and estimated timeline when you reply.
What I have
• Microsoft Dynamics ERP (core Finance & Supply Chain components active)
• Full API documentation for the external app
• Access to test and production instances on both sides
What I need from you
• Design and build the integration layer using the most appropriate Dynamics tools—OData services, Custom Connectors, or Azure Logic Apps—while respecting existing security policies and rate limits
• Map and transform customer, financial, and inventory entities between the two data models
• Implement error handling, logging, and retry logic so no transaction is lost
• Provide step-by-step deployment notes plus concise user-level documentation
Acceptance criteria
1. Creating, updating, or deleting a record in either system is reflected in the other within the agreed polling/window.
2. All three data domains (customers, financials, inventory) pass consistency checks with zero data loss in a controlled test cycle.
3. Clear rollback procedure documented for every release.
If your background includes hands-on work with Dynamics 365 Finance/Supply Chain integrations, RESTful APIs, and Azure middleware, this should feel familiar. Please outline your proposed approach and estimated timeline when you reply.