Issue Adding New Column to Write to Table Functionality

You need to re-run the company row in the people table to make newly created columns visible in other table formulas. Force run through the whole column to see the new values. If the column still isn't processing correctly, try these steps: 1. Delete the affected column 2. Create a fresh column 3. Re-map your data to the write to table (ensure auto-dedup is activated in the destination table)

Since you've already tried re-running and recreating the column, try these additional steps: 1. Use Force Run in the table settings - this may take time depending on your table size 2. Re-map your data to the write to table and ensure auto-dedup is activated in the destination table 3. When mapping columns, make sure to select the columns you want to copy from the source table and match them to the appropriate columns in the destination table 4. If mapping individual columns (not lists), enter "/" to skip list selection during the mapping process The key is ensuring the column mapping is properly configured between your source and destination tables after the column recreation.

Sources: Write to Other Table | Documentation | Clay University Write to Other Table | Documentation | Clay University

Hey Dan, thanks for that table link and screenshot. I'll have a look and see what's going awry.

I re-ran the 'Company Table Data' cell in the first row. When I view the cell details there, I see the 'Sector Result' value came in. And then the Write to Table recognized it being available:

Those 'Company Table Data' aren't like traditional action columns. They're more to illustrate the link between tables, than to be configurable/re-runnable. Using the Lookup Rows feature can help you do this more flexibly – good tool for similar use cases in the future! https://www.clay.com/university/guide/lookup-rows

Which one(s) can you not do now?

I described the solution and illustrated it in my last messages. Are you not seeing the same option? What do you see?

You're welcome! I like to think of those 'Company Table Data' as a like a "snapshot" of the columns in the company table, at the time that new people row was created. Ditto for Lookup columns in Clay. So if the data where you're fetching data has new stuff available (e.g. new columns; columns re-run with different results), then the lookups will need to re-run to fetch the latest. I think you've got what you needed here, so I'll tentatively mark this closed for the moment. But please keep in touch if you hit other roadblocks – here to help.

'Company Table Data' is the name of the second column in your table. I re-ran only the 'Company Table Data' cell in the first row. Re-run the rest at your leisure.