Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
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.
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.
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.
In simple way Odata is a alternative and advance version of SOAP.
If you want to know the complete difference read below article.
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.
nav2013 supports only read access through ODATA and nav2013R2 supports read,write access , am i right?
yep, you are right.
if your question is answered, please verify. thx.
Business Applications communities