NAV Web Services Integration The Old Way Text

NAV Web Services

Integration: The “Old” Way

Text Files • May require manual steps to export, import, convert, and transmit files. • Complex mapping of file formats. • Usually scheduled process, not real time synchronization. • Transmitting system does not receive immediate feedback if errors occur. • Receiving system typically has to deal with invalid data.

Database connection • Bypasses application logic and calculated Flow. Fields. • Security risks of exposing database to other systems, Internet. • Additional programs to validate and apply data. Same issues as text files.

Integration With Web Services

What is a Web Service? • An interface to communicate with other computers over a network. • Methods for sharing data and running application code. • Hides the inner workings from the clients accessing the service. • Provides options for encrypting and securing data. • Platform independent common standards.

Sharing Data Securely Dynamics NAV Web Service Other System Web Service

NAV Built-In Web Service Types

SOAP • Standard Object Access Protocol • One of the most common types of web services. • Best suited for transactional processing. • High overhead, slow performance for large datasets.

OData • Newer protocol standard. • Faster performance, better suited for large datasets. • Used by Excel connector, Power BI, and other reporting tools.

OData API • New feature starting with NAV 2018. • Most common data entities are mapped by default. • Integration with other toolsets to create “codeless” integrations. • Currently in beta status.