Hi Buddy,
When you delete a record under User Criteria → Not available for, the delete action may show up in the update set, but it often doesn’t apply in the target instance. That’s because these entries are typically M2M/relationship records, and update sets are not reliable for migrating deletions—especially if the record doesn’t exist with the same sys_id in the target instance.
Because of this, the change won’t be visible after migration.
The usual and safest options are:
Manually delete the record in the target instance, or
Inactivate the record instead of deleting it (inactivation migrates more reliably).
So this isn’t a bug—just a limitation of how update sets handle deletions for User Criteria–related records.
@SankeethRamT - Please mark Accepted Solution and Thumbs Up if you found Helpful 🙂
