How can I pull data into a child table from the parent's other child table?

  • 1
  • 1
  • Question
  • Updated 3 months ago
  • In Progress
Hello!! First post. Excited to see where it takes me.

I have 3 tables: Work Orders, Subdivisions, Locations. Both Work Orders & Locations are children tables to Subdivisions. A subdivision can have many locations, and a Subdivision can have many work orders.

A Location is an address.

When I open the work order form, to add a new work order, one of the fields is a drop down of all previous subdivisions. I can select one or add a new one if needs be. Works great.

I would like to add another field, preferably labeled Location, where when I select a subdivision from the drop down menu (as detailed above), the location's drop down will only give me a list of locations associated with the selected subdivision.

However, with how I currently have it, even if I select a subdivision, it gives me all of the locations, regardless of the subdivision.

Any ideas?

Again, I am excited to see where this will take me and appreciate everyone's time and willingness to assist.
Photo of Andrew Fry

Andrew Fry

  • 142 Points 100 badge 2x thumb
  • confident

Posted 3 months ago

  • 1
  • 1
Assuming you have it set up that Locations have many work orders via relationship- you can edit your reference field - Related Location to be a conditional dropdown in the field settings and make the selection of the location conditional on what you've already selected in sub-division. Its pretty straight-forward to set it up via this conditional dropdown setting to only show locations related to that subdivision



Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Photo of Andrew Fry

Andrew Fry

  • 142 Points 100 badge 2x thumb
Thanks Chauncey!! I will give it a try. I hadn't thought of a conditional drop down.

Currently I don't have a Work Orders - Locations relationship set up.

So you are saying to have it set up as one work order to many locations, correct?

So in actuality, a single work order will have a single location for that work order. But I guess that if I needed to generate a new work order for the same location later on, then it would in fact be a On location multi work order relationship.

I will give it a try! Thanks for the tips.
From how I'm reading it - Locations will have many work orders so Locations is your parent table. As you stated, over time, you could have hundreds of works orders at that same location, so Work Orders will be the child table. 



Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Photo of Andrew Fry

Andrew Fry

  • 142 Points 100 badge 2x thumb
Chayce, Thanks a ton for the info and the link to the blog!! Read through it, made a ton of sense. Thanks again!!