2c:T4c2,

Hey 👋

I see there is a new update which replaces the "Write to other table" function.
Now this function is called called "send table data".

The fact you can more rapidly and easier select your columns you want to write to other table is great.
However there's a major setback I noticed, not sure if I'm doing something wrong but i tested it in multiple ways and cant seem to make it work.

What's the setback:
The fact that even if you match column names and data types in both tables they don't automatically populate.
Which means if I send data from multiple sources to 1 table that acts as a master table, the columns that are the same are imported as separate columns.
This is a big problem!

e.g:
I have a company qualification table with multiple AI/enrichment steps that rely on placeholders (column names).
But now each time I import from a different source it's automatically split into a "new column name" even if its exactly the same name and data type it will just default to "same name and type (2)"
So now the flow in that table cant work on autopilot anymore.

Any idea how to solve this?

2d:T44c, I see there is a new update which replaces the "Write to other table" function. Now this function is called called "send table data". The fact you can more rapidly and easier select your columns you want to write to other table is great. However there's a major setback I noticed, not sure if I'm doing something wrong but i tested it in multiple ways and cant seem to make it work. What's the setback: The fact that even if you match column names and data types in both tables they don't automatically populate. Which means if I send data from multiple sources to 1 table that acts as a master table, the columns that are the same are imported as separate columns. This is a big problem! e.g: I have a company qualification table with multiple AI/enrichment steps that rely on placeholders (column names). Bu