Idea Description

In Dynamics 365 Customer Insights - Data, the Unified Customer Profile is currently designed to display a single flattened row per customer after data unification. While this design supports identity resolution and aggregation scenarios, it limits the ability to visualize or consume related 1:N data collections directly within the unified profile.

In our scenario:

• Contact records are ingested from Dataverse
• Multiple related Contract records are ingested from an external data source (e.g., Snowflake via Power Query)
• A 1:N relationship is correctly configured using Contact ID
• After unification, only a single related Contract record is displayed on the unified customer profile

This behavior prevents organizations from:

• Viewing all associated transactional or contractual records per customer
• Building segmentation logic based on individual related child records
• Supporting downstream marketing and analytics use cases that depend on multiple related entities (e.g., customers with multiple active contracts)

Currently, customers must rely on workarounds such as segmentation or analytics models to access related child records, as displaying 1:N related collections directly in the unified profile is not supported by design.

Business Impact

This limitation impacts organizations that:

• Maintain transactional or contract‑based relationships with customers
• Require visibility into multiple related records within a unified customer view
• Depend on Customer Insights – Data for downstream marketing segmentation and personalization

Marketing and analytics teams may be unable to:

• Accurately represent customer relationships
• Target customers based on individual related records
• Execute campaigns that depend on multi‑record relationship context

Requested Enhancement

Introduce support for:

• Displaying 1:N related entity collections within the Unified Customer Profile, or
• Providing an optional nested or expandable relationship view within the profile

This would enable organizations to:

• Preserve relational context during data unification
• Support more advanced segmentation and personalization scenarios
• Improve usability for business users relying on the unified customer view

Customer Scenario

Financial services organization needing to associate and visualize multiple contract records per customer within a unified profile for marketing segmentation and lifecycle engagement use cases.