Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When an existing field is set to required, related Permission Sets are not pulled #6

Open
FabienTaillon opened this issue Jul 11, 2022 · 2 comments
Open

When an existing field is set to required, related Permission Sets are not pulled #6

FabienTaillon opened this issue Jul 11, 2022 · 2 comments
Labels
change not tracked on org Change in Org isn't tracked correctly in SourceMember

Comments

@FabienTaillon
Copy link
Member

Describe the bug
When an existing field is set to required, related Permission Sets are not pulled

To Reproduce
Steps to reproduce the behavior:

  • Create a Scratch Org
  • Create a field (like a text field on Account)
  • Create a Permission Set and add read and edit access to the field
  • Pull everything
  • Go to the field and set it as required
  • Pull again

Expected behavior
Both field and Permission Set should be pulled. Today, only the field is pulled, whereas the Permission Set should be pulled too. When deploying as is (without manually retrieving the Permission Set) you'll get this error: "You cannot deploy to a required field".
@FabienTaillon FabienTaillon added the change not tracked on org Change in Org isn't tracked correctly in SourceMember label Jul 11, 2022
@FabienTaillon
Copy link
Member Author

Case 42923165 created.

@FabienTaillon
Copy link
Member Author

Known Issue created: https://trailblazer.salesforce.com/issues_view?id=a1p4V000002eKRcQAM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
change not tracked on org Change in Org isn't tracked correctly in SourceMember
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FabienTaillon