Customer experience | Sales, Customer Insights,...

Remove data source from Customer Insights - Data unification (and then remove it altogether)

(2) Share

Report

Posted on by CU17041051-0

Hi all,

I want to remove an obsolete data source from Customer Insights - Data.

However, it won't let me due to "downstream dependency(s)". Clicking more details lists literally every segment, but I checked and they just use Customer. This source is in unification, but completely removed from all steps.

How do I discover the depedencies of these two columns so that I can remove the data source from unification, and then from the system entirely?

As far I'm aware nothing uses data from this source. I manually checked countless segments, measures and table relationships.

It is included in unification, but I cannot remove it here. There is still a dependency somewhere.

Going backwards, from unified view to customer data:

Unified view: 0 fields use data from this source

Matching rules: there is exactly 1 rule, which was mandatory to let me save unification,

Deduplication: no rules involving this source, only the default 'keep most filled'

Customer Data: all columns unmapped. But going into the "Select tables and columns" menu, two columns are checked and greyed out meaning I cannot disable them.

I already checked the Tables->Relationships page, and (after enabling all user and system tables, and all user, system and inherited relationships, and checking both the source and target table columns) there are exactly two relationships which both seem to be unification artefacts.

Categories:

Dynamics 365 Customer Insights - Data

All responses (2)

Answers (0)

Suggested answer

Daivat Vartak (v-9d... 7,336 Super User 2025 Season 1 on at

Like (1)

Report
Remove data source from Customer Insights - Data unification (and then remove it altogether)

Hello CU17041051-0,

You've done a thorough job checking the obvious dependencies! The fact that those two columns are still checked and greyed out in the "Select tables and columns" for that data source is the key indicator that a dependency still exists at the system level, even if you can't see it directly in segments or measures.

Here's a systematic approach to uncover these hidden dependencies and then remove the data source:

1. Focus on the Greyed-Out Columns in "Select tables and columns":

These greyed-out columns are the most likely culprits. The system believes something still relies on them. Since you've checked segments and measures, the dependency is likely within the data unification process itself, even after you've seemingly removed it from the steps.

2. Investigate the Mandatory Matching Rule:

You mentioned a mandatory matching rule that allowed you to save unification. This is a prime suspect. Even if it appears to only use the unified Customer entity, it might have been initially configured (or the system might still internally track) using columns from your obsolete data source during its creation.

Edit the Mandatory Matching Rule: Go back to your Matching rules and open this specific rule. Carefully review all the rule conditions and the fields being used. Even if it currently points to the unified entity, see if you can identify any lingering references or configurations that might have involved the columns from the obsolete source.

Try Recreating the Mandatory Rule: As a test (be cautious, as this might impact your unified profile quality), try deleting this mandatory matching rule and then recreating it, ensuring you only use fields from the unified Customer entity. If you can then proceed with removing the data source, this was likely the hidden dependency.

3. Examine Table Relationships within Unification Again (with a Different Lens):

You mentioned two relationships that seem like unification artifacts. Let's revisit these with the greyed-out columns in mind:

Identify the Tables and Columns in the Relationships: Note down the exact tables and columns involved in these two relationships.

Cross-Reference with Greyed-Out Columns: Do the greyed-out columns from your obsolete data source participate in either of these unification-related relationships? Even if it seems like a system-level relationship, the system might still consider those columns as being "used" due to their involvement in defining the relationship, even if the relationship's logic currently doesn't explicitly leverage them.

Try Deleting These Relationships (Carefully): If these relationships involve the tables from your obsolete data source and you suspect they are the cause, carefully consider deleting them. Back up your Customer Insights - Data configuration before doing this! After deletion, try removing the data source.

4. Use the API to Inspect Dependencies (More Advanced):

If the UI isn't revealing the dependency, you could try using the Customer Insights - Data API to inspect the metadata and dependencies more directly. This requires some technical knowledge. You would look for references to your data source or the specific greyed-out columns in the API responses for entities, matching rules, and unification configurations.

Steps to Remove the Data Source:

Once you've identified and removed the dependency:

Go to Data Sources.

Hover over your obsolete data source.

You should now be able to click the "..." (ellipsis) and select Remove.

In your specific case, the greyed-out columns in the "Select tables and columns" section of the data source are the strongest clue. Focus your investigation on any matching rules or unification-related table relationships that might still be referencing or be configured based on these columns.

Start by carefully re-examining the mandatory matching rule. Let me know what you find!

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak
Suggested answer

Holly Huffman 6,078 on at

Like (0)

Report
Remove data source from Customer Insights - Data unification (and then remove it altogether)

Good morning, afternoon, or evening depending on your location!

It sounds like you're dealing with a hidden dependency within Customer Insights that’s preventing you from fully removing the data source. Here’s how you can systematically track down and eliminate the dependencies:
Steps to Identify and Remove Dependencies

Check Unified Data View Dependencies

Even if no fields are mapped, ensure the data source isn’t referenced in any computed fields or aggregations.

Go to Data > Unify > Unified Data View and verify that no fields from the obsolete source are included.

Review Matching Rules

Since you mentioned there’s one mandatory matching rule, try removing or modifying it to exclude the obsolete source.

Go to Data > Unify > Matching Rules and check if the rule is still referencing the source.

Investigate Deduplication Rules

Even though you’re using the default "keep most filled" rule, ensure that no deduplication logic is still tied to the obsolete source.

Go to Data > Unify > Deduplication and verify that the source isn’t involved.

Check Customer Data Selection

The two greyed-out columns in "Select tables and columns" indicate that they are still linked somewhere.

Try removing them from the unified profile first before attempting to delete the source.

Review Table Relationships

Since you found two relationships that seem to be unification artifacts, check if they are still active dependencies.

Go to Data > Tables > Relationships and attempt to delete or modify them.

Force Removal via API or Support

If all else fails, you may need to use the API or contact Microsoft Support to force the removal.

Microsoft has documented steps for handling data source removal issues here.

Final Steps
Once you’ve removed all dependencies:

Go to Data > Data Sources and attempt to delete the source.

If deletion is still blocked, try refreshing the environment or reprocessing unification.

Please note: I teamed up with CoPilot AI to research and craft the best response to your question!
Hope this helps some!

Community site session details

Remove data source from Customer Insights - Data unification (and then remove it altogether)

Helpful resources

News and Announcements

Quick Links

Announcing the Engage with the Community forum!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Adis Hodzic – Community Spotlight

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

Remove data source from Customer Insights - Data unification (and then remove it altogether)

Helpful resources

News and Announcements

Quick Links

Announcing the Engage with the Community forum!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Adis Hodzic – Community Spotlight

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates