To install the Mobius Connect for Dynamics NAV Integration, follow the instructions below. Note that the steps and screen shots are from a machine that already had the .NET Framework installed.
Go to the installation page: deployment.mobius-connect.com/DynamicsNAVIntegration
The installation creates a Mobius Connect for Dynamics NAV Integration desktop icon.
The application will open immediately after installation. You will be required to activate the integration with the license key file. Click “Select License File” to install your license file and activate the integration.
If you do not have a license file, please contact your ConnectWise Account Manager at AccountManager@ConnectWise.com.
Your passwords will be encrypted using Window's built-in cryptography system. Therefore, the saved password will only be allowed to be used by the currently logged in user on the same machine.
Connecting to OData Endpoints
Before you can begin using the integration you must map to the user defined OData endpoints. From the integration interface, navigate to Options > View Modules to open the Enabled Modules screen. Select the Endpoint Mapping Interface and click Configure Module.
When the Endpoint Mapping Interface opens, it will attempt to validate your mappings. There are 3 possible validation responses.
Not all Endpoints have been mapped.
At least 1 endpoint failed to validate. Would you like to save a log?
This validation can also be run manually after the NAV Endpoint Mapper has opened by clicking the Validate button. To begin mapping to exposed NAV endpoints, click to select the NAV Endpoint for each required NAV Interface.
As you populate the NAV Endpoint mappings, validation logic will run and check off the Valid? checkbox for each row. If a row does not check the Valid? checkbox, you can use the Validate button to generate a log containing details. In this case response #2 will display providing the option to save a log. Review of this log will indicate why the validation for a particular endpoint may have failed. Generally, this occurs when a field is missing from the endpoint’s Page object. See Additional OData Configuration for details on adding missing fields to an endpoint Page.
After completing the Endpoint mappings, it is recommended to use the Export Mappings button to store your defined mappings. This allows for quickly importing your mappings back into the integration using the Import Mappings button. This is useful in the event that the integration needs to be installed on a new workstation or reinstalled for any reason. We recommend storing your mappings.json export in the same location as the integration’s activation license.