Kategorien durchsuchen
Entdecken
Fiverr Pro
Deutsch
$
USD
I will fix business central integrations and migrate soap and odata to apis
A Vohra
Über diesen Service
I fix Business Central integrations that break when Microsoft removes old web services, and move them to supported APIs before they do.
What Microsoft is removing:
- API v1.0: gone since version 28 (April 2026)
- - SOAP on Microsoft's standard pages: version 29 (October 2026)
- - OData on the same pages: version 30 (April 2027)
If your webshop, WMS, EDI tool, bank feed, Power BI report or custom app uses one of these, it stops when your environment updates.
What I do:
- List every at-risk web service and the system that calls it
- - Get a broken integration running again, with 1-day delivery
- - Move integrations to API v2.0, custom API pages (AL) or OData actions, with OAuth
- - Update the calling code (C#, Node.js, Python, Power Automate) or brief your developer
- - Sandbox testing, deployment, Postman and Swagger docs
Not included: Business Central licenses, or changes inside another vendor's product.
I'm a Business Central technical lead with 6 years of experience, most of it on NAV and Business Central. I've moved integrations from SOAP to OData V4 and built OAuth API pages for external systems. 59 Fiverr orders, 100% on time.
Online and on-premises. Microsoft partners welcome.
Lerne A Vohra kennen
A Vohra
Software Developer, Business Central, Power Automate
- AusPakistan
- Mitglied seitJan. 2018
- ⌀ Antwortzeit4 Stunden
- Letzte Lieferung1 Jahr
Sprachen
Urdu, Englisch
Hi, I'm Ahmed. Business Central and Power Automate developer with 6 years of experience, most of it on NAV and Business Central, on-premises and online.
What I do:
- AL extensions and NAV to Business Central upgrades
- BC integrations with REST APIs: Shopify, payments, CRMs, accounting
- Moving integrations off SOAP, OData and API v1.0 as BC removes them
- Power Automate flows, approvals and custom connectors
- Invoice processing with AI Builder, posted to your ERP
- RPA for apps without APIs
59 orders delivered, 100% on time. Send me your process and I'll tell you how I'd build it.
Mein Portfolio
Meine weiteren Dienstleistungen im Bereich Software-Entwicklung
FAQ
Our integration broke after a Business Central update. How fast can you fix it?
Usually within a day of getting access. For SOAP, I copy the Microsoft page into an extension and publish it again, so the other system only changes the service name in its URL; then we move it to an API. For API v1.0, I move the calls straight to v2.0.
Which web services break in version 29, and which in version 30?
Version 29 removes SOAP on pages published by Microsoft, such as Customer Card or Sales Order. Version 30 removes OData on the same pages. API v2.0, custom API pages, queries and web services on your own extension pages keep working. Telemetry event RT0053 logs every affected call.
Our integration uses API v1.0. Is it affected?
Yes. Microsoft removed API v1.0 in version 28 (April 2026), so those calls fail once your environment is on version 28 or later. API v2.0 covers the same data with new IDs and field names. I move the calls and map the fields.
When will our Business Central online environment move to version 29?
Version 29 comes out in early October 2026 and reaches existing environments about a week later. Your admin can postpone the update until early March 2027. After a one-month grace period Microsoft forces it and can uninstall extensions that block it.
Will our Power BI reports or Power Automate flows break?
Power BI reports that read Microsoft pages published as OData stop in version 30 (April 2027); reports on API pages or queries keep working. Flows using the Business Central connector are fine, since it runs on APIs. Flows that call page web services over HTTP break. I move both.
Can you migrate without changing the other system?
Often, yes. If the other system can only send SOAP and nobody can change it, I put a small bridge on Azure Functions that accepts its SOAP calls and forwards them to the Business Central API.
Should we use API v2.0, custom API pages or OData?
API v2.0 when it already has the fields you need, such as customers, items, sales orders and invoices. A custom API page for your own fields or tables. An OData action to replace a SOAP codeunit. Microsoft says APIs are up to 10 times faster than SOAP.
We're on NAV or Business Central on-premises. Does this apply to us?
Only when you upgrade to version 29 or later. Older versions keep SOAP, so the integration work fits into your upgrade: I move the integrations before or during it.
What access do you need, and is our data safe?
A sandbox copy is best. You create a user or an Entra app for me and can remove it at any time, and I don't need production data to build and test. Partners can give delegated admin access. Don't send passwords in chat; we set up access together.
Can you work as a subcontractor for our Microsoft partner?
Yes. I work in your development environment or your customer's sandbox, follow your naming, object ranges and code analysis rules, and hand over the source code. You stay the customer's contact.
