Next, we need to setup the link to Clever Dynamics Azure based web service that enables the different agent integrations that are supported.
Search for ‘Integration Setup’
Create a new record if one does not exist and set the fields on the page as follows
Note the 102 is the version of the endpoint which we increment when adding or changing a specific shipping agent interface. You may be asked to enter a later number than sai102.
Sender ID: CLEVER_DYNAMICS
File Delimiter: , (Comma)
Modification Offset (Seconds): 2
In addition, you have the option of getting notifications when integration messages fail. If you require this then set the following fields
Send Processing Error : On
Notification Type : SMTP
Notification Sender : the email address these messages are sent from
Notification Recipients : the email addresses these messages are sent to
Platforms & Platform Versions
While still on the Integration Setup page select the Navigate, Platforms option from the action bar.
You should immediately see a page similar to the screenshot below. The records for the different shipping agents have been created automatically when the Integration Setup page was completed. Seeing these records means your Business Central instance is correctly communicating with the Azure Web Services published by Clever Dynamics.
Although it's not critical, for each of the shipping agents listed you can select Actions, Versions from the action bar and see the API versions we support for each company.
These versions will allow you to seamlessly ‘upgrade’ when the different shipping agents change the specification of the API the Clever Shipping Agent Integration communicates with. As those API’s change they should increment the version, Clever Dynamics will publish a version supporting their new version, this integration will pull down the option of that new version and then you can test and go with no downtime.