Role Overview
We are seeking an experienced Microsoft Dynamics 365 Business Central Developer for a 12-month contract to support the modernisation of our Business Central integrations.
The primary objective of this role is to assess and refactor existing OData V4 integrations into supported Microsoft Dynamics 365 Business Central standard APIs or appropriately designed custom APIs. This will be the core focus of the position, where the majority of the successful candidate’s time and effort will be directed.
The successful candidate will work closely with internal engineering teams, functional consultants, and integration stakeholders to ensure that the revised API architecture is secure, scalable, maintainable, and aligned with Microsoft best practices.
In addition to the API assessment and refactoring work, the role will also involve supporting Business Central-related business-as-usual requests as they arise, including troubleshooting, minor enhancements, and general development support. These BAU responsibilities are secondary to the primary integration objective, but the candidate is expected to support them as part of maintaining a stable and well-functioning Business Central environment.
Primary Project Objective
The developer will review the organisation’s existing Business Central OData V4 services and determine the appropriate migration approach for each integration.
This includes:
- Migrating suitable integrations to Microsoft standard Business Central APIs.
- Designing and developing supported custom APIs in AL where standard APIs do not meet business requirements.
- Reviewing existing endpoints, field mappings, consuming applications and integration dependencies.
- Identifying compatibility, performance, security and data integrity risks.
- Supporting the transition and controlled decommissioning of legacy OData services.
Key Responsibilities
- Review and assess existing Business Central OData V4 services, published pages, queries and integration dependencies.
- Create an inventory of existing endpoints, consumers, data mappings and business processes.
- Identify opportunities to replace existing OData services with Microsoft standard Business Central APIs.
- Design and develop custom API pages or API queries using AL where standard APIs are insufficient.
- Develop and maintain Business Central extensions using AL.
- Refactor existing integrations while minimising disruption to connected applications and business operations.
- Define API request and response structures, field mappings, validation rules and error-handling standards.
- Implement secure API authentication and authorisation using OAuth 2.0 and Microsoft Entra ID.
- Apply appropriate API versioning and backward-compatibility practices.
- Troubleshoot integration, data consistency and performance issues.
- Conduct unit, integration, regression and performance testing.
- Support sandbox testing, User Acceptance Testing and production deployment.
- Maintain source code using Git and support deployment through suitable CI/CD processes.
- Prepare technical documentation, including API specifications, field mappings, deployment procedures and support guides.
- Provide knowledge transfer to internal development and support teams.
- Ensure all development follows Microsoft Business Central development standards and avoids unsupported modifications to the base application.
Required Experience and Skills
- At least 3 to 5 years of hands-on Microsoft Dynamics 365 Business Central or Dynamics NAV development experience.
- Strong proficiency in AL development and the Business Central extension framework.
- Proven experience designing and developing Business Central custom APIs.
- Practical experience migrating, refactoring or replacing OData V4 integrations.
- Strong knowledge of:
- Microsoft Dynamics 365 Business Central standard APIs
- Business Central API v2.0
- API pages and API queries
- OData V4 web services
- Business Central tables, pages, codeunits, queries and events
- OAuth 2.0 and Microsoft Entra ID authentication
- REST APIs and JSON-based integrations
- Experience working with Business Central online environments, sandboxes and extension deployment.
- Experience using Visual Studio Code, Git, Postman and Azure DevOps or equivalent tools.
- Strong debugging, troubleshooting and performance-optimisation skills.
- Ability to analyse existing integration code and identify downstream dependencies and risks.
- Good technical documentation and communication skills.
- Good written and verbal English.
- Must be based in Malaysia and able to collaborate effectively with regional stakeholders.
Preferred Qualifications and Experience
- Microsoft certification related to Dynamics 365 Business Central development.
- Experience integrating Business Central with ERP, finance, e-commerce, warehouse, CRM or middleware platforms.
- Experience with Azure Functions, Logic Apps, Service Bus or other Azure integration services.
- Knowledge of Business Central webhooks and event-driven integration patterns.
- Experience with asynchronous processing and high-volume integrations.
- Experience working with multi-company or multi-environment Business Central implementations.
- Familiarity with automated testing using the Business Central test framework.
Expected Deliverables
The developer will be expected to deliver:
- A technical assessment of the existing OData V4 integrations.
- An inventory of existing endpoints, consumers and dependencies.
- A recommended API migration, prioritisation and deprecation plan.
- Replacement of suitable OData services with Microsoft standard Business Central APIs.
- Development of custom APIs where standard APIs do not meet business requirements.
- Updated technical mappings and interface specifications.
- Support for downstream teams updating consuming applications.
- Functional, integration, security and performance test cases and results.
- Deployment and rollback procedures.
- Production implementation support.
- Technical documentation and knowledge-transfer sessions.
Candidate Profile
The ideal candidate is not only an experienced AL developer but also has strong integration and API design capabilities. The candidate should be comfortable reviewing legacy integrations, recommending appropriate modernisation approaches and implementing maintainable solutions without unnecessary customisation.
Contract Duration
This is a 12-month contract position, with the possibility of extension depending on project requirements and performance.