The other day, our client brought an interesting issue to our attention. On the address form, both the ‘Save’ and ‘Save and Close’ buttons were missing on the header of the form; the address record could not be saved and linked to a contact record.
Our first inkling was a caching issue, but we were later informed all users with the exception of the a few – those with the System Administrator role – were experiencing this problem.
This notion led us to the belief that the issue was security related, yet we were quiet confident that no specific privilege related to the address entity. Our initial thoughts were the ‘Append’ and ‘Append To’ on the Contact entity (afterall, we do associate the address record to a contact). That did not work.
The remaining privileges for the Contact entity were in order.
What was going on?
As it turns out, CRM also expects the Write privilege on the Account (Company) entity in order to save an address record for a contact.
There is some truth that the address record form is shared between contact and account records, but I would not have expected to expose privileges on one entity, in order to allow a particular action for another.
We leave this question open to the community for a better explanation, workaround, or fix.