Customer experience | Sales, Customer Insights,...

Unable to add table in existing Dataverse Data source

(1) Share

Report

Posted on by CU09081545-3

Hi everyone,

I’m encountering an issue when trying to add a table in the existing Dataverse data source within Customer Insights Data. The process fails with the following error:

Error: Invalid data source operation was found due to downstream dependencies or other already running operation 'Active' on data source with data source id '28c4b677-8536-44ec-b716-e71facf792b0'.  
Request ID: 8bf3a193-d26e-4437-9a29-ccaeee8cc103
Time: 29/12/2025, 1:24:54 pm

Additional details:

There are no segment refreshes or system refreshes running.

The only thing I can see is that there are columns unified from the Dataverse data source, but this didn’t cause an issue last time when we ingested a new table.

We are trying to ingest the table msdynmkt_contactconsentpoint4 in our Customer Insights Data instance.

Has anyone experienced this before? Please see attached images for what I am referring to. What could be causing this error, and how can I resolve it? Any guidance or best practices would be greatly appreciated.

Thanks in advance!

Categories:

Dynamics 365 Customer Insights - Data

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Daniyal Khaleel 764 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Why This Happens Even Though It Worked Before
This issue usually appears when one of the following changed since last ingestion:

A new unification rule was added or modified

A segment references a profile attribute coming from Dataverse

A measure or calculated attribute references Dataverse

A previous ingestion failed silently

CI-D backend still considers the data source “busy”

The table msdynmkt_contactconsentpoint4 is also Marketing-related, which often participates indirectly in profile unification, increasing the likelihood of locking.

Resolution Steps (In Order)

Check for Hidden Dependencies

Even if no refresh is running:

Go to Data → Tables

Open existing Dataverse tables

Check:

Profile mappings

Unified attributes

Measures

Segments

If any of these reference the Dataverse source, CI-D will block schema changes.

Was this reply helpful? Yes No
CU09081545-3 14 on at

Like (0)

Report
Copy link

Link copied!

Thanks, Daniyal. I can confirm that we do have multiple segments as well as columns from the Dataverse data source unified at the Customer Profile level. Are you suggesting that these need to be removed before we can add a new table to the existing Dataverse data source? That seems quite time-consuming and counterproductive, as we don’t want to remove anything just to add another table. If this is indeed a limitation, it looks like we may need to create a separate data source using Power Query instead. Is this the way forward?

I’ve also reviewed the tables, and the output indicates success with no errors. How would we know if this is a silent failure? Is there a way to trace this in our logs? Note: we’ve already lodged a ticket with Microsoft support for this issue but haven’t received a resolution yet.

__PRESENT

Was this reply helpful? Yes No

Join the conversation

Community site session details

Unable to add table in existing Dataverse Data source

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Meet the Microsoft Dynamics 365 Contact Center Champions

Congratulations to the March Top 10 Community Leaders

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

Unable to add table in existing Dataverse Data source

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Meet the Microsoft Dynamics 365 Contact Center Champions

Congratulations to the March Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates