Navigate to destinations in Hightouch app and find Microsoft Dynamics 365.
Follow the OAuth flow.
Once successfully authenticated, you will be asked to enter your service URL.
To get your service URL, sign in to your Microsoft Power Apps.
Then, click the settings icon on the top right corner to open the settings sidebar.
Click on Developer resources
Copy the Web API endpoint then go back to Hightouch and paste the URL where it's required.
Finish creating your destination by pressing continue.
Before you set up a sync, we recommend you to skim through these concepts to gain an insight on how to effectively sync your data into Microsoft Dynamics 365.
Dataverse is the source of truth for your Dynamics 365 applications.
Microsoft Dynamics 365 destination will sync your data into the Dataverse which will then allows you to use the data directly in your Dynamics 365 applications.
For more information about Dataverse see Microsoft's documentation.
Record matching allows you to match queried data in Hightouch to rows in Dataverse.
GUID and alternate keys are the two ways to match your query results to rows in your Dataverse tables.
GUID is the auto-generated primary key in your Dataverse tables. You are allowed to use GUID to match query results in Hightouch with rows in your Dataverse tables by default.
Although GUIDs are available by default, we recommend the use of alternate keys
for record matching in your Hightouch syncs.
Alternate keys are custom unique identifiers that can be derived from one or more columns in your Dataverse table.
it's a flexible way to set up a unique identifier in your Dataverse table to be use for record matching between your query results in Hightouch and your rows in Dataverse.
In most case, you won't have access to Dataverse GUID in your external data warehouse for record matching so alternate keys are convenient solution.
In the Power Apps, navigate to tables in Dataverse.
Select the table you want to sync to. In this walk through, we will use the Account table.
Please make sure that you are always working on the correct environment in
Power Apps. If you haven't set up your environment yet, go to this
link
for more information. Here is an
article
from Microsoft on environment strategy.
Once you are in the table view, select keys to open the alternate keys view.
In the keys page:
(1) Click New Key then in the pop-up on the right, enter the configuration for the key you are about to create.
(2) Enter a label for this key. This label is the label that will be displayed in Hightouch's ID mapping section.
(3) Select a column that you want to use as an alternate key.
Note that alternate keys must be unique and must meet the requirements described in the Dynamics 365 docs. If you do not have a column that meets these requirements, you can manually add a column and use it. In our example below, We're using a column that we created called Custom External ID.
If you are creating a new column to be used as external ID, you may have to
backfill the new column first before they can be used to avoid accidental duplicates.
While you can use multiple columns to make a unique key in Dynamics 365, Hightouch
doesn't support multi-column alternate keys. These keys will not appear as
option in Hightouch.
(4) Once configured, hit save button to create the alternate key.
The created alternate keys will appear as options in the ID mapping section of your Hightouch sync configuration. They're ready to use.
You may have noticed that First Name and Last Name appear to be read-only in the destination side while Description is editable.
These read-only fields are fields that are marked as Business required in Dataverse.
This means that whenever you create a sync, you must send data for these fields.
The Microsoft Dynamics 365 destination will not automatically cast your data to the data types they are expected to be in your table in Dataverse. This means that you are responsible for casting them to the valid type they need to be in. The image below shows an example of fields we pulled from Dataverse along with their types. The icons on the left indicate the type of the column. As you may notice, there are icons with ?. This indicates that the type is either complex or unexplored by Hightouch. Reference the Dynamics 365 docs for more details on types.
You want to insert rows into table, but don't care if the data within each row remains up to date
Static data where each row is never updated, such as emails, events, etc.
To ensure syncs send each event, use a hash function for the event model's primary key . The hash should combine all columns, including member ID, timestamp, etc. See the event sync documentation for more information.
Insert has two configuration parameters:
Name
Description
Object
The table (Account, Contact, etc..) where the rows will be inserted into Dataverse.
Hightouch to Dataverse field mappings
Tells us how fields in your query results will be mapped to columns in your Dataverse table.
In this mode, selected columns from query results in Hightouch will update the columns of matching rows in your Dataverse table. For example, you could add an LTV column to an account. This mode doesn't create new rows for that account in your Dataverse. Instead, it updates the columns on existing matched rows.
See ID matching section in the prerequisites to learn how to match Hightouch query results to rows in your Dataverse.
This mode is good for the following scenarios:
You have rows in Dataverse that you want to enrich.
You want to continuously sync data from your warehouse but do not want to insert new rows to your table in Dataverse.
Update has three configuration parameters:
Name
Description
Object
The table (Account, Contact, etc..) where the rows will be updated into Dataverse.
Hightouch to Dataverse record matching
Tells us how to match queried records to rows in your Dataverse table.
Hightouch to Dataverse table field mappings
Tells us how fields in your query results will be mapped to columns in your Dataverse table.
To validate that your configuration is working, we highly recommend that your to run a test.
Click on Test button to open the test pop-up.
Click on the Sync as added row to make the request.
The result on the right will indicate if the request to Dataverse is successful.
Be aware that requests made through here will persist data into your
destination as if you ran an actual sync. When working on a production
environment, please make sure that you fully understand the risks.
Ready to get started?
Jump right in or a book a demo. Your first destination is always free.
