How do I configure Dynamics NAV for the Mobius Connect Integration?

Dynamics NAV Configuration

The integration requires a collection of OData Web Service “endpoints” to be exposed in order to function. OData is a web service protocol that allows the integration to read and write data to the Dynamics NAV database and must be activated using the Dynamics NAV Administration tool. 

OData Setup

OData Services Activation

  1. Ensure OData Services is enabled. This checkbox must be checked.

  2. Note the Port value. This will be required in the URL to access exposed OData endpoints.

  3. Edit button to enable editing if OData Services is NOT enabled.

Exposing OData Endpoints

After OData Services have been enabled, Dynamics NAV must have the following list of endpoints exposed. In the Dynamics NAV client the Web Services interface can be opened by navigating to Departments > Administration > IT Administration > Services > Web Services. Create a new “Page” Object Type for each Object ID in the following table and ensure that each new entry has the Published column checked. The Object Name represents the interface to be exposed. The Service Name can be any URL safe value that represents the interface being exposed. Each defined Service Name should be unique to the Object Name.

OData Endpoint Entry Example

The following screenshot illustrates an example entry for Object ID 43, Sales Invoice.

The Service Name of “ARInvoice” will be applied to the OData URL upon publishing. Confirm that the OData Web Service is working by navigating to the OData URL in your browser.

Additional OData Configuration for NAV

Depending on the Dynamics NAV version and/or release, there may be additional fields that need to be added to the “Page” from within the Dynamics NAV Development environment. The integration requires “mapping” to all required user defined endpoint service names before any data can be transferred into Dynamics NAV. This Endpoint Mapping interface attempts to validate the available fields for each endpoint and will log any issues if they exist. See Integration Configuration, for details on the integrations 

Endpoint Mapping Module.

As an example, if your General Ledger Entries endpoint (object ID 20) does not have the “External_Document_Number” field available, it will need to be added using the Dynamics NAV Development Environment. Open the NAV Development Environment and open the proper database by navigating to File > Database > Open

Select the proper Database Name and click OK. This should open the Object Designer. If the Object Designer is not visible it can be opened by navigating to Tools > Object Designer. 

Make sure the “Page” Object Type is selected then find the Object Name or ID needed (in this case General Ledger Entries, ID 20). Select the row and click Design to open the Page Designer.

Select the first available field record then Navigate to View > Field Menu to open the Field Menu list.

Scroll until the Field necessary is found (in this case External_Document_Number), select the row, and click OK. Click Yes to the Confirmation prompt to add the field(s) that is selected. Navigate to Tools > Compile to update the Dynamics NAV database to complete adding the missing field to the Page.

Dynamics Web Service Access

(This step is optional.) 

You will need to enable a Web Service Access Key for the Dynamics User that will be used to authenticate with the Dynamics web services. Open up the User Card for the desired Dynamics User and click the ellipsis on Web Service Access to generate a key.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.