You’re offline. This is a read only version of the page.
1,110
We are working on one of the project for our customer to develop plugin connectors (Integration Adapter), which would enable the end users to quickly integrate cloud and on premise applications. We are targeting to develop plugin connectors for Microsoft Dynamics NAV.
NAV supports both ODATA and SOAP Web services. So could you please guide us with which service should be used for future enhancement, ODATA or SOAP?. Which service should we use to do intergration?. Any pointers or reason will be helpful.
*This post is locked for comments
SOAP web services allow full flexibility for building operation-centric services. They provide industry standard interoperability. Windows Communication Framework (WCF) has supported SOAP services since its initial release in .NET Framework 3.0, and later releases of the .NET Framework have added additional support and default bindings to make it easier to build SOAP services using WCF.
The most common type of messaging pattern in SOAP is the Remote Procedure Call (RPC), where one network node (the client) sends a request message to another node (the server), and the server sends a response message to the client.
The OData standard is well suited for web service applications that require a uniform, flexible, general purpose interface for exposing create retrieve update delete (CRUD) operations on a tabular data model to clients. OData is less suited for applications that are primarily RPC-oriented or in which data operations are constrained to certain prescribed patterns. OData supports Representational State Transfer (REST)-based data services, which enable resources, identified using Uniform Resource Identifiers (URIs), and defined in an abstract data model (EDM), to be published and edited by web clients within corporate networks and across the Internet using simple Hypertext Transfer Protocol (HTTP) messages. OData services are lightweight, with functionality often referenced directly in the URI.
Whereas SOAP web services expose a WSDL document, OData web services expose an EDMX document containing metadata for all published web services.
OData is supported in PowerPivot, a data-analysis add-in to Microsoft Excel that provides enhanced Business Intelligence capabilities. PowerPivot supports sharing and collaboration on user-generated business intelligence solutions in a Microsoft SharePoint Server environment. For more information about PowerPivot, see http://www.powerpivot.com/.
The extensions to the Atom Publishing Protocol defined in the AtomPub extensions to the OData protocol documentation (which you can download here) describe how REST-based data services can enable resources, identified using URIs and defined in an abstract data model (EDM), to be published and edited by web clients within corporate networks and across the Internet using simple HTTP messages.
In addition to the AtomPub format, the OData implementation in Microsoft Dynamics NAV 2013 R2 also supports the JSON format, a somewhat less verbose format that may perform better in low-bandwidth environments.
Ref: http://msdn.microsoft.com/en-us/library/hh168269(v=nav.71).aspx
-Saurabh Shah
The Open Data Protocol (OData) is a web protocol that is designed for querying tabular data and provides you with an alternative to SOAP-based web services.
OData builds on web technologies such as HTTP, the Atom Publishing Protocol (AtomPub), and JavaScript Object Notation (JSON) to provide access to information from different applications, services, and stores. OData uses URIs for resource identification and commits to an HTTP-based, uniform interface for interacting with resources. This commitment to core Web principles allows for OData to enable a new level of data integration and interoperability across a broad range of clients, servers, services, and tools.
(MSDN)
In simple way Odata is a alternative and advance version of SOAP.
If you want to know the complete difference read below article.
odata is faster than soap, much better read performance. but with nav 2013 there is only read access, no write access. with nav2015 odata has also write acess (interesting for upgrade versions).
so when using nav2013 use odata for read and soap for write transactions.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (