Home
Events
Groups
Members

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps
Gtm Career Advice
Member Spotlight

Community Guidelines

Powered by Tightknit

Retaining Data Access in Lookup Tables Despite Enrichment Re-runs or Deletions

·

·

if I have a table with lookups of enrichments from other tables and those enrichments from the original table re-run/get deleted, will the data still remain accessible to the lookup table (until the look up column re-runs)? Not sure if this makes sense 😆 let me know if you want me to explain further

Retaining Data Access in Lookup Tables Despite Enrichment Re-runs or Deletions | Clay

12 comments

· Sorted by Oldest

Clay Team
APP
·
·
Hi Nick, so you want to know if the Lookup values that we pulled from an original table will remain static when the original source gets updated, right?
:thumbsup_all:1
Nick Singh
·
·
correct
Fred (Automindz Solutions)
·
·
Interested in that aswell! Great question Nick Singh!
:thumbsup_all:1
Clay Team
APP
·
·
I confirm you that the values will remain static, if you delete the source the result of the lookup won't be affected, unless you run the lookup again
:thumbsup_all:2
Nick Singh
·
·
Perfect, couple of other questions:
1.
as a failsafe If I put a filter to exclude matches on the look up column, even if I "force run" on the remaining rows in the column showing, the "matched results" would not be affected by the force run, is that right?
2.
do I have to pull the data out of the look up columns onto the table for that data to be accessible by other tables, or can I access the data directly from the look up column (again if this doesn't make sense, let me know and I'll clarify)
Clay Team
APP
·
·
2. In order to be able to pull a column to another table through a lookup, this column should be in the source table: Example: I do a linkedin company enrichment, I won't be able to pull the company description into the new table through a lookup if there is no previous description column in the source table, no matter if that field is "included" in the LinkedIn enrichment
Clay Team
APP
·
·
checking the 1.
Clay Team
APP
·
·
A filter will prevent all the rows not selected to be enriched when you run a column
:thumbsup_all:1
Clay Team
APP
·
·
But I would use formulas if possible
Clay Team
APP
·
·
As they are more robust
Nick Singh
·
·
can you explain that further and give an example?
Clay Team
APP
·
·
Sure, check this loom: https://www.loom.com/share/77b9f67983b443e1b32f91474a3a833f