ODATA action method and Custom services in D365F&O
I wouldn't say that "When we found the Logic which is not possible through ODATA then we go for Custom services". I can't think of anything that you couldn't write in an OData action but you could in a custom service.
The typically reason for choosing an OData action is that the logic is related to an entity. For example, you can create a transfer order with InventTransferOrderHeaderEntity and the ship the order by the ship action. It could be a custom service, but this is easier to discover and use.
Note that OData actions are also exposed in dataverse virtual entities, therefore they can be easily used through the Dataverse connector.
Was this reply helpful?YesNo
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.