web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Odata support only inb...
Finance | Project Operations, Human Resources, ...
Answered

Odata support only inbound

(0) ShareShare
ReportReport
Posted on by CU10121822-0 994

Hi team, as I have read in blogs about ODATA, and have small confusion between inbound and outbound.

 

What I understood, Odata only support the inbound not outbound. Because 

The external system consumes D365FO's OData endpoint and performs operations such as:


GET → Read data from D365FO
POST → Create data in D365FO
PATCH → Update data in D365FO
DELETE → Delete data in D365FO

 

I mean to say, The OData does not push data from D365FO to an external system. 

The external system must call D365FO's OData endpoint to consume it.

Am I correct?

.pls advise, thanks 

 

Categories:
Dynamics 365 Finance
I have the same question (0)
  • Verified answer
    CU-1234529-002 Profile Picture
    CU-1234529-002 337 on at

    Hi, your understanding needs a small correction. OData itself is neither strictly inbound nor outbound, it depends on who initiates the call.

    You're right that OData doesn't push data automatically, but it supports both directions:

    Outbound D365FO exposes OData endpoints, and an external system calls GET to read/consume data from D365FO. This is actually outbound from D365FO's perspective.

    Inbound  the external system calls POST/PATCH/DELETE to create or update data in D365FO.

    For pushing data proactively from D365FO to an external system, you'd use Business Events or Logic Apps  OData alone can't push, the external system must always initiate the call.

    So OData supports both inbound and outbound, just not push-based outbound. Thanks,

  • CU10121822-0 Profile Picture
    CU10121822-0 994 on at

    Hi, thanks for your clarity…

     

    As mentioned “Outbound D365FO exposes OData endpoints, and an external system calls GET to read/consume data from D365FO.”

     

    Here my question is, When external system calls GET to read the data from D365FO, It's actually called Outbound . If yes why?

     

     

    And for other calls like POST, PATCH, DELETE , it's called Inbound.

     

    Still I have confusion on Outbound.

     

    Pls advise, thanks 

     

  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 307,015 Super User 2026 Season 2 on at

    According to my definition of inbound versus outbound, it is about the direction. When you have Dynamics 365 and an external application, the external application can read data from Dynamics 365 for the purpose of importing data. In this scenario, from the point of view of the external application, this is an inbound integration. 

    In case the external application will use POST or PATCH it will send data to Dynamics 365. For the external application, this is outbound.

    In case you need to push data from Dynamics 365, you can use trigger options like data events, alerts with business events to send an event externally. An external endpoint, like the external application, but also a tool like Logic Apps can receive the event, checks what exact data is required, GET potentially additional data and then complete the file to be imported by the external application or to be sent to the external application from Logic Apps. There are more tools that can be used as middleware.

  • CU10121822-0 Profile Picture
    CU10121822-0 994 on at

    Thanks Andrea,

     

    Pls let me know, is my assumptionn is correct?

     

    Pls advise, thanks 

  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 307,015 Super User 2026 Season 2 on at

    When you read my reply, you can conclude that your assumption was not correct. You are correct that OData is not directly pushing information. OData is a standard for REST APIs.

    You also correctly listed the actions supported by OData (e.g. GET, POST).

    You can call OData actions from external applications, but, as mentioned in my reply, also by other triggers. Dynamics 365 F&O has the business event and data event technology as a trigger mechanism. Middleware or external applications can also have their triggers and execute OData calls.

  • Verified answer
    CU-1234529-002 Profile Picture
    CU-1234529-002 337 on at

    Please note that the inbound outbound is not related to like methods Get/patch or endpoints

    Inbound - data read from external third party application and send it to D365FO

    Outbound - data pass from D365FO and send it to Third party application

    Thanks 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 361 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 329 Super User 2026 Season 2

#3
CU10121822-0 Profile Picture

CU10121822-0 324

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans