Current Behaviour: Once the Azure Synapse Link for Dataverse is setup, all the tables with parent child relationships are synced with the correct value of Parent Name column in Child Table. However, when the parent record primary name field is updated in Dataverse, there is no trigger in Dataverse for child table, hence the parent table gets updated in Azure Data Lake and child table doesn't get cascaded with the parent's primary name field value. Any new child record created in Dataverse then has the new parent's primary name value. This leads to a discrepancy in the parent's primary name value in the parent table with respect to an old value in Child table.
ISSUE: Now it you have a reporting based on parent's name value from child table without knowing that the value won't be update, it leads to all the reports not functioning properly.
ASK: Please help with finding a way to have this data sync appropriately based on the changes in parent name. Alternatively, please help develop a tool which should update all the child tables with the latest parent's primary field name value
Comments
Users need to be able to trust their data at all times. Please make this real time to sync the data appropriately as changes are made.
Category: Dataverse
Users need to be able to trust their data at all times. Please make this real time to sync the data appropriately as changes are made.
Category: Dataverse
Please make this real time to sync the data appropriately as changes are made. Vote to make this happen.
Category: Dataverse
voted
Category: Dataverse
Users need to be able to trust their data at all times. Please make this real time to sync the data appropriately as changes are made.
Category: Dataverse
Data integrity is so fundamental that responding with works as designed raises many different questions.
Category: Dataverse
This issue goes to data quality and the proper care and feeding of the data estate. It is surprising that this has been allowed to linger for this long without resolution. If we can't trust the data in child records when an update occurs to a parent record, it calls into question the usage of the data in the dataverse for enterprise production purposes. This is critically important for further usage of the dataverse.
Category: Dataverse
This issue creates inconsistencies which Business Users latch onto and causes distrust of the data. With the newer advances of Synapse Link / Fabric Link and capabilities within fabric, including the new deltalake change data feed, a cascading update solution could be built.Stating the lookup fields are not supported in a FAQ document is NOT sufficient. We went around for 3+ months on a support case, trying to figure out why Fabric Link had data mismatches from CRM. It took months until a tech finally pointed out the small entry in the FAQ which has been slightly revised since this happened now: https://experience.dynamics.com/ideas/idea/?ideaid=56c55490-151a-ee11-913b-0003ff4588ed#submit-commentThis needs to be front and center for anyone enabling Synapse Link or Fabric Link for Dataverse / CE. It needs to be made clear what fields are lookup fields and that they may be wrong. I would have honestly preferred that the fields not be presented at all via Syn/Fabric Link if they could be inaccurate.Users need this data to be accurate and we would like to ask the Microsoft takes further steps to ensure accuracy.
Category: Dataverse