Clay Icon

Troubleshooting Write to Table Issues with Multiple Sub-Groups

ยท
ยท

Hey team, I'm trying to "write to table," but for some reason, if there are multiple groups within a sub-group, I can only write the first one, and the rest don't appear as options. For example, many records have multiple employers, yet it's only allowing me to map or write to the table for the first employer.

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    The Write to Table feature in Clay supports mapping both individual values and lists, including multiple items within groups. Here's how to properly map multiple groups: 1. When setting up Write to Table, make sure to select the correct column containing your list of items (like multiple employers). 2. In the mapping step, you'll need to specifically select the list properties you want to map to your destination table columns.The Write to Table action supports writing lists, single values, or objects, so it should be able to handle multiple groups.If you're still experiencing issues with mapping multiple groups, you may need to check your column setup and ensure the data is properly formatted in your source table. If the problem persists, you should request help from a human agent to investigate your specific setup. Sources: Write to table integration overview | Documentation | Clay University Write to Other Table with Clay Labs

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!

  • Avatar of Andi D.
    Andi D.
    ยท
    ยท

    Hey Bo here's the link, it's the same one from yesterday where I tried to do group mapping: https://app.clay.com/workspaces/449716/workbooks/wb_RrFKxUfBuRDb/tables/t_cyhACKZ2yZBB/views/gv_m8i8Ubcco5Bv

  • Avatar of Bo (.
    Bo (.
    ยท
    ยท

    Here's how - 1. Create a JSON object to store all experience data with the formulas (see example in your table, but since we're adding all the fields, you're hitting a cell size limit when trying to write multiple employers. We'd need to remove the fields we don't want and only return name experience.domain for example) 2. Use JSON.parse to extract employer names into a new table 3. Set up a lookup from your people table to pull those values. This way you'll avoid the size limits while keeping all employer data accessible. Want me to clarify any part of this workflow?

  • Avatar of Andi D.
    Andi D.
    ยท
    ยท

    tysm Bo! I think I understood the idea, let me give it a try first!

  • Avatar of Andi D.
    Andi D.
    ยท
    ยท

    Bo im trying this out right now, each cell would have multiple contacts and each contact with multiple work history records. With formula it's able to extract all the info but it's still merged within a single cell, for example, all 5 separated contacts. What would you recommend me to do to slice them into 5 rows, Bo? Thank you so much!

  • Avatar of Bo (.
    Bo (.
    ยท
    ยท

    I recorded this walkthrough video showing exactly how to set this up: https://cln.sh/R0K11d2j Let me know if you have any follow-up questions!

  • Avatar of Andi D.
    Andi D.
    ยท
    ยท

    Ty so much Bo! The video is really helpful. Quick question, is there a way to extract full employment history here? The result you got only have one work experience, which is the issue. I ran into when used Write-to-table directly

  • Avatar of Bo (.
    Bo (.
    ยท
    ยท

    Hey! Absolutely, tweaking the formula is the way to go to get all the fields you'd like per person. ๐Ÿ˜Š You'll typically reference the field names you want to keep and use them in the formulas in the same pattern. If you get stuck, just let me know!

  • Avatar of Andi D.
    Andi D.
    ยท
    ยท

    Hey Bo, thanks so much for working on this with me! but im dead lol man it's hard. The data I pulled are from CrustData API and im looking for "sales" roles given a company domain. Some companies would come back with 20+ contacts and each would have multiple employment history (that's what I'm looking for) It seems like it's oversize for Clay cells and I won't be able to parse it out via Json.

  • Avatar of Andi D.
    Andi D.
    ยท
    ยท

    just found a get around! So for some reason if I start within the said HTTP column, Clay would limit the match to just 1 employers but if I go into "add other data from this table" while in Write to Other Table, and manually go back into the HTTP column, it for some reason would show me the full list of employers

  • Avatar of LuisArturo
    LuisArturo
    ยท
    ยท

    Hey there, jumping in for Bo, good to hear you found a workaround, let us know if you have any other questions.

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    Hi Andi D.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: