Thanks @KyleJepson That makes sense.
The situation is that we have sales reps working their sales processes towards say 50 of total 100 companies underneath a parent company. Let’s call the parent company “Tomato Group”. Then Tomato Group has 100 locations with names along the lines of Tomato Dublin, Tomato London, Tomato Manchester, etc. 50 of these locations are in sales processes with our sales reps. Would it be smart if we created a custom objects for “locations”, so that we could see all these locations from the “Tomato group” company record?
This would also make it better for our sales reps to easier manage their sales processes, as with “location” as a custom object, I assume they can associate deals to the respective locations, rather than associating all deals from a tomato location to the parent company (Tomato Group), as is the case today.
Lastly, we would also like to see from all the Tomato location records that “Tomato group” is the parent company. In my head custom objects sounds much better than creating custom properties for this matter, and I can’t really see a good way of handling this using custom properties instead. Do you agree?
And by the way, sorry for the Tomato-example. I have no idea why I chose that as my example company name. I must really like tomatoes I guess..
Thanks!