Finance | Project Operations, Human Resources, ...

Odata support inbound (part 2)

(0) Share

Report

Posted on by CU10121822-0

990

Hi all,

To continuing the earlier thread…

https://community.dynamics.com/forums/thread/details/?threadid=d63a56c8-c0a3-f111-b8de-6045bda97caf

Thanks to every one to reply but still I explored more and come to the conclusion

In D365FO, OData is the standard REST-based API used for inbound integrations, it means

1.External systems call Odata endpoints to perform CRUD operations on public data entities.

2.It’s ideal for real-time, low-volume integrations

3.It cannot be used for outbound pushes — for that, we need Business Events, DMF exports, or middleware like Power Automate, Logic Apps etc.

Am I correct?

Pls advise, thanks

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (2)

Answers (0)

Sort by

CU10121822-0 990 on at

Like (0)

Report
Copy link

Link copied!

I exploded more and trying to set an example like

Suppose the external system where sales reps capture orders. These orders must be created in D365FO in real time.

Here the external system consumes D365FO’s OData endpoint to insert data in D365FO.

For example -
POST https://<my dev env>.cloudax.dynamics.com/data/SalesOrderHeaders
Authorization: Bearer <token>
Content-Type: application/json
{
CustomerAccount: "US-001",
DeliveryDate: "2026-08-30",
SalesOrderNumber: "External007"
}

Now D365FO validates the request, creates the order, and returns the Sales Order ID to external system for tracking.

Am I correct?
Pls advise, thanks

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

CU-1234529-002 335 on at

Like (0)

Report
Copy link

Link copied!

Hi, OData isn't "inbound only" it's synchronous and caller-initiated, in both directions:
External system can POST/PATCH to write data into D365FO (like your example)
External system can also GET to pull data out of D365FO
What OData can't do is let D365FO push data out on its own when something happens. For that, you need:
Business Events real-time, event-driven push (order created → notify subscriber instantly)
DMF scheduled/bulk file-based export
Middleware (Power Automate, Logic Apps) usually sits on top of the above to route data further
So the better distinction is: OData = pull-based, external system decides when to call. Business Events = push-based, D365FO decides when to notify.
Your example flow is correct. Two small fixes:
Sales order numer is normally auto-generated by a number sequence you'd read it back from the response rather than pass it in
Check the entity's actual field names via GET…/data/$metadata before finalizing your payload (e.g. delivery date may not literally be Deliver date)
Thanks,

Was this reply helpful? Yes No