[SalesForce] Protected Custom Settings in managed package are not visible by apex class

I'm facing a major problem is critical stage of my project:

I have packaged my app in a managed package (currently beta), including 5 custom setting objects, 2 of which are Protected.
The 2 protected objects were not installed. Does anyone know why?
In an attempt to move forward I manually copies the two objects into the org (via the IDE), of course these have no namespace. Now some of my code that refers to these object does not work and I don't know if this is because the objects are Protected or because of the namespace .

Any suggestions for these two problems are much appreciated

Thanks

Best Answer

As you say, installing the custom settings outside your managed package won't work as they will be in a different namespace.

Assuming that your protected custom objects are included in the managed package, ensure any of the fields for them are also included. This should happen automatically when they are referenced by your Apex code.

If Privacy for a custom setting is Protected, and the custom setting is contained in a managed package, the subscribing organization cannot edit the values or access them using Apex.

You can only work with your protected custom settings from apex code within your package. You won't be able to manipulate them directly via the settings page.

Related Solutions

[SalesForce] Retrieving extended package object descriptors into Eclipse with Force.com IDE plugin

To retrieve the managed package objects along with your custom metadata, you have to manually add the objects you want to retrieve to your package.xml file. For example, to retrieve a custom object, you might already be retrieving the Account object like this:

<types>
    <members>Account</members>
    <name>CustomObject</name>
</types>

You simply need to add the namespaced object name to this list. This is the "API Name" visible on the object page in the Salesforce UI

<types>
    <members>Account</members>
    <members>packagenamespace__CustomObject__c</members>
    <name>CustomObject</name>
</types>

If you just want to retrieve the fields that you are adding to that object for subsequent deployment, you can specify them in a CustomField type

<types>
    <members>packagenamespace__CustomObject__c.MyField__c</members>
    <name>CustomField</name>
</types>

Remember that the CRUD / FLS rules for any profiles that you are retrieving will include this object / field.

Please also see my response to this similar question about layouts How to retrieve layouts of customs objects belonging to a managed package?.

This technique applies generally to most (all?) objects in the metadata API.

[SalesForce] Custom Settings – Visibility Protected – Managed Package

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

Best Answer

Related Solutions

[SalesForce] Retrieving extended package object descriptors into Eclipse with Force.com IDE plugin

[SalesForce] Custom Settings – Visibility Protected – Managed Package

Related Topic