5

I have a requirement to create a protected (visibility) custom setting which will be part of managed released package, now in the next release we need to make the visibility to public.

I know there are several scenarios where once some components are packaged you cannot update/delete the properties.

Q) If I make the visibility of a custom setting to Protected in v1.0 of a managed package, and in v1.1 make it public, does salesforce allow it?

Regards,

  • No. You will not be able to modify the visibility once it is packaged and released – Eric Jun 12 '15 at 17:00
6

No. You will not be able to modify the visibility once it is packaged and released

  • In fact, you can't change the setting from the moment it's created. It's a done deal, forever. – sfdcfox Jun 12 '15 at 18:19
1

Prior to the Summer 15 release, you could not change the visibility of custom settings once they were created. But starting in Metadata API v. 34.0, you can change a custom setting from protected to public (but not the other way around) using the Metadata API, even after managed package release, unless you're in a patch organization. The user interface doesn't support doing this yet, though.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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