Changes to Table Search and Column Mapping in Our Workspace

Laurent B. · 2025-07-16T21:25:03.975Z

Did something change with table search in column mapping? The dropdown now displays all tables in our workspace - an extremely long list. it seems to be related to duplicate notebooks running into errors, as links between tables break (which I reported here ) any help appreciated! link to notebook:

Changes to Table Search and Column Mapping in Our Workspace | Clay

14 comments

· Sorted by Oldest

Clay
APP
·
·
Performance issues can occur when there are large tables within workbooks and multiple actions running simultaneously, which can manifest as latency issues where cell data takes longer to load. Performance issues are more likely with larger tables or complex workflows, such as tables linked together in a workbook. For "write to table" functions not processing correctly, try using the Force Run option in table settings, which may take time depending on your table size. If issues persist, delete the affected column, create a fresh column, and re-map your data to the write-to-other table (ensure auto-dedup is activated in the other table). Try a hard refresh to troubleshoot performance issues: Mac users can use Command (⌘) + Shift + R for Chrome/Firefox or Option (⌥) + Command (⌘) + E for Safari, while Windows users can use Ctrl + F5 or Ctrl + Shift + R. Are you experiencing this issue specifically when trying to map columns in the "write to table" integration, or is it happening in other column mapping scenarios as well?
Source: Table management settings | Documentation | Clay University
LuisArturo
·
·
Hey there Laurent thanks for reaching out, to clarify here the Lookup table option has always included all other tables to search in. However by default it should start showing you whatever other tables are inside the current workbook you're working in
Laurent B.
·
·
this doesn't solve my issue - why are the connections between tables dropping when duplicating the workbook? this is a new issue in last 2 weeks
Smit V.
·
·
Hi Laurent, thank you for reaching out! Taking a look into it now
Smit V.
·
·
I tried to duplicate the workbook but ran into an error. Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Laurent B.
·
·
thanks Smit V., appreciate you looking into this. when should I expect to get an update?
Smit V.
·
·
The bugs usually takes two weeks to get fixed. We will reach back out as soon as we have an update here. Apologies for any inconvenience this may cause!
Laurent B.
·
·
Hi Smit V. - any update here? this bug is creating a significant missed opportunity for us
Smit V.
·
·
Hi Laurent, haven't heard back from the engineering team yet. Apologies for the inconvenience, but it will take up to 2 weeks from the time we filled the bug to get it fixed. Will circle back as soon as we have an update!
Laurent B.
·
·
Can you help me understand the scope of the issue - is table duplication broken for all users? it seems like a pretty big deal!
Smit V.
·
·
It's actually not completely broken it's only happening in some instances where the workbooks are big or contains a lot of tables. I'll ping the engineers again and see if we can fast track it!
Laurent B.
·
·
hi Smit V. - i just tried again and duplicating the workbook still breaks all the links between tables. did you hear back from engineering? again, this bug is creating a significant opportunity cost for us. 30 SDRs stopped receiving valuable leads
Smit V.
·
·
Heyy Laurent, The fix is not out yet and I don't have a timeline to share. I understand how this can be annoying. That said, I tried recreating the workbook using this shared template URL in your workspace and I was able to create one. Here's the newly created workbook: https://app.clay.com/workspaces/195674/workbooks/wb_0szx4pfSjcdrNVWtxSX/all-tables Could you try that, and let me know how it goes? - Smit
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in Clay Support.

Clay
APP
·
·
Performance issues can occur when there are large tables within workbooks and multiple actions running simultaneously, which can manifest as latency issues where cell data takes longer to load. Performance issues are more likely with larger tables or complex workflows, such as tables linked together in a workbook. For "write to table" functions not processing correctly, try using the Force Run option in table settings, which may take time depending on your table size. If issues persist, delete the affected column, create a fresh column, and re-map your data to the write-to-other table (ensure auto-dedup is activated in the other table). Try a hard refresh to troubleshoot performance issues: Mac users can use Command (⌘) + Shift + R for Chrome/Firefox or Option (⌥) + Command (⌘) + E for Safari, while Windows users can use Ctrl + F5 or Ctrl + Shift + R. Are you experiencing this issue specifically when trying to map columns in the "write to table" integration, or is it happening in other column mapping scenarios as well?
Source: Table management settings | Documentation | Clay University
LuisArturo
·
·
Hey there Laurent thanks for reaching out, to clarify here the Lookup table option has always included all other tables to search in. However by default it should start showing you whatever other tables are inside the current workbook you're working in
Laurent B.
·
·
this doesn't solve my issue - why are the connections between tables dropping when duplicating the workbook? this is a new issue in last 2 weeks
Smit V.
·
·
Hi Laurent, thank you for reaching out! Taking a look into it now
Smit V.
·
·
I tried to duplicate the workbook but ran into an error. Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Laurent B.
·
·
thanks Smit V., appreciate you looking into this. when should I expect to get an update?
Smit V.
·
·
The bugs usually takes two weeks to get fixed. We will reach back out as soon as we have an update here. Apologies for any inconvenience this may cause!
Laurent B.
·
·
Hi Smit V. - any update here? this bug is creating a significant missed opportunity for us
Smit V.
·
·
Hi Laurent, haven't heard back from the engineering team yet. Apologies for the inconvenience, but it will take up to 2 weeks from the time we filled the bug to get it fixed. Will circle back as soon as we have an update!
Laurent B.
·
·
Can you help me understand the scope of the issue - is table duplication broken for all users? it seems like a pretty big deal!
Smit V.
·
·
It's actually not completely broken it's only happening in some instances where the workbooks are big or contains a lot of tables. I'll ping the engineers again and see if we can fast track it!
Laurent B.
·
·
hi Smit V. - i just tried again and duplicating the workbook still breaks all the links between tables. did you hear back from engineering? again, this bug is creating a significant opportunity cost for us. 30 SDRs stopped receiving valuable leads
Smit V.
·
·
Heyy Laurent, The fix is not out yet and I don't have a timeline to share. I understand how this can be annoying. That said, I tried recreating the workbook using this shared template URL in your workspace and I was able to create one. Here's the newly created workbook: https://app.clay.com/workspaces/195674/workbooks/wb_0szx4pfSjcdrNVWtxSX/all-tables Could you try that, and let me know how it goes? - Smit
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in Clay Support.