You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When "Field-Level Security for Permission Sets during Field Creation" is activated (Setup/User Management Settings/Field-Level Security for Permission Sets during Field Creation), adding FLS on one Permission Set ends up in all Permission Sets being pulled.
Even though only 1 Permission Set is modified, all of them are pulled, even some standard ones.
This also happens when using the "Set Field-Level Security" button on an existing field.
This is painful as we don't want to retrieve unmodified Permission Sets that may be in the org but not part of our project.
Expected behavior
Only the modified Permission Set should be pulled.
Screenshots
All Permission Sets:
Only one which has object permissions is selected:
Everything is pulled:
The text was updated successfully, but these errors were encountered:
Describe the bug
When "Field-Level Security for Permission Sets during Field Creation" is activated (Setup/User Management Settings/Field-Level Security for Permission Sets during Field Creation), adding FLS on one Permission Set ends up in all Permission Sets being pulled.
To Reproduce
Even though only 1 Permission Set is modified, all of them are pulled, even some standard ones.
This also happens when using the "Set Field-Level Security" button on an existing field.
This is painful as we don't want to retrieve unmodified Permission Sets that may be in the org but not part of our project.
Expected behavior
Only the modified Permission Set should be pulled.
Screenshots
All Permission Sets:
Only one which has object permissions is selected:
Everything is pulled:
The text was updated successfully, but these errors were encountered: