Business Central Integration

OData integration between Storeman and Microsoft Dynamics 365 Business Central for master and operational data exchange.

Role: Backend / Integration Developer

Location context: India

Overview

Integration layer between the Storeman application and Microsoft Dynamics 365 Business Central to exchange master and operational data through OData-based APIs.

Challenge

Warehouse operations and ERP master data had to stay synchronized without manual re-entry or inconsistent records across systems.

Approach

Implemented authenticated OData integrations with explicit entity mapping, request/response handling, and iterative debugging of sync failures.

Key contributions

Developed backend API integration with Business Central
Worked with OData endpoints for retrieving and synchronizing business data
Implemented authentication and authorization for API communication
Mapped Storeman entities with Business Central entities
Worked on commodity, vendor, location, and other master-data integration requirements
Debugged API requests, responses, and integration failures
Updated application business logic based on Business Central requirements

Key features

OData-based ERP integration
Master data synchronization
Bearer-token authenticated API communication
Entity mapping between Storeman and Business Central
Integration failure debugging and recovery

Technology stack

Backend: Ruby on Rails
Database: MySQL
Integrations: Microsoft Dynamics 365 Business Central, OData APIs
Other: Bearer-token authentication, API testing tools

Technical challenges

Cross-system data mapping

Problem: Storeman and Business Central use different entity structures for the same business concepts.

Solution: Explicit field mapping and validation on the Rails integration layer.

Integration failure debugging

Problem: OData failures required careful inspection of auth, payloads, and endpoint behaviour.

Solution: Request/response analysis and targeted fixes across commodity, vendor, and location workflows.

Timeline

Integration work across multiple release cycles

Enterprise ERP integration — no credentials or private endpoints are published.