Join Two Tables. Save in other Table

Need help Database
1

Hi fellow bubblers!

I wanna join those two tables “Source” and “Num” on “Var” and fill the information in another table.

I figured there might be the option of using a nested API Workflow or an SQL API.
Though, is there another, simpler way? What will change if I wanna do it scalable?

Thanks for the help!

Source Table
|Var|Source|
|X|A|
|X|B|
|Y|B|
|Y|C|
|Z|A|

Num Table
|Var|Num|
|X|21|
|Y|3|
|Z|7|

Example Result:
SourceNum Table
|Var|Source|Num|
|X|A|21|
|X|B|21|
|Y|B|3|
|Y|C|3|
|Z|A|7|

2

Are you trying to do this on an ongoing basis or do you just have a bunch of data in source and num table and you want to combine it? If the second, then just export both to csv and combine in excel and then upload back to bubble. If the first, then you can do this with backend workflows.

1 Like
3

Thanks for your answer! Yeah, it’s the second option. For that I need a nested backend workflow. Do you know any tutorial about a nested backend workflow?

4

Sorry but I’m confused. If it’s the second option, then why do you need to perform a nested backend workflow? Why don’t you just do the export to csv of both tables, combine in excel and reimport?

The backend workflow is only required if you need it done on an ongoing basis.

5

Sorry! I meant the first option - regular basis so nested backend workflows.
Doing one backend workflow is no problem. Though, the nested backend workflow causes me trouble. So basically, I have a backend workflow that calls a backend workflow that makes the work in the end.
@paul29 do you have experience with that?

6

I’m not sure why you have to create a nested workflow. This tutorial should work for you How to Run a Loop in Bubble.io - YouTube
It’s very similar to his example except your first step will be “create a new SourceNum” and the value will be the “iteration” variable row number of each of your other tables. Then the last step is scheduling the workflow as he has done but run until iteration is <= count of either one of the Source or Num tables.

Although I still am confused as why you need to do this for ongoing bases. Clearly you have actions for create a new source and create a new num, so why not just create a third action that is “create a new sourceNum” which has a value of the result of steps 1 and 2 concatenated with each other?

7

Thanks Paul! The tutorial link is basically a way of do a Workflow on a list. Though, your second input helped me to have a new look on the thing - I now pre-fill a table with the same info of “the base” table and then add the data of the other table.
Thanks!

1 Like