When a Dataverse table is deleted and recreated with the same logical name, Fabric Link should recognize the recreated table provide a seamless experience. Currently, Fabric Link can treat the recreated table as an actual table and duplicates the data for the table and it requires manual intervention to avoid synchronization issues.

Current Behavior:

• A Dataverse table is deleted and recreated using the same logical name.
• Fabric Link identifies the recreated table as the same object.
• Customers must manually stop synchronization, remove the table from the Fabric Link configuration, save changes, and then re-add the table or refresh the Fabric Link configuration.
• If not handled correctly, this can lead to confusion and potential duplicate data scenarios.

Expected Behavior:



• Fabric Link should automatically detect that a table has been recreated and provide a seamless reconciliation process.
• The platform should prevent duplicate data scenarios and clearly notify administrators when a table recreation event has been detected.