Our Data steward team works on the variety of UI updates. One such update is after completing the overmatches, they inactivate the wrong identifiers on the crosswalk so that they don't contribute into the matching for future. This was the direction from Customer.
However, we noticed when a crosswalk comes with an update on any other attributes, the inactive status is flipped which is causing the overmatch again.
Is there a better approach for this from UI perspective so that the reactivates doesn't happen when the data loads. This is at crosswalk level.
Thank You!