Forum Discussion
MarkComish
7 years agoQrew Assistant Captain
Wow I really appreciate all the info. I think I will make a copy of my app and try to make all the changes and if I mess up I can use the copy too make sure I am back to where I started. I will give it a shot and let you know how it goes.
- MarkComish7 years agoQrew Assistant CaptainOne thing I didn't think about is "Opportunities" Table. Sometimes an opportunity will be related the the Parent Company and sometimes the Subsidiary Company. I guess if I copy the "Companies" Table and rename the copy to "Subsidiaries" table it would retain all the relationships created? Then I can just edit the data based on which Table it is in?
- AnnaKelley7 years agoQrew MemberI would probably relate Opportunities to both Parent Company and Subsidiary company tables - meaning Opportunities would become a child table to both Parent and Subsidiary tables. Then, if I want to have a master record of all Parent company AND Subsidiary company opportunities, I'd pull through theOpportunities from the Subsidiary to the Parent company table with summary fields or embedded reports.
I'm better at drawing out the relationship than typing it out but I'd describe it exactly as Evan depicted in his initial response to you, except replace Contacts with Opportunities. Hope that makes sense. - EvanMartinez7 years agoQrew EliteHi Mark,
I would agree with Anna that you could replicate this build to share Opportunities as well. This way a Parent company can have Opportunities and a Subsidiary could have their own opportunities.