1

The current behavior of table auditing that contain calculated field, is that all data is synced to Fabric lakehouse in the initial sync. However, when calculated fields on a table change because the underlying fields being used in the calculation change, the computed field value changes but is not audit tracked. This means that change is not being picked up in the fabric link to lakehouse, and we are loosing that change tracking. We only see the initial sync value of that calculated column.


The 2 options suggested are to:

1. unlink and relink that specific table (this is not a feasible long-term solution)

2.duplicate the calculation on the fabric lakehouse side. (this is also not a feasible or scalable long-term solution).


I am suggesting that an audit tracking enhancement be made to sync calculated columns when they change.

Category: Dataverse
STATUS DETAILS
New