About the Microsoft Dynamics 365 Integration

Synchronise data from Microsoft Dynamics 365 (MsD) to APSIS One - manage consent and sync contact data. Read on to learn more about how the integration works!

Full sync & Real-time Sync

There are two features that empower data transfer from MsD into APSIS One: Real-time Sync and Full Sync.

A Real-time sync takes place whenever a contact card is created or updated in MsD. This results in a corresponding Profile being updated or created in APSIS One, matching the state of the contact in the MsD.

A Full sync systematically goes through all contacts in your MsD account and either creates a new Profile in APSIS One, or updates the existing Profile data. We recommended using this feature after setting up your initial mappings, or when you intend to sync new mappings.

How Profiles are synced

When a Profile is created in, it will receive the customer ID as a unique identifier, and Email and SMS consent is updated according to the chosen consent mapping. All data is written through MsD.

If a Real-time or Full sync detects a new email address for a Profile, the following will take place:

The new email address will be opted-in to all Subscriptions which the old address had given consent to;
The old email address will be opted-out from all Subscriptions and lose any consent, as it's no longer in use.

What can be synced?

Consent

Sync the freely given consent stored on a Contact in MsD to a Profile in APSIS One. Without consent no communication can be send.

If a Contact in MsD decides to unsubscribe or a MsD user untick the consent box the corresponding Profile in APSIS One will also be opted-out. Read more about Consent Mapping.

Contact data

With easy data mapping you decide what data should be synced.

Sync data from a Contact in MsD to Profiles in APSIS One. By mapping data fields to Profile Attributes in APSIS One Profiles will be updated with data from MsD at all times.

Marketing Lists

Create rich Marketing Lists in MsD and sync them directly into APSIS One to personalise your sendings even more.

Response data

Campaign Response Data such as Open, Click, Bounce, Unsubscribe, Sent, Delivered will be sent back to the CRM keeping your data hygiene to a high level.

Setting up the Integration

How do you integrate?

Here's a summary of the process of integrating Microsoft Dynamics 365 with your APSIS One account. Click to jump right to a section in the article for a more detailed run-down.

You will require both an APSIS One Integration User security role and an installation file in order to perform the installation.

1. Enable MsD with APSIS One with the API key.

2. Add Sync Conditions in case you only want a subset of your profiles to be synced with APSIS One.

3. Map data fields from the contact card in MsD to APSIS One Attributes.

4. Map consent. Set a checkbox for the mailing list Contacts can opt-in and out to, and Map it to Subscriptions in APSIS One.

5. Sync your data!

Solution Overview

Prerequisites

The APSIS One Integration solution only works with Microsoft Dynamics 365 CRM for Sales: No other products from the Microsoft Dynamics 365 CRM family are currently supported.

The APSIS One integration is intended to work with all recent versions of Microsoft Dynamics 365 CRM for Sales, or any version above 9.1.0.0.

The installation does not change any local files and does not require any specific software to be installed on the end-user's system. The only prerequisite is a web browser. To see which browsers are supported please refer to Microsoft's official documentation.

Note: that currently the APSIS One Integration is not intended to work with an on-premises version of Microsoft Dynamics 365 CRM for Sales.

APSIS One Configuration Values

Here's a list of all APSIS One values sent to MsD CRM:

Discriminator for the Section on which the integration was installed.
Discriminator for the Keyspace created to use with the integration.
APSIS One API Client ID.
APSIS One API Client Secret.

Security Roles

The installation package includes one security role which is required to access the entities related to the APSIS One integration. The name of that security role is APSIS One Integration User. and it can be combined with other security roles, including both built-in and custom roles.

This role ensures that users with this role have read-only access to the apsis_authentication and apsis_events entities.

Virtual Entities

Virtual entities to show APSIS One data are still under development and the list will be extended as new functions are implemented.

Currently, only the apsis_event entity is implemented, which provides a list of Events shown on the Contact Card.

To read more, head over to the MSD Developer Guide on Virtual Entities.

APSIS One Authentication Subsystem

The APSIS One Authentication Subsystem is aimed to provide easy access to APSIS One authentication token and consists of the CRMK.APSIS.Authentication plugin, registered automatically during the installation, and the apsis_authentication entity.

During installation, several configuration values holding APSIS One credentials are pushed. These allow the subsystems to work as intended.

After the configuration, the authentication subsystem provides the APSIS One authentication token. Once expired, it can be renewed.

The authentication subsystem is intended to work only for the purpose of integrating MSD with APSIS One, and not for users to interact with directly.

Get the token information as an output by retrieving the apsis_authentication entity.

About Microsoft Dynamics CRM

"Microsoft Dynamics 365 CRM is a set of intelligent business applications that helps you run your entire business and deliver greater results through predictive, AI-driven insights.

Read more on Microsoft Dynamics 365 CRM's website.