A new knowledge base article has been published on our support portal.
Overview
This article shows how you can use the North52 business rules engine for Microsoft Dynamics 365/Dataverse and the Azure Maps Get Search Address API to set Latitude and Longitude based on the address details of a Lead. It replaces the North52 GeoCodeBing function which has been discontinued by Microsoft.
North52 Decision Suite Solution
The North52 Decision Suite solution works like this:
- A Formula is set up on the Lead table which executes when address fields are changed:
- It calls the Azure Maps Get Search Address API using the CallRestAPI function and the address details
- JSON information is returned containing the Latitude and Longitude details
- North52 parses the JSON information and updates the Latitude and Longitude fields on the Lead table