We have created a custom entity called Property. This entity has a many to
one relationship to the Contact entity so that one Contact can be associated
with many Properties. The Property entity is also related one to many to
Opportunity so that one property can be associated with many Opportunities.
We are not using the Account entity in CRM and have therefore not granted
any priveledges for the Account entity to any users. This way, the Account
entity will not show up on users wonderbar, menus, lookups, etc. Having done
this, Account is removed from being one of the record type options when doing
a lookup on the Customer field on Opportunity which is great because now
users cannot accidentally select and account record as an opportunity
customer.
With our one Property to many Opportunities relationship we have mapped the
Property Contact field to the Opportunity Customer field in order to have
that information populate the opportunity when a new one is created from
Property. When the user attempts to to this however, they get an error
message that they have "insufficient permissions".
If I grant the users read access to the Account entity, then this error does
not happen when they attempt to create an opportunity from a property. So it
appears that the CRM user needs Account Read permissions to map to the
Customer field on Opportunity from Property. I suspect that this is because
the lookup on the Customer field in Opportunity can use either the Account or
Contact entities even though we are only putting contacts in the field.
This presents a problem to us however in that if we grant the Account Read
priveledge to users in order to work around this error message, then the
Account entity shows up in all of the menus and lookups which we feel will be
very confusing to the users. Yes, we could work around this by renaming the
Account entity to something like "Do Not Use" but I think you will agree that
this is an inelegant solution. We can also do a certain amount of cleanup
using the Site Map entity, but this does not solve the problem througout the
whole system. The Account entity still shows up as one of the entity type
options in the lookups for the Regarding field on Activities and on the
Customer field in Opportunities for example.
Oddly, if I create an new Opportunity from a Contact, it does not give the
error message even though I am still trying to map a contact in to the
Customer field in Opportunity.
Does anyone have any ideas on how I can work around this issue elegantly?
