Configuration and Usage
For configuration and usage of this connector please go to the Microsoft Dynamics 365 guide.
No action needs to be taken for customers on cloud deployments hosted by Smart Communications as the environment should already have this connector installed. If you need a licence please contact your Customer Service Manager.
For customers on self-hosted deployments (either in the cloud or on-premise), consider the following requirements before installing or upgrading this extension:
You must have administrator/elevated permissions to a suitable web server to install the service.
Ensure you have a compatible version of the connector with your current SmartIQ version (Connector and SmartIQ should match versions)
️ Licence key required
You must have a valid license key to enable the MS Dynamics 365 module. If you do not have one, please contact your SmartIQ representative.
This connector has now been implemented as a service which can be registered to an instance which behaves in a similar fashion to the previous versions. This is referred to as the Dynamics Service. The Dynamics Service needs to be hosted somewhere accessible only by the SmartIQ platform.
Remove the existing Extension if deployed as a dll (all upgrades previous to v13). This may include removing entries in the appSettings.json as well as the dll’s from directories.
.Net Framework 4.8 has to be installed on the machine and registered for usage within IIS.
These steps are almost identical to installing Manage and Produce in IQ12 (as they ran on .Net Framework).
- Create a new site in IIS and define a port. For example, port 8080. This can run over http or https.
- Extract the files from the Dynamics Service zip archive to the site root.
- Create a .Net Framework App Pool for the service. Do not use the same application pools that are already allocated to Manage and Produce.
- Convert to an Application selecting the App Pool from #3.
- With no other settings changes the service will have bindings to http://localhost:8080 as the
From your web browser navigate to
<serviceURL>/v1/CreateConnection/Metadata. For example, http://localhost:8080/v1/CreateConnection/Metadata which should return a metadata document. Anything else and you will need to troubleshoot the specific error in relation to requirements above.
If valid, the result will look like xml or json (browser decides what it will look like).
A Tenant Ops Api key is required to complete these steps.
For an information sheet on how to implement a Tenant Ops Api key and available endpoints, please contact Support.
This connector has the following url endpoints to be registered using the RegisterService endpoint in the Tenant Ops API | Register-Service :
Updated 3 months ago