Microsoft Dynamics

This page describes how to use Census with Microsoft Dynamics.

Microsoft Dynamics 365 is a cloud-based suite of enterprise resource planning (ERP) and customer relationship management (CRM) applications designed to streamline business processes and improve customer interactions. Census can sync your data to its integrated modules for sales, customer service, finance, operations, marketing, and more, enabling you to make data-driven decisions and enhance overall efficiency.

Getting Started

This guide shows you how to use Census to connect your Microsoft Dynamics account to your data warehouse and create your first sync.

Prerequisites

Step 1: Connect Microsoft Dynamics

For Production Dynamics instances, the user to authenticate Census needs to have "Service Writer" permissions. For the Default environment, the user must be an Admin. Read more about this here.

  1. Log into Census and navigate to Destinations.

  2. Click New Destination and select Microsoft Dynamics from the menu.

  3. Follow the Microsoft Dynamics OAuth authentication flow, which will ask you to log in with your Microsoft Dynamics username and password.

Once complete, you'll see your new connection in the Destinations list. 👇

Step 2: Create your model

When defining models, you'll write SQL queries to select the data you want to see in Microsoft Dynamics. This can be as simple as selecting everything in a specific database table or as complex as creating new calculated values.

  1. From inside your Census account, navigate to the Models page.

  2. Click Add Model.

  3. Enter a name for your model. You'll use this to select the model later.

  4. Enter your SQL query. If you want to test the query, use the Preview button.

  5. Click Save Model.

Basic SQL query for a new model

Step 3: Create your first sync

The sync will move data from your warehouse to Microsoft Dynamics. In this step, you'll define how that will work.

  1. From inside your Census account, navigate to the Syncs page and click Add Sync.

  2. Under What data do you want to sync?, choose your data warehouse as the Connection and your model as the Source.

  3. Under Where do you want to sync data to?, choose Microsoft Dynamics as the Connection and the object (aka entity in Microsoft Dynamics) that you want to sync to (see Supported objects for more detail).

  4. Under How should changes to the source be synced?, choose Update or Create (see Supported sync behaviors for options)

  5. Under How are source and destination records matched?, select an Identifier for the model and for the Microsoft Dynamics object. Valid identifiers are single-columns keys for entities that you can set up in your Microsoft Dynamics instance (see Supported objects for more detail).

  6. Under Which properties should be updated?, select which fields you would like to update.

  7. Click Next. This will open the Confirm Details page where you can see a recap of your setup.

  8. If you want to start a sync immediately, set the Run a sync now? checkbox.

  9. Click Create Sync.

When configuring your sync, the page should look something like this: 👇

Source, destination and sync operation selectors
Sync identifier and mappings selectors

Step 5: Confirm the synced data is in Microsoft Dynamics

Once your sync is complete, it's time to check your data. Open Microsoft Dynamics and check that the entity that you sent data to has updated entries.

If everything went well, that's it! You've started syncing data from your warehouse to Microsoft Dynamics! 🥳️

And if anything went wrong, contact the Census support team to get some help.

Supported objects

Object Name

Supported?

Sync Keys

Entity name

All single-column keys for the entity

Marketing Lists

All single-column keys for the entity

All Microsoft Dynamic entities are supported as objects to sync to in Census. Here is some documentation on defining keys for entities in Microsoft Dynamics:

Lookups to other records

Lookups from one Dynamics Entity to another in the same 365 workspace can be configured, and this happens via the single-column keys for the entity as such:

The lookup by key needs to single-column keys

When you have a null lookup, or a reference from which you want to disassociate a record, you need to sync over null.

For a string example of a column in Snowflake:

IFF(lookup_ref = '', NULL, lookup_ref) as lookup_ref

Supported sync behaviors

Behavior

Supported?

Objects

Update or Create, Update Only

All

Learn more about all of our sync behaviors in our Syncs documentation.

Let us know if you want Census to support additional sync behaviors for Microsoft Dynamics.

MS App Approval Flow

To use Census with Dynamics, your Dynamics user must be able to request to request admin approval for apps. The following will walk you through the approval workflow in Microsoft Entra.

  1. [ADMIN] Configure your Admin settings in Entra, so users can request admin consent to apps. This is found after navigating to Enterprise applications > Consent and permissions > Admin content settings.

  2. [USER] Add Microsoft Dynamics as a destination in Census and go through the OAuth flow. At the end, you will be prompted to enter a justification and request for access.

  3. [ADMIN] Find the approval request in Entra. Approval requests can be found after navigating to Enterprise applications > Admin consent requests.

  4. [ADMIN] Click on the approval request, then click on Review permissions and consent.

  5. [ADMIN] A popup will prompt you to select a Microsoft Account. After selecting, approve the request.

  6. [USER] Re-add the destination and complete the OAuth flow in Census.

Need help connecting to Microsoft Dynamics?

You can send our support team an email at [email protected] or start a conversation from the in-app chat.

Last updated

Was this helpful?