Hi, in some cases the row from send to table can be expanded (so I don't have to add all values as new columns in to table to be able to reference them) and in other cases I can't. These screenshots will explain, these are from two different workspaces. In one image I can just use the data out of the table without making a new column, in the other one I was forced to create the columns. This large amount of columns is not ideal in terms of table length...
The ability to expand rows from "send table data" depends on the data structure being sent. When data contains nested endpoints or arrays, you can expand them directly in the destination table. However, if the data is sent as flat values without nested structure, you'll need to create individual columns to access each piece of data. The difference between your workspaces likely stems from how the original data was structured - one contains expandable nested data while the other contains flat data that requires separate column mapping.
These are the kind of fields that are being sent
Hi Sem, thank you for reaching out! If you are sending data using 'Send Table Data' then in the destination table the data that you get would be referenceable in other columns in the same table without having to add them as columns. But if you want to send the data again to new table through 'Send Table Data' then you would have to extract it as columns first.
Hi Smit V. the screenshot that shows that I have to create extra columns is actually the destination table. So it goes from table A to Table B, but it's not referenceable without creating new columns for it. The data gets sent from the "Enrichment Persoon" table to the "Output" table, this is the workbook link: https://app.clay.com/workspaces/397233/workbooks/wb_YY6noj7bkasS/tables/t_eYCjCrAAR9DP/views/gv_4ANJTgXYfx5E
I'm not sure what you mean exactly here. Do you mind creating a quick loom or some screen recording going over it? That will really help clarify what's going on :)