For the complete documentation index, see llms.txt. This page is also available as Markdown.

Microsoft Dynamics 365

Microsoft Dynamics 365 is a cloud-based suite of enterprise applications that combines CRM and ERP capabilities to help businesses manage sales, customer service, finance, operations, and more. Didomi currently supports two versions of a Microsoft Dynamics 365 integration:

Version
Description

The original version of the Microsoft Dynamics 365 integration whereby end-user preferences were managed directly on the Contact table/entity within Microsoft. Microsoft Dynamics 365 has since replaced this method with Compliance Profiles and Contact Point Consent table/entity.

Note: Currently, maintained for existing organizations that have implemented the Microsoft Dynamics 365 integration with Didomi. These organizations are strongly encouraged to update and migrate their integration to utilize the Current iteration of the Didomi/Microsoft Dynamics 365 integration.

Leverages Microsoft Dynamics 365's current method of managing end-user preferences via Compliance Profiles and Contact Point Consent table/entity.

Note: Organizations implementing the Microsoft Dynamics 365 integration will implement this version of the integration by default.

Migration to Microsoft Dynamics 365 (Current)

For organizations who have implemented Microsoft Dynamics 365 (Legacy), Didomi strongly urges you to upgrade the integration to the most current version. In this section, we provide an overview of the migration process:

A significant shift between the legacy and current version of Microsoft Dynamics 365 is how Microsoft organizes and stores end-user consent and preferences data. Review the table for more information:

Version
MS Dynamics 365 Entity
Structure

Legacy

Contact

End-user consent and preferences stored on the Contact entity/table with each purpose and preference stored as a separate column in a single row for the end-user.

Current

Contact Point Consent

End-user consent and preferences stored on the Contact Point Consent entity/table with each purpose and preference stored as distinct row.

Historical records migration

Didomi currently does not support a native way to automatically migrate your historical end-user preference records in Microsoft Dynamics 365 to the Contact Point Consent table/entity used in the current method.

Please contact your Microsoft Dynamics 365 representative for more information and assistance.

Last updated