One of our production org has been automatically migrated to Spring22 by Salesforce last week-end
The following jobs has been run by SF platform during the update (audit trail extract)
After this upgrade, all of the permission set has been automatically updated:
- For some of them, all fieldAccess has been removed (Standard and Custom fields)
- For some of them, only some fieldAccess has been removed (again standard and/or custom fields)
All Permission Sets, even the ones not in our CI, even Salesforce Internal ones, has been automatically updated, it can not be from a manual operation
Has anyone observed the same error on his/her production org after Spring22 update ?
Is there some "one-click" way to rollback the forced destruction of rights on PS ?
Last Modified By
say?