Timeline for How do you create scratch orgs with permissions that match production?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2018 at 14:56 | comment | added | user2270837 | Thanks, I was unaware of that. That will help if I can't do what I'm trying to do in code. As an example, only certain users should be able to change the owner of an opportunity, so that field should be read-only by default and then enabled for some users via permission sets. However, I can't figure out how to automate making that field read-only in both scratch orgs and production because the information is embedded in profiles which are not compatible between scratch and production. I don't necessarily need to do this in a .profile-meta.xml file if there's another way to script this. | |
| Aug 9, 2018 at 6:42 | comment | added | Aidan | If I follow you correctly, you just need to create a .forceignore file in your sfdx project to say you don't want profile changes in your source tree. See developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/… | |
| Aug 9, 2018 at 5:26 | comment | added | user2270837 | I attempted the steps above, and item #3 is a big issue. It seems as though any time I wish to modify the field level security for a non-custom field, I'm going to have a problem as when you modify field level security, you're actually modifying the profiles. Thus, if I modify such a field in a scratch org, perform a pull, I end up with profiles in my source tree that won't work in a production org. Does this sound correct, or am I missing something? | |
| Aug 7, 2018 at 17:07 | comment | added | user2270837 | That could be helpful. I've been unable to figure out how to manage page layout assignment via permission sets. Is there a way to do that? Assuming not, it seems like the overall workflow would be something like.... 1. Manually assign users to the built in profiles in prod 2. Manually assign permission sets to users in prod 3. Remove permissions from prod profiles as needed & document 4. Create scratch org 5. Remove permissions from profiles in scratch org per what was documented 6. Leverage SFDX to develop & configure the scratch org 7. Deploy changes to production #3 concerns me | |
| Aug 7, 2018 at 8:08 | history | answered | Aidan | CC BY-SA 4.0 |