The curious case of the case entity
I believe most people know about this: in the case entity, there are 2 attributes that can be used to map a case to either an account and/or a contact.
These 2 attributes are:
- customerid
- responsiblecontactid
What if your client’s business requirements tell you to put both information on the case form? Let me explain: my client wants to be able to track from which contact the incident originated and for which account, resulting in a double way on how to find the incident.
You might say “All right dude, this is easy! Let’s put both the attributes on the form and it will solve the problem right away”. Yes it can, alas for my client it will not! “But why?” will you ask me, it looks like you can designate both the contact and the account on the case, so it’s OK. But no. “Why not?”
Well, if you designate a responsible contact on a case, the case will not be linked to the contact in the contact form detail!
