1

When I bring a number of change sets over from one org to another I find that only the user permissions are contained within the XML. How can I ensure the object and field permissions metadata is included as well?

3
  • can you explain a bit briefly about change sets over from one org to another.@EmilioSandoz
    – Pavan tej
    Aug 11, 2016 at 18:40
  • they let you push salesforce configuration data from one org to another Aug 11, 2016 at 18:41
  • 5
    Are you including the user profiles in the change sets?
    – Dave Humm
    Aug 11, 2016 at 18:44

1 Answer 1

2

You need to include the objects, classes etc in the change set as well. This is the trigger for salesforce to include the object permissions, field level security, record type perms etc in the profile or perm sets. The rub however, is that this will deploy your objects etc even when you have don't want to do that. So, be very careful about doing this using change sets. You can do the same using other tools like Force.com IDE, ANT. These are developer focused tools. So, proceed appropriately.

There are vendors that publish tools to accomplish this stuff without too much difficulty, like the company I work for, DreamFactory.

2
  • Thanks - luckily the use case was only for field information was able to include those without too much pain. Aug 12, 2016 at 9:20
  • What if the object is a standard object?
    – kabrice
    Aug 3, 2022 at 15:41

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .