Forum Discussion
IvanWeiss
6 years agoQrew Captain
Evan, thanks for the response! not quite right though. I am not referring to an internal hierarchy. I am referring to a client hierarchy. For example our largest client has the following Hierarchy:
So in essence a pyramid type of setup with (4) layers. If I pick any contact towards the top of the list I should be able to see all of their opportunities underneath them.
So if I view the President, I see the entire pyramid. If I pick a RVP I get the DM and GM opportunities reporting up to that RVP, etc.
------------------------------
Ivan Weiss
------------------------------
- President of the Division
- Multiple Regional Vice Presidents reporting to the President
- Multiple District Managers reporting to each Regional Vice President
- Multiple General Managers reporting to each District Manager
So in essence a pyramid type of setup with (4) layers. If I pick any contact towards the top of the list I should be able to see all of their opportunities underneath them.
So if I view the President, I see the entire pyramid. If I pick a RVP I get the DM and GM opportunities reporting up to that RVP, etc.
------------------------------
Ivan Weiss
------------------------------
EvanWestbrook
6 years agoQrew Cadet
Ivan,
Thanks for the clarification. I'm going to assume your client list table is called "Clients."
I think an additional table to track hierarchies is still the direction you want to go (maybe a separate table for each hierarchy step if it's going to remain fairly static.) If you relate Clients to Clients, you'll have to add a new table relationship for each additional field (not fun.) Having Parent records automatically know their Children or Grandchildren could get tricky, but once you figure that out, it will be simpler to manage.
From there, you can set up report links to display the information your form. Lookup fields counting the total # of Child records for each hierarchy step can then feed form rules to display different aspects of the Client form.
------------------------------
Evan Westbrook
PRIME Developer
Harder Mechanical Contractors Inc.
Portland OR
------------------------------
Thanks for the clarification. I'm going to assume your client list table is called "Clients."
I think an additional table to track hierarchies is still the direction you want to go (maybe a separate table for each hierarchy step if it's going to remain fairly static.) If you relate Clients to Clients, you'll have to add a new table relationship for each additional field (not fun.) Having Parent records automatically know their Children or Grandchildren could get tricky, but once you figure that out, it will be simpler to manage.
From there, you can set up report links to display the information your form. Lookup fields counting the total # of Child records for each hierarchy step can then feed form rules to display different aspects of the Client form.
------------------------------
Evan Westbrook
PRIME Developer
Harder Mechanical Contractors Inc.
Portland OR
------------------------------