Task to update a record when the ID match in both tables

[Kuroshi]

How can I create a a task that will update the records on table1 with the information on table 2 when the ID match in both tables? I already have all my records in the table 2that's why I come up with creating a Task instead of a triggered action. Can you help me creating this? 

Thanks.

[Barbie]

Hi @Batchini,

Let's assume that Table 1 is the Child_tbl_ and Table 2 is the Parent_Tbl. You may refer to the Task configuration below:

 

I hope this works on your end. 

- Barbie

[ParkLoey]

Hi everyone, just wanted to add these links too. It helped me a lot when I was just getting started with tasks.

 

https://howto.caspio.com/tasks/

And since Application tasks and Triggers are somewhat similar, these were helpful too.

https://howto.caspio.com/tables-and-views/triggered-actions/

https://www.caspio.com/webinars/introduction-to-triggered-actions/

 

[Kuroshi]

Thank you that worked. Do you also perhaps know How can I insert data from table one to table two when the value of ID is not on table two?
Expected Result: send the information from table 1 to table 2 only if the ID on table 1 is not found in table 2?

[Barbie]

Hi @Batchini,

I understand that you wanted to store the records from table 1 to table 2 if the ID is not existing in table 2. You can refer to this Task configuration that I have created:

Again, with this configuration, let's assume that the Child_tbl_ is the 'Table 2' and the 'Parent_tbl' is the 'Table 1. The records will be inserted in table 2 if the ID of the records from Table 1 does not exist on this specific table.

I hope this works! 

- Barbie

[CoopperBackpack]

Hello @Batchini,

The solution with Left Join should work as well to select the records from Table_1 that do not exist in Table_2 (based on the ID field).
Here is an example of the Task:

[CoopperBackpack]

@Batchini,

If in the future you are going to add new records to Table_1 and want to insert records with unique IDs into the Table_2, you may try this Triggered Action:

Basically, you may use this approach to avoid duplicates and to save only distinct values.

Hope this helps.

 

[NiceDuck]

You may also want to use "Not Exist" instead of "Not in", specially if it involves a lot of records:

 

[jenifferlopez1245]

thanks for this answers

[roattw]

Going back on this.  Could you accomplish both at same time?  Update and records if changes AND insert new records if any found?  Last time I ntried this I kept getting duplicate entries, not updates to exisiting.