Debugging undefined Issues in Parent-Child Table Enrichment

I used the "Create item in another table" enrichment on a list within a JSON field. When I go to that item in the other table, one of the parent item fields is being populated with "undefined" when the parent item does in fact have that field defined. This also occurs when I try the workaround of "look up row in other table" to search for the parent (in this case a company) from the child (contact) tables. Suggestions?

3 comments

Clay
APP
·
·
When parent fields show as "undefined" in target tables, this typically happens because the data needs to be refreshed or re-run after changes. You need to re-run the company row in the people table and force run through the whole column to see the new values. You can also identify the parent column of your child column by clicking on the child column to open the dropdown menu, then selecting "Go to parent column" to better understand the data context. Are you seeing "undefined" values for all parent fields or only specific ones in your target table?
Sources: Table columns | Documentation | Clay University Table columns | Documentation | Clay University
Tony C.
·
·
but what if the second table already had enrichment columns run that used credits? it would essentially force a rerun of all downstream.
Clay
APP
·
·
You can avoid forcing a rerun of all enrichments by using conditional runs and filtered views: Method 1: Filter for New Rows Only Filter your table to show only rows with "undefined" values, then run the enrichment on that filtered view. This ensures only the problematic rows are processed without affecting existing data. Method 2: Use Conditional Formulas Set up conditional runs in your enrichment settings using the "Only run if" box. This prevents enrichments from running on rows that already have valid data, conserving credits by only processing rows that meet specific conditions. Method 3: Leverage Existing Data Use Lookup columns to pull existing data from other tables or your CRM instead of re-enriching, which saves credits by avoiding duplicate enrichments. These approaches let you fix the "undefined" issue while preserving your existing enriched data and avoiding unnecessary credit usage.
Sources: Guide: Ways to save Clay credits | Documentation | Clay University Guide: Ways to save Clay credits | Documentation | Clay University

Debugging undefined Issues in Parent-Child Table Enrichment | Clay