Duplicate Connected Records

Duplicating connected records enables you to import many records belonging to this or another record and re-assign them accordingly. 

For example: 

Suppose a specific job has 5 tasks that must be completed each time this job is added. We can create trigger a pipe that will allow us to select another job to be used as the template and add all those tasks to the new job created. 

As you can see in the screenshot below, we have a Jobs table and a Tasks table. Each Job has many Tasks. 

 

Let's see how to go about importing all tasks connected to another record into a newly created record. 

Install Pipe

To get started, first install the Tadabase Record utility pipe. 

 

Add API Credentials

Once you have the Pipe installed, add your API credentials which can be found in your app settings into the Global Parameters tab. 

API-Keys-record-pipes.jpg

 

Utilize the Pipe

To utilize the pipe we must ensure we have our data tables set up as follows. 

  • Jobs table. As you can see in the Jobs table we have an extra field called "Import Tasks From" and its a connection to this same Jobs table
    •  
  • Tasks table. In the tasks table, we have a simple table with a connection from each task to its parent job. 

All said and done, our relationship diagram looks as follows: 

Next, we must take note of the ID's of the tables and fields being used and the Join field being used in that table. 

Our Tasks table ID: eykNOvrDY3

and the join field: field_48 

Finally, inside the form where we add a new job we can now set up the pipe to do the import for us. 

We must set a few parameters. 

  1. Import records from this table. This is the table we want to import the records from. In our case its the Tasks table. So we enter a custom value of the Table ID. 
  2. Which are connected to this record. This is the record for the job template we'll choose. So we choose a record value of the field we'll be using to do this import. 
  3. Using this field. This will be the field that connects the tasks to the job. In our case field_48. 
  4. Assign them to this record. This will be the new record we are creating now. So we'll choose Record Value of {Record ID}.  

Keep in mind, pipes run based on values you wish to set. Therefore, there must be a value in the rule that is being set based on the response from a pipe. 

As you can see in the screenshot below, we created a field in the table called "Duplicate" and we set that value to Pipe Value of Status. 

If we don't set a value to be utilized from the response, this Pipe does not get triggered. 

 

import-child-gif.gif