We want to implement Contacts to Multiple Accounts. But how do I enforce that the Contact and Account are at least indirectly related? The lookup filters don't seem to be able to look at the Account Contact Relationship object.
Also, with email to case, I know it would automatically assign the Primary Account as the default account associated with the case that is created. But how do I open that Account field so that they can change it to any of the Accounts where they have an indirect relationship, but NOT to some random Account that isn't related to the contact at all?
That's the problem we were having to start with - people choosing a Contact and Account that were unrelated, and we didn't know if the case was for the Account that was related to the Contact or the Account that was chosen in the Account field. We have to have some way to enforce that the two are related. But we HATE having so many duplicate contacts just so we can enforce the correct data entry on Cases. I'd love to use the contacts to multiple accounts function, but I can't figure out how to allow this indirect relationship without opening it all the way and letting people pick an account that might have nothing to do with the chosen contact.
I know we're not the only ones with this dilemma. How have others handled this?
2 件の回答
Thanks, Ben. This seems to always be the answer when I try to use a new feature. It seems so great on the surface, but when you go to use it, it's not *quite* all the way finished. So frustrating to be so close, but still impossible.
I went to the idea and upvoted and commented. I'll try to be an optimist today and believe that will help. Thank you for *your* help!
