Issue with 'Write to Table' Step Not Updating Specific Column

I'm trying to update the "Write to Table" step by adding a new field. The mapping appears correctly in the configuration and is clearly visible in the destination table. Data is being written successfully to all other columns, but for some reason, it's not getting written to this specific column. This issue is occurring only with the 'People' table. The same data is correctly flowing into other 'Write to Table' steps within the same workflow. Screenshot attached below for reference. I also tried creating a new column again didn't work. see sap_skill_comma column in below screenshot.

🎫1

12 comments

· Sorted by Oldest

Abdul Sa. (Clay Expert)
·
·
Hey Bhanu Singh If the sap_skill_comma field is mapped correctly but not writing to the 'people' table, a few things to check: Make sure the column type matches the data you're sending Confirm you're referencing the right column (especially if it was recently recreated) Try writing to that column manually in the table to test it Double check if any filters or conditions might be skipping it
Bhanu Singh
·
·
1.
Yes the type is correct
2.
Yes I am able to write data manually OR via a work around ( performed a lookup from 'People table' to 'company table' to get the same column value and that worked too.
3.
No filters are applied.
Abdul Sa. (Clay Expert)
Abdul Sa. (Clay Expert)
·
·
that helps narrow things down since the column works with a workaround but not directly in the “people” table it might be a bug or sync issue
Siddhant Bhansali (Certified Clay Expert)
·
·
Bhanu Singh - share what the Write to Table looks like.
Clay
APP
·
·
Since the column works with a workaround but not directly in the "write to table" step, try these troubleshooting steps: 1. Delete and recreate the column: Delete the affected sap_skill_comma column, create a fresh column, then re-map your data to the write to table step. 2. Use Force Run: Try using the Force Run option in the table settings, which may take some time depending on your table size. 3. Check for misconfiguration: Ensure you're not writing to a deleted column or sending data to a table that references another table, as this can cause write failures. If the issue persists after these steps, it may indicate a sync issue that requires further investigation.
Source: Write to Other Table | Documentation | Clay University
Siddhant Bhansali (Certified Clay Expert)
·
·
Bhanu Singh - did this get sorted out?
Clay
APP
·
·
Based on the troubleshooting steps we provided earlier, here are the key solutions to try if the sap_skill_comma column still isn't writing properly: Delete and recreate the column: Delete the affected sap_skill_comma column, create a fresh column, then re-map your data to the write to table step. Use Force Run: Try using the Force Run option in the table settings, which may take some time depending on your table size. Check for misconfiguration: Ensure you're not writing to a deleted column or sending data to a table that references another table, as this can cause write failures. Since the column works with your workaround but not directly, this suggests a sync issue that should resolve with these steps.
Source: Write to Other Table | Documentation | Clay University
Sayli Godse
·
·
Hello Bhanu! Thanks for reaching out! Can you share your table link URL so that I can take a look? Mapping can be tricky because WTT simply sends data as additional rows to another table and does not exactly map. If you have a common column in both tables you would like to map, you can perform a lookup. However I just want to ensure that is the case before I give you any recommendations so would like to see the tables first! :)
Bhanu Singh
·
·
Sending From Table - https://app.clay.com/workspaces/39601/workbooks/wb_6HyESRMSPnDU/tables/t_yyZOKlMfcYp7/views/gv_sLmxB2eJua1O Sending into - https://app.clay.com/workspaces/39601/workbooks/wb_6HyESRMSPnDU/tables/t_iyen4PVo4SI5/views/gv_VcwOx1pV3Z9D Sayli Godse
Bhanu Singh
·
·
check the write to table below Siddhant Bhansali (Certified Clay Expert) it contains two entries. because I tried creating new column as per Clay Support 's recommendation, didn't work!
Sayli Godse
·
·
Hey Bhanu! Some follow up on this: Can you guide me to the columns which show up in the destination table on performing WTT and the rows which did not get mapped correctly? The table has a lot of columns so would like to get some more context to narrow it down faster!
Channeled
APP
·
·

Abdul Sa. (Clay Expert)
·
·
Hey Bhanu Singh If the sap_skill_comma field is mapped correctly but not writing to the 'people' table, a few things to check: Make sure the column type matches the data you're sending Confirm you're referencing the right column (especially if it was recently recreated) Try writing to that column manually in the table to test it Double check if any filters or conditions might be skipping it
Bhanu Singh
·
·
1.
Yes the type is correct
2.
Yes I am able to write data manually OR via a work around ( performed a lookup from 'People table' to 'company table' to get the same column value and that worked too.
3.
No filters are applied.
Abdul Sa. (Clay Expert)
Abdul Sa. (Clay Expert)
·
·
that helps narrow things down since the column works with a workaround but not directly in the “people” table it might be a bug or sync issue
Siddhant Bhansali (Certified Clay Expert)
·
·
Bhanu Singh - share what the Write to Table looks like.
Clay
APP
·
·
Since the column works with a workaround but not directly in the "write to table" step, try these troubleshooting steps: 1. Delete and recreate the column: Delete the affected sap_skill_comma column, create a fresh column, then re-map your data to the write to table step. 2. Use Force Run: Try using the Force Run option in the table settings, which may take some time depending on your table size. 3. Check for misconfiguration: Ensure you're not writing to a deleted column or sending data to a table that references another table, as this can cause write failures. If the issue persists after these steps, it may indicate a sync issue that requires further investigation.
Source: Write to Other Table | Documentation | Clay University
Siddhant Bhansali (Certified Clay Expert)
·
·
Bhanu Singh - did this get sorted out?
Clay
APP
·
·
Based on the troubleshooting steps we provided earlier, here are the key solutions to try if the sap_skill_comma column still isn't writing properly: Delete and recreate the column: Delete the affected sap_skill_comma column, create a fresh column, then re-map your data to the write to table step. Use Force Run: Try using the Force Run option in the table settings, which may take some time depending on your table size. Check for misconfiguration: Ensure you're not writing to a deleted column or sending data to a table that references another table, as this can cause write failures. Since the column works with your workaround but not directly, this suggests a sync issue that should resolve with these steps.
Source: Write to Other Table | Documentation | Clay University
Sayli Godse
·
·
Hello Bhanu! Thanks for reaching out! Can you share your table link URL so that I can take a look? Mapping can be tricky because WTT simply sends data as additional rows to another table and does not exactly map. If you have a common column in both tables you would like to map, you can perform a lookup. However I just want to ensure that is the case before I give you any recommendations so would like to see the tables first! :)
Bhanu Singh
·
·
Sending From Table - https://app.clay.com/workspaces/39601/workbooks/wb_6HyESRMSPnDU/tables/t_yyZOKlMfcYp7/views/gv_sLmxB2eJua1O Sending into - https://app.clay.com/workspaces/39601/workbooks/wb_6HyESRMSPnDU/tables/t_iyen4PVo4SI5/views/gv_VcwOx1pV3Z9D Sayli Godse
Bhanu Singh
·
·
check the write to table below Siddhant Bhansali (Certified Clay Expert) it contains two entries. because I tried creating new column as per Clay Support 's recommendation, didn't work!
Sayli Godse
·
·
Hey Bhanu! Some follow up on this: Can you guide me to the columns which show up in the destination table on performing WTT and the rows which did not get mapped correctly? The table has a lot of columns so would like to get some more context to narrow it down faster!
Channeled
APP
·
·