3 ms·
Oh I get it. But as I said in another response below, what you're describing is the stage of a contact, not separate objects (in my opinion). You could just as
by inthewoods 5y ago
Oh I get it. But as I said in another response below, what you're describing is the stage of a contact, not separate objects (in my opinion). You could just as easily have a single object but where the status was "lead" (no company name needed) and "contact" where you add the company information and the ability to add them to an opportunity.
- kube-system 5y agoYou’re right, it could be done that way, but for the orgs that do use leads, it would mean a lot of repetitive filtering on pretty much every business process. The difference in functional concept between a lead and a contact are great enough that processes (both software and human) between the two rarely overlap. A foreign key does all of this for free. For this reason, I think they made the right choice, especially since the orgs that do not like the concept of leads can just simply not use them.
- inthewoods 5y agoSadly it is not that easy if you do not want to use them - if that would true I would not be complaining.