Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Overview 

DBSync's Microsoft Dynamics NAV connector allows you to integrate your front, and back-office, applications to streamline and automate your business processes. 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 applications - such as MSCRM, Salesforce, SkuVault and various other databases.

DBSync's MS NAV connector allows you to move data in, and out, of the Microsoft Dynamics NAV application. This connector connects directly to your MS Dynamics NAV instance. 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 must:

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

Connector Configurations

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 represents parameters required for opening the connection to NAV user instance.

Property

Description

Required

Username

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

Yes

PasswordThe password for the user of MS NAV instance that has to be connected with.Yes
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.


Yes

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

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

Uses Of MSCRM Online Connector

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

DBSync's MS Dynamics NAV connector only supports 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. 

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

A: Yes. This connector supports both versions.

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 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: At times, Web Services that are exposed either cannot be imported or ETL tools cannot interpret the metadata. This may cause ETL tools to fail. With our Java Adapter extensions, we can handle many of these cases very efficiently.


  • No labels