How do I install and configure Mobius Connect for Dynamics 365 Integration?

Installation

To install the Mobius Connect for Dynamics 365 Integration, follow the instructions below. Note that the steps and screen shots are from a machine that already had the .NET Framework installed.

  1. Go to the installation page: http://deployment.mobius-connect.com/Dynamics365Integration/ 


    2.  Download the Dynamics 365 Extension

Right click the link and choose "save link as"



    3. Click Install.

The installation creates a Mobius Connect for Dynamics 365 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.

4. Upload the Mobius Connect Extension for Dynamics 365.    

The extension needs to be uploaded through the Sandbox account, then it can be deployed into production from there.


To upload an extension into production, open up the Extension Management screen and navigate to Manage > Upload Extension

 Once the extension is installed you should be able to search for "Mobius-Connect" and find the following Extension.

Logging In

The first time you run the application, you will be prompted for both your Dynamics 365 and Manage credentials. They will be retained on the Login screen for your convenience when you run the application the next time.

 

  1. Enter the following Dynamics 365 information in the Login screen:  

  • OData URL: URL representing the root of the OData web service.

  • Company ID: This is the Dynamics 365 company database. 

  • Credential Type:

  • Username & Password:  If using Windows Authentication as the Credential Type, Username & Password are not required. If connecting to Dynamics 365, Username & Password are required. 

  1. Enter the following ConnectWise Manage information in the Login screen: 

  • Site: The domain name of the Manage site. For example, “connectwise.mycompany.com”. 

  • Company ID: Your company database ID as assigned by Manage

  • Auth Type: Select the method of Authentication setup in ConnectWise Manage Configuration


    • MemberImpersonation: If using MemberImpersonation AuthType, enter your Member, Integrator User, and Integrator Pass

    • APIKey: If using APIKey AuthType, enter your Public Key and Private Key

  1. Save Password: Check this box if you would like your Dynamics 365 and Manage passwords saved for the next time you run the application.

  2. Click Login

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.

  1. Not all Endpoints have been mapped.

  2. At least 1 endpoint failed to validate. Would you like to save a log?

  3. Validation PASSED

This validation can also be run manually after the Dynamics 365 Endpoint Mapper has opened by clicking the Validate button. To begin mapping to exposed Dynamics 365 endpoints, click to select the Dynamics 365 Endpoint for each required Dynamics 365 Interface.

As you populate the  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. 

Did you find it helpful? Yes No

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