Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview 

The DBSync's Microsoft Dynamics NAV connector allows you to integrate your front, and back-office, applications to streamline and automate your business processes and ensure . It ensures that your MS Dynamics NAV data is accurate, timely, and functional. As a Nav user, you can use this connector to integrate MS NAV with another On-demand, On-premise or SaaS-based application applications - such as MSCRM, Salesforce, SkuVault and various other databases.

DBSync's MS NAV connector allows you to move data into in, and out, of the Microsoft Dynamics NAV application. This connector connects directly to your MS Dynamics NAV instance and . It enables you to query, add, modify various types of records including quotes, sales orders, blanket sales orders, return orders, Invoices, credit memos, Items and much more.

Prerequisites

To establish a connection to Dynamics NAV, via DBSync NAV connector, the user has to do the followingmust:

  • Have a valid license to DBSync NAV connector, username and password to connect to DBSync iPaaS platform.
  • Access Have access to Dynamics Nav with valid username and password.

Connector Configurations

The DBSyncs DBSync's MS NAV connector instance represents a single NAV account, including login credentials. If a user wishes to connect to multiple instances, of the either sandbox/production, then, s/he must create a separate connection for each. The table below table represent represents parameters required for opening the connection to NAV user instance.

Property

Description

Required

Username

The username of the MS NAV instance which that has to be connected with.

yesYes

PasswordThe password for the user of MS NAV instance which that has to be connected with.yesYes
Base URL

Base URL is the web service URL that is generated from the NAV application in the following manner.

Navigate through

Administration→IT Administrators→General→ Lists→ Web service

SOAP URL format "http://WIN-73D0K4TTRC2:7047/DynamicsNAV80/WS/CRONUS%20New%20Zealand%20Ltd./Page/"

Copy the SOAP URL and paste it in the Base URL field of the connector page.


yesYes

After a connector is created within a project, set up the connector within the project. DBSync can then map to, and from, the systems which that are supported by our standard connector list and . It can use NAV connector to retrieve data from, or send data to, NAV Platform.

Click on the following link to know which link Connectors to learn about all connectors we support Connectorssupport.

Uses Of MSCRM Online Connector

The DBSync Microsoft Dynamics NAV connector can be used to:

  • Synchronize customer master databases with Microsoft Dynamics NAV.
  • Convert closed won opportunities to Invoice/sales orders MS Dynamics NAV.
  • Integrate e-commerce website orders to MS Dynamics NAV.
  • Integrate payments received from online payment systems for reconciliation.

Supported Versions

The DBSync's MS Dynamics NAV connector only supports only the following versions of Navision.

  • Microsoft Dynamics NAV 2016
  • Microsoft Dynamics NAV 2015
  • Microsoft Dynamics NAV 2014
  • Microsoft Dynamics NAV 2013

Frequently Asked Questions

Q: How does DBSync connect to MS NAV?

A: DBSync connects to MS NAV through Web Services. Services (and Pages or routines) should be exposed for other applications to consume it.

Q: What are the prerequisites for DBSync integration to work with MS NAV?

A: SOAP Web service of MS Dynamics NAV should be enabled enabled. 

Q: Is this connector available with on, On-demand and onOn-premise, versions of DBSync?

A: yes, Yes. This connector has the support for supports both the versions of DBSync.

Q: Does DBSync need to be installed on the same machine as that of MS NAV?

A: DBSync MS NAV adapter can be either configured on the same machine - where MS Dynamics NAV is installed - or, on a remote machine which that can access MS Dynamics NAV.

Q: What is DBSync SDK?

A: DBSync SDK allows you to write your own custom adapters and extensions. It can be deployed to your DBSync Integration Engine with processes you need to setup.

Q: Why do we need this additional coding?

A: Many At times, Web Services that are exposed either cannot be imported or ETL tools cannot interpret the metadata. This causes many other may cause ETL tools to fail. With our Java Adapter extensions, we can handle many of these cases very efficiently.