Hi all,
I have two tables I have related: Work Requests(Child Table) and Teams(Parent Table)
I am trying to figure out some sort of button, whether it ends up being IOL or formula URL button, that grabs the values from a multi-line text field within the form of the parent record(this would be a list of the work requests [WR #] that relate to the child record) and relates it to the parent record(the team).
Something similar to this:
where we can enter in the work request numbers, save, then click the "Add Jobs" button to change the value of [Related Team] in the each of the listed child records to the related team of the parent record being viewed. It would then clear the value of [Job Add List], but this part is easy to add in.
Can anyone help me with this?
I open to suggestions, automations, webhooks, IOL, etc.
Thanks!
Question
Add existing Child Records to Parent Record from List
+12Just some clarification first. When you enter a Work Request, and identify the 3 Jobs (in your example). Are you then creating another set of child-records (Jobs) against the Work Order which are then needing to be connected to the correct Teams?
Teams < Jobs > Work Requests
Are you creating 1 work request and trying to create "copies" of the Work Request each one associated to the correct "Team" parent? Or, do you have multiple relationships within the Work Request and each one needs to connect to a different Team?
It is not clear in your 2-table structure how the "Jobs" component factors in.
If you are, in fact, having a 3 table (Teams < Jobs > Work Requests) - how do you determine which Team should be the parent of a job?
Teams < Jobs > Work Requests
Are you creating 1 work request and trying to create "copies" of the Work Request each one associated to the correct "Team" parent? Or, do you have multiple relationships within the Work Request and each one needs to connect to a different Team?
It is not clear in your 2-table structure how the "Jobs" component factors in.
If you are, in fact, having a 3 table (Teams < Jobs > Work Requests) - how do you determine which Team should be the parent of a job?
Sorry for the misunderstanding!
I am using jobs as a general term for work request. All Work Request numbers are unique. When I say Job, it's because each work request also has a job# that is not unique. We have multiple districts(Longview, Shreveport, Texarkana, etc.) and they each have their own job#s. So there is a Longview Job# 1 and also a Shreveport Job#1, we don't have a separate "Jobs" table. The job# isn't anything that has to be messed with in this particular situation; i just used it out of habit.
Currently, the "Teams" table basically holds shells where we can edit the technicians and work requests on a day to day basis. The teams are: ALPHA, BETA, CHARLIE, etc.. One day, Team Echo could have technicians, john and jane, and work requests, 61254638 and 71555643, and then a separate set of technicians and work requests the next day. I have any easy way of taking jobs off of the team using an embedded report of the related Work Requests in the team record with a URL button in each row that clears the value in the field "Related Team" but I can't do the same with adding work requests to the team. A team will only ever have up to 10 Work request assigned to it at once, so removing them is not that hard, but we have over 3000 work requests total, so adding from an embedded report would be a nightmare. That's why a simple list with a button would be most efficient.
For this particular case, our field manager will go to the "Teams" table, click on team "Echo" then assign field technicians to the team then enter in the list of work requests he wants that team to work and click the "Add Job" button to have those work request linked to that team by automatically changing the value in the field "Related Team" in each of the listed Work Requests.
I am using jobs as a general term for work request. All Work Request numbers are unique. When I say Job, it's because each work request also has a job# that is not unique. We have multiple districts(Longview, Shreveport, Texarkana, etc.) and they each have their own job#s. So there is a Longview Job# 1 and also a Shreveport Job#1, we don't have a separate "Jobs" table. The job# isn't anything that has to be messed with in this particular situation; i just used it out of habit.
Currently, the "Teams" table basically holds shells where we can edit the technicians and work requests on a day to day basis. The teams are: ALPHA, BETA, CHARLIE, etc.. One day, Team Echo could have technicians, john and jane, and work requests, 61254638 and 71555643, and then a separate set of technicians and work requests the next day. I have any easy way of taking jobs off of the team using an embedded report of the related Work Requests in the team record with a URL button in each row that clears the value in the field "Related Team" but I can't do the same with adding work requests to the team. A team will only ever have up to 10 Work request assigned to it at once, so removing them is not that hard, but we have over 3000 work requests total, so adding from an embedded report would be a nightmare. That's why a simple list with a button would be most efficient.
For this particular case, our field manager will go to the "Teams" table, click on team "Echo" then assign field technicians to the team then enter in the list of work requests he wants that team to work and click the "Add Job" button to have those work request linked to that team by automatically changing the value in the field "Related Team" in each of the listed Work Requests.
Sign up
Already have an account? Login
Login to the community
Login with Quickbase US – quickbase.com Login with Quickbase EU – quickbase.eu
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.