Forum Discussion
Microsoft EmployeeMirroring dataverse in Fabric
I am using 'Mirroring dataverse to Fabric' option . It intitially refreshed the list of tables i chose. After that i dont see any incremental updates? I am also not able to see the last refreshed timestamp anywhere in Fabric for those tables. Anybody else facing the same ?
Hi hajanawaz
I would also take a moment to thank NandanHegde , svenchio and tayloramy for actively participating in the community forum and for the solutions you’ve been sharing in the community forum.
Since you are using the “Mirroring Dataverse into Fabric” private preview, the behavior you’re seeing is expected. Incremental updates in this preview do not run reliably and often occur only at initial provisioning, with long delays afterward because the service currently operates on a best-effort basis. Fabric also doesn’t provide a “last refreshed” timestamp or monitoring details for mirrored tables yet. The only dependable way to check whether updates have occurred is by reviewing the Delta Lake _delta_log folder for each table if no new JSON files appear, no incremental data has been applied. These delays can result from backend throttling, temporary pauses, preview bugs, slow Dataverse change propagation, or simply no new data to replicate. Since Mirroring is still a private preview feature it is better to reach out to your Microsoft preview contact.
Best Regards,
Community Support Team
8 Replies
- NandanHegde
Super User
Based on my knowlegde this is still in private preview and not public preview. So would suggest reaching out to the product team
v-karpurapudCommunity Support
Hi hajanawaz
I would also take a moment to thank NandanHegde , svenchio and tayloramy for actively participating in the community forum and for the solutions you’ve been sharing in the community forum.
Since you are using the “Mirroring Dataverse into Fabric” private preview, the behavior you’re seeing is expected. Incremental updates in this preview do not run reliably and often occur only at initial provisioning, with long delays afterward because the service currently operates on a best-effort basis. Fabric also doesn’t provide a “last refreshed” timestamp or monitoring details for mirrored tables yet. The only dependable way to check whether updates have occurred is by reviewing the Delta Lake _delta_log folder for each table if no new JSON files appear, no incremental data has been applied. These delays can result from backend throttling, temporary pauses, preview bugs, slow Dataverse change propagation, or simply no new data to replicate. Since Mirroring is still a private preview feature it is better to reach out to your Microsoft preview contact.
Best Regards,
Community Support Team- tayloramy
Hi hajanawaz,
I have a mirrored dataverse environment using Synapse Link and it's working fine on my end.
Are you able to share some screenshots of your configuration from Dataverse?
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
- svenchio
Hi hajanawaz I just want to confirm if what you meant with "Mirroring dataverse to Fabric'" referes to using a Fabric/Synapse Link to replicate your dataverse tables into a Lakehouse (I wrote a series on this topic Dataverse Meets Fabric (Series)) ... the reason why I'm asking is because there's a buzz around a new preview feature to Mirror dataverse into Fabric, so, it's importatn to understand what exactly are you using.
If it is Fabric/Synapse Link, it is important to know wheter is FABRIC LINK or a SYNAPSE LINK 😅 as these two have different max refresh rates and characteristics! For instance, the SYNAPSE LINK depends on your synpase infrastructure, hence, in addition to your Link configuration, other aspects like synpse infra. configuration plays a big role in how ofter updates happen! And for FABRIC LINK, depends a lot on what MSFT offers, last time I checked it was 15 minutes.
In my article, Dataverse Meets Fabric - What About Monitoring? I discuss about monitoring, but answering your question on "not able to see the last refreshed timestamp" ...
"Application Layer
Assuming the infrastructure is functioning correctly, the next focus is on the synchronization status of individual tables within Dataverse. Microsoft provides system tables that offer real-time insights into the sync status:
SynapseLinkProfileEntityState: This table provides information about the initial synchronization status of each table.
SynapseLinkExternalTableState: This table offers details about the external tables in the Synapse workspace, including their synchronization status and metadata
By monitoring these tables, you can detect anomalies such as delayed syncs or failed updates. For proactive monitoring, consider setting up Power Automate flows that trigger alerts based on specific conditions (e.g., SyncState not equal to 'Completed' or LastSyncedDataTime exceeding a threshold)."
So, hope this information has been useful, if so, I would appreciate a kudos or mark this as solution to your question! Best of lucks!
hajanawazHi svenchio Thank you for the response. But I am not using the 'SYnapse link' or 'Link to fabric' which is something been set up from dataverse side.
I am using the "new preview feature to Mirror dataverse into Fabric". Yes it says its in preview. so wondering any one used this option. I see this directly puts the dataverse data to your one lake house for use as delta tables
- svenchio
Hi hajanawaz I guess the percs of working at MSFT? I don't have that option nor I can requested or enabled by tenant settings, I guess A VERY FEW PEOPLE have access to that preview feature, best of lucks. Anyways, please let me know if you know how to request access to that preview to test and enrich my series on Dataverse meet Fabric 😉
- v-karpurapud
Hi hajanawaz
We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank You.
