Microsoft Dynamics CRM and Customer Insights: Understanding the msdynci Column Pattern

When integrating Microsoft Dynamics 365 CRM with Customer Insights — Data (CI-D), many administrators notice a curious pattern: certain tables like Contact receive columns with the msdynci_ prefix, while others don't. This isn't a synchronization error—it's an intentional design element that reveals how Customer Insights processes different types of entities.

The Purpose Behind the Pattern

Profile-Designated Tables

Tables designated as customer profiles (primarily Contact and Account) receive special treatment in the CI-D ecosystem. When synchronization is enabled, the system automatically adds metadata columns including:

• msdynci_isprofile - Designates the record as part of the unified customer profile
• msdynci_lastprofileupdate - Tracks when profile data was last refreshed
• msdynci_profilestatus - Indicates the current state of the profile in CI-D

These columns enable CI-D’s core capabilities: profile unification, data enrichment, audience segmentation, and predictive scoring.

Standard and Custom Non-Profile Tables

Other tables — whether standard Dynamics entities or custom tables — don’t automatically receive the msdynci_ columns because they're not treated as profile entities by default. These tables can still synchronize and function within CI-D, but they serve different purposes in the customer data model.

Validating Your Integration

To confirm your synchronization is working properly:

1. Examine Sync Health Metrics

• Access the Power Platform Admin Center
• Review the synchronization health dashboard
• Check individual table sync status indicators

2. Verify Table Classifications in CI-D

• Navigate to the Data > Tables section in Customer Insights
• Confirm how each table is classified (profile, interaction, or relationship)
• Review which tables are actively being utilized

3. Configure Non-Profile Tables

• For custom entities you want incorporated into CI-D
• Explicitly map the table schema
• Define relationships to profile entities
• Set appropriate data refresh schedules

Key Insights for Administrators

The selective application of msdynci_ Columns provide a window into how Customer Insights categorizes and processes your CRM data. This pattern helps CI-D maintain clear boundaries between profile-centric data and supporting information.

When building comprehensive customer data models across Dynamics 365 and Customer Insights, understanding this architectural choice ensures you can properly interpret table structures and create effective entity relationships.