What is the easiest way to ensure the FLS is deployed to the next environment together with the field?

Debbie has created a new custom field in Dev1. She commits it on a user story together with the permission set to deploy FLS. After committing the changes, she realizes she forgot to grant the permission set access to the field in Dev1, so she goes back to Dev1 and updates the FLS.

What is the easiest way to ensure the FLS is deployed to the next environment together with the field?
A . She can go back to the user story where she committed the changes and use the Recommit Files Git operation.
B . She needs to create a new user story and commit again the permission set.
C . She needs to delete the user story, create a new one and commit again the field and the permission set.
D . She needs to create a new user story and commit again the custom field.

Answer: A

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments