ContributionsMost RecentMost LikesSolutionsRe: Need help adding multiple children conditionallyAlright I'll give that a shot. So if I had a conditional Multi-Select field I would: Make a number field: =1 Make a formula text field: [Test_i]=Part(ToText( ),[Counter],";") Trigger an automation to do the following: 1) Create related child i 2) Copy parent [Test_i] to child [Test] 3) In parent, =+1 4) Repeat if [Test_i] is not blank Re: Need help adding multiple children conditionallyIs it possible to chain that url together with a save? So at the bottom of the edit mode you can click a button, it creates the Request, adds the blank children, then moves you back into edit with the blank children? Alternatively, I had mentioned a Multi-Select Field. I could've set it to trigger an automation and fill in the child records without secondary intervention. Is it possible to restrict the list?Re: Need help adding multiple children conditionallyHey thanks for replying. It's not as simple as it appears. If users were expected to click "Add New Test" it would be very simple because the parent record would save and the child would be created with the CDD. I however want my users to use one form to add the child records all at once, then save. This can be 10+ children all with different [Test Names]. The complexity lies in the fact that when you create a new parent record, it doesn't immediately create a [Record ID#] or the parent [Test Category] until you save. In addition, using a grid-edit embedded report, doesn't drop the [Test Category] to the child record until that child record is created itself. You would have to add a field (let's say [Test#]) to initialize the child record before the CDD would work. If the child is not initialized first QB throws a "This Field is dependent" error. Thus I would have to instruct my users to fill out the sample information, save, edit, add child in grid-edit using the [Test#] as the first field. I don't want them to have to save then edit.Need help adding multiple children conditionallyHello. I currently have a setup where Requests < Tests. I have a 3rd Methods table which has 2 fields: "Test Name" and "Test Category". In the Requests page, I would like people to input their sample information and select the "Test Category" from a drop-down. Based on this field, I am trying to limit the choices of their "Test Names" in the Tests table. I cannot figure out a way to allow them to enter multiple tests with the conditional implementation. I tried a few things already but nothing seems great. Idea 1) I tried a grid-edit embedded report. I made an automation to generate 10 blank related Tests when a report is created but it takes a lot of steps: Create the Request, save, reload after automation, edit Record, select Test Name from dropdown on blank children, and save. This is obviously not ideal. I'm trying to get AJAX scrolling enabled which may help by only loading the embedded report after the automation has run. Idea 2) The other idea I had was to create one connected table per Test Category and use dynamic form rules to bring up the correct Multi-Select Text field. Then when everything is saved run a looping automation to create the child records. This is pretty messy and requires a lot of overhead but is WAY more user friendly. Can someone please let me know if there is a better way to accomplish this?Re: Quickbase Action Add Child Record with Grandchild Text look-upSo there is a field call [Related Table C] which uses the [Record ID#] although i just use the proxy field. I cannot seem to write numeric values either. The only fields that show as editable within the QB Action page are the regular text fieldsQuickbase Action Add Child Record with Grandchild Text look-upHello, I am trying to set up a quickbase action to add multiple child records to another table. This works fine but I cannot write values to a dropdown list that comes from the other table. Basically the action in Table A causes multiple entries in Table B. One of the fields in Table B is a dropdown with entries from Table C. I cannot write entries into this field for some reason. Is there a work around for this?