Ability to Associate Custom Object with Company Instead of Contact
J
Janeale Dean
We currently set up a custom object to log serial numbers for B2B purchases and their warranty start/end dates. Currently you have to associate it with a contact, this is "okay" for now, but if that contact ever chooses to leave their company, all associated purchased product serial numbers will have to be reassociated with another contact. Not only this, but when someone calls in for repair/RMA/support, it could be a totally different contact than who purchased the product.
Log In
C
Chris Fairchild
I have the same request, with a different use case. For a company that has many locations, and several contacts at each location, we would want to create a "parent company" (or similar name) object and allow a one-to-many association so several companies could be associated with the parent. Then we should be able to view associated companies, opportunities, and contacts, along with relevant activities all under that parent.
That's the purpose of a custom object though - they should be customizable to fit whatever use-case the object is created for. Tying custom objects indelibly to contacts renders them useless for many conceivable use-cases.