1

Still fairly new to Salesforce, and can see there are changes I’ve made in the sandbox that I won’t be able to transfer over to production(sharing settings, standard object field-level security/accessibility, etc) via a change set.

I’m wondering if someone wouldn’t mind sharing their methodology as to how they work with sandbox change sets, mostly on how you ensure you’re bringing over all changes. Thanks for any advice.

closed as too broad by Markus Slabina, glls, Eric, Santanu Boral, Ratan Paul Aug 11 '17 at 5:43

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

1

I don't really use change sets, because the interface Salesforce provides for building them is, frankly, terrible. Instead, I use the Force.com Migration Tool. I still face the same issues that you're finding yourself facing though.

For the most part, I don't even make an attempt to deploy things like Field-Level Security (FLS).

Instead, I just keep in mind that I need to (in the target org) update the page permissions for who can view the Visualforce pages I deploy, update the FLS for the fields I deploy, update profile settings for SObjects and RecordTypes that I deploy, etc...

There are issues with scaling this approach, and editing profiles for access to SObjects and RecordTypes is a big pain, but it should be manageable for small teams (say, 3 developers or less).

Not the answer you're looking for? Browse other questions tagged or ask your own question.