2

I put a custom object into a managed package, and installed that package into another organization. I can see the custom object in the interface just fine - it shows up under the managed package area, and I can write reports against it, but I'm getting 404s on hitting the REST API for it. I am checking that the namespace is correct. What else should I be looking at? Object permissions? API permissions?

Improve this question
1
  • 1
    Ah! The Standard User doesn't come with access to custom objects provided by packages. I'm not sure what to do to fix it.
    – freyley
    Jan 7, 2015 at 23:25

1 Answer 1

Reset to default
1

When you install a managed package in an org, you have to be sure to choose "Available to all users" in order for everyone to have access to custom objects within it.

Your options now are to either remove and re-install the package selecting this option (the easy way!), or to create custom profiles and reassign all of the users who need access to the new profiles.

One other side note, even when you do have access, remember that you'll need to use the package namespace prefix to access the objects as well.

Improve this answer
1
  • I did check 'Available to all users' - users can see the custom object in the interface, just not access it in the API. The 'Standard User' profile doesn't seem to have API access to custom objects by default.
    – freyley
    Jan 8, 2015 at 6:32

You must log in to answer this question.

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