https://cln.sh/YhPm58gQ https://app.clay.com/workspaces/9621/workbooks/wb_0sxcxy7kKqncEzZNREz/tables/t_0sxcye0JcmP4qzcUnXo/views/gv_0sxcye0kJxxgDpNtCya Nested JSON arrays don't work with write to other table for me. I need to run this this week, so please help!!
If you're having trouble with nested JSON arrays in write to table, 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 other table) If the value isn't formatted as a proper list, add it through the "Other data from this table" section. You can watch a tutorial here: https://cln.sh/DpHTlNt0 Could you copy and paste your JSON into the chat so I can troubleshoot further?
{ "type": "object", "properties": { "company_name": { "type": "string", "description": "The name of the company" }, "company_domain": { "type": "string", "description": "The company's website domain" }, "linkedin_url": { "type": "string", "description": "The LinkedIn URL for the company" }, "company_description": { "type": "string", "description": "A one-sentence summary of the company" }, "leads": { "type": "array", "items": { "type": "object", "properties": { "first_name": { "type": "string", "description": "First name of the lead" }, "last_name": { "type": "string", "description": "Last name of the lead" }, "title": { "type": "string", "description": "Title of the lead" }, "linkedin_url": { "type": "string", "description": "LinkedIn profile URL of the lead" }, "reasons_for": { "type": "string", "description": "All supporting evidence concatenated into one text field" }, "reasons_against": { "type": "string", "description": "All concerns or gaps concatenated into one text field" }, "final_determination": { "type": "string", "description": "Final determination if the lead is qualified", "enum": [ "Yes", "No" ] } }, "required": [ "first_name", "last_name", "title", "linkedin_url", "reasons_for", "reasons_against", "final_determination" ], "additionalProperties": false } } }, "required": [ "company_name", "company_domain", "linkedin_url", "company_description", "leads" ], "additionalProperties": false }
this might work - if you take action on the list from within the cell rather than using the write to enrichment, plus send table data that's accessible through action on the list is so much better because it avoids the manual mapping
is the send table data also not working Joel B.? this essentially - https://www.loom.com/share/958e8a9d10d54ccf8f4837229d0b7fb8
Hey Jordan, thanks for reaching out! I just checked your table and it looks like the send table data works better than write to other table here to send your nested JSON arrays
Hi Jordan, Thank you for sharing this feedback, I’ve passed it along to the product team, and it’s something I personally agree with as well. Since this is still a relatively new feature, we’re seeing many legacy users continue to rely on the older "write to table" method. Over time, as more users adopt the new approach and we do more education around it, we’ll be in a stronger position to consider fully deprecating the old feature. Appreciate you surfacing this!
.png){kind=logo}
