8

I'm receiving the following error when uploading a managed package (during the validation stage):

"Permission Set Name" references "Custom Object" that has M-D relationship with Account.

This is a subsequent release, this custom object has already been released along with all the related fields on the custom object (including the M-D field "Account"). Nothing new has been added to this object for the new release.

This happens for three of my custom permission sets. My custom object absolutely has a master-detail relationship with the Account object. I am not sure what the actual issue is as this "error" is really not giving much information on how to solve the problem.

Has anyone ever seen this error? Can anyone give me any direction on what the root cause of this issue is?

Improve this question

1 Answer 1

Reset to default
9

Adam Torman's answer to a somewhat related (but not entirely) question notes:

We do intentionally block the setting of parent permissions if it's a standard object

By granting any access to a custom object that is M/D to a standard object, that necessitates giving access to that standard object as well.

Managed package permission sets can't grant any access to a standard object, so this is blocked!

Improve this answer
1
  • 2
    WInner winner! Thanks for the help, I need to remove the M-D field on my custom object and replace it with a lookup field.
    – techbusinessman
    Feb 6, 2016 at 20:57

You must log in to answer this question.

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