[SalesForce] Can’t install managed package because packaged permission set seems to have lost a read permission

I developed a Managed Extension Package. When I try to install it or create a patch org for it, this fails with no error but the note to call Salesforce.

Support told me that it fails due to:

MyPermissionSet: Permission Create MyNamespace__MyChildObject__c depends on  
permission(s): Read ExtendedPackageNamespace__MyParentObject__c

From the error message it seems like the permission set is unable to assign a CREATE permission to a Master/Detail child object, because it misses a READ permission on its parent object.

BUT this is not true. MyPermissionSet contains READ access rights to this object. While packaging or installing this seems to get lost or ignored.

Can the reason for this be, that the parent object it is depending on, is no from my package but the package I am extending?

Best Answer

I'm a product manager at salesforce.com responsible for Permission Sets. I was able to reproduce this use case. We do intentionally block the setting of parent permissions if it's a standard object (Kibitzer is totally correct with this). I'm working through this use case with my team since this use case is directly related to a custom object from the base package instead of a standard object. Please stay tuned. Thanks for your patience!

Related Solutions

[SalesForce] Managed package install failed with The first validation error encountered was “{0}”

Re: "The formula references fields across 11 relationships while only 10 are allowed. Please contact support at salesforce.com for more assistance"

This is a "soft" limit, that is salesforce support has the ability to raise this limit within reason. I've seen it raised to 12 without any pushback before. I believe anything over 15 requires additional approvals from the product management team.

The limit is in the number of related object fields you are referencing. For example the formula:

myCustomLookup__r.name && account.name

would consume two "relationships" in terms of this limit as it follows the account and myCustomLookup__c fields.

After resolution notes

Some notes from the support case in the customers Org that got the limit increased after 12 hours with Premier support and several levels of esculation:

I need assistance with CRM
Product Topics Limits & Feature Activations
Subject Increase Spanning Relationships limit (Note that Support changed the subject to this)
Excerpt from Case Comments: "I am glad to inform you that the requested limit has been increased to our hardcoded maximum of 15 for your organization."

[SalesForce] Managed package install fails in a single customer Org

FiscalYear might only be available if the organisation has setup fiscal details in their setup - there is definitely some reason that it doesn't exist.

You could test for the existence of the field using the system describe information, then if it does exist reference it via a string (as opposed to using the field name directly in code), thereby making your code tolerant of orgs which do not have this field.

// do not do this
theYear = theOppty.FiscalYear;

// do this
if (fieldExists)
{
  theYear = ((SObject)theOppty).get('FiscalYear');
}

Best Answer

Related Solutions

[SalesForce] Managed package install failed with The first validation error encountered was “{0}”

[SalesForce] Managed package install fails in a single customer Org

Related Topic