Ask Search:
Julia StewartJulia Stewart 

Insufficient privileges error when user tries to create new record

Problem: I've created a new custom object called "Postsecondary Resource." The object contains two lookup fields, for an account and a contact.  For one of my users, when they go to the Postsecondary Resources tab and hit "new," they get an insufficient privileges error.

Troubleshooting: 
  • I logged in as the user and confirmed the error.
  • I logged in as the user and tried cloning a Postsecondary Resource, which worked.
  • I reviewed the users' profile.  The profile has all permissions (Read, Create, Edit, Delete, View All, Modify All) for all three objects (Postsecondary Resources, Accounts, and Contacts).
Any ideas?  I don't understand how it could be related to sharing rules, since the user is trying to create a NEW record, not modify any existing record.
Best Answer chosen by Julia Stewart
Will UlmerWill Ulmer
Julia, I would tend to agree with you about sharing rules b/c you are trying to create a new record, which is normally owned by the creator. The OWD for the objects should not matter since you are giving "Modify All" on the profile, even if something was immediately transferring record ownership to another user upon insertion of the record. Is there anything like that?

Which leads me to think, is there some custom code involved? Are you potentially overriding the New button and using a custom Visualforce page to input the PostSecondary Resource record? In which case the user might not have access to the VF page and thus receives insufficient privileges.


 

All Answers

Will UlmerWill Ulmer
Julia, I would tend to agree with you about sharing rules b/c you are trying to create a new record, which is normally owned by the creator. The OWD for the objects should not matter since you are giving "Modify All" on the profile, even if something was immediately transferring record ownership to another user upon insertion of the record. Is there anything like that?

Which leads me to think, is there some custom code involved? Are you potentially overriding the New button and using a custom Visualforce page to input the PostSecondary Resource record? In which case the user might not have access to the VF page and thus receives insufficient privileges.


 
This was selected as the best answer
Geoffrey FlynnGeoffrey Flynn
Any chance you replaced the New button with a Visualforce page?  Or with a URL hack of some kind.  If it's the standard button being used then there shouldn't be an issue
Julia StewartJulia Stewart
Thanks so much, Will and Geoffrey!  We were overriding the New button and using a custom Visualforce page to input a default value in the standard "Name" field.  I updated the security on that Visualforce page to include all profiles, and that resolved the issue.  Thank you!