Dynamics 365 BC Functional & Technical Consultant
Budget: ₹400 – ₹750 INR
I’m looking for a seasoned Dynamics 365 Business Central developer (minimum two years in the field) to take ownership of our solution design work. The immediate priority is to customise existing Business Central features: review what we already have, clean up any technical debt, and then create new customisations where gaps appear.
You’ll spend most of your time writing clean, well-structured AL (and the occasional C/AL) code, exposing or consuming web services, and building solid API connections to the other systems in our stack. Along the way you’ll collaborate with finance, operations, and our in-house IT team to refine requirements and validate your work. After go-live, I’ll still count on you for post-deployment support—root-cause analysis, quick fixes, and iterative improvements.
To fit smoothly into this role you should already be comfortable with:
• Dynamics NAV / Business Central architecture and development patterns
• AL / C-AL syntax, extensions, and events
• Web services, OData, and RESTful API integration
• Troubleshooting and communicating findings clearly to non-technical stakeholders
If this aligns with your background and you’re ready to dive into both legacy reviews and fresh module work, let’s talk about next steps and timelines.
You’ll spend most of your time writing clean, well-structured AL (and the occasional C/AL) code, exposing or consuming web services, and building solid API connections to the other systems in our stack. Along the way you’ll collaborate with finance, operations, and our in-house IT team to refine requirements and validate your work. After go-live, I’ll still count on you for post-deployment support—root-cause analysis, quick fixes, and iterative improvements.
To fit smoothly into this role you should already be comfortable with:
• Dynamics NAV / Business Central architecture and development patterns
• AL / C-AL syntax, extensions, and events
• Web services, OData, and RESTful API integration
• Troubleshooting and communicating findings clearly to non-technical stakeholders
If this aligns with your background and you’re ready to dive into both legacy reviews and fresh module work, let’s talk about next steps and timelines.