| This Help Center article is relevant to customers using the Event Lead Management system only.
If you are using the Event Lead Management system with the Demand Acceleration Platform, see Using Outbound Forms.
After connecting the Event Lead Management system with your Microsoft Dynamics 365 instance, you can add the integration to your Event. This article explains how to configure the settings and map fields to enable lead flow into Microsoft Dynamics 365.
| You need to have 1) connected your Microsoft Dynamics 365 account with the Event Lead Management system, and 2) have finalized the setup of your Event form - before setting up an integration on your Event.
|Connecting the Event Lead Management system to Microsoft Dynamics 365|
In this article
Add a Microsoft Dynamics 365 integration to an Event
| This step needs to be repeated with each Event that will create Microsoft Dynamics 365 leads.
Duplicating an existing Event that already has a Microsoft Dynamics 365 integration will duplicate the setup.
1. In the Events dashboard, open an Event.
2. Select Setup integrations.
3. Select Dynamics 365 and click Add.
4. Define how you would like data to be updated in Dynamics 365. Read more about the behaviour settings in Integrations & Duplicate Handling.
If business card scanning is enabled for your Event, determine which source should be used to fill a Microsoft Dynamics 365 Lead Property, in case the transcription and the form values are different.
5. Proceed to map your fields and click on Save changes once finished. Fields set to Unassigned will not be filled with any data.
A note on Match and Mismatch labels
The label displayed next to each mapped field indicates whether the mapped field data types are the same. For example, a string field mapped to a string field is the same data type and will display a Match label.
Different data types that are mapped together will display a Mismatch label. This will not prevent you from saving the integration setup because certain data types are compatible despite them not being the same - for example, a string field can receive data from a number field.
Some field types are not compatible and may cause leads to be rejected by the integrated system, for example a datetime field cannot receive data from a boolean (ie. 0 or 1) field.
The Mismatch label simply serves as a prompt to double check that the mapping is accurate. If the fields are confirmed as compatible, the Mismatch can remain in place.
Testing the Microsoft Dynamics 365 integration
| It is crucial to confirm that each test lead has been successfully received, properly routed and is complete within Microsoft Dynamics 365 - prior to your Event.
It is advisable to send numerous test values using different data capture methods (ie. business cards and badges if these will be used at your Event). This will minimize the risk of error during an Event when lead data is incoming.
If you don't have access to Microsoft Dynamics 365, collaborate with your system admin to confirm that test lead(s) have been received.
1. In the mobile app or webform - Submit a test lead.
2. In the Event Lead Management dashboard - Navigate to the Event and check the lead has been received. Reference the Integrations Logging Page to confirm no errors have been reported (and to help with troubleshooting, if needed).
3. In Microsoft Dynamics 365 - Login to home.dynamics.com, click on the Dynamics 365 app and navigate to Leads (in the Sales menu). Check that the lead has been received.
The Microsoft Dynamics 365 integration has been added to your Event.