Enhancing Spreadsheet Safety: Request for Save a Sheet Feature

·

or like, at least the ability to "save a sheet" in it's current form. I spend hundreds or thousand of dollars on enriching a big ahh sheet and I am literally shaking in my boots every time I make a change bc I mess one thing up and then whole sheet is ruined.

2

3 comments

· Sorted by Oldest

Clay
APP
·
·
Currently, Clay doesn't have version history or the ability to restore previous table versions. However, you can create a backup by duplicating your table and moving it to a separate workbook - this preserves the structure without data. Consider adding '[Template Do Not Delete]' to the backup table title for clarity. This workaround lets you maintain a clean copy before making risky changes to your enriched data.
Umer I.
·
·
+1 Henry S., great point - I’m in a similar situation. A lot of my data is already enriched, and when I try to stop old data from running, I use a date-based conditional run. That helps prevent reruns of old data, but when the condition isn’t met, the old data gets wiped out. For example, I have a scoring criteria in place that I want to update. But if I change it, it affects the entire table. And if I apply a date condition, it removes old data under the “condition not met” logic. So yeah, we definitely need a better solution for this.
🙏1
Clay
APP
·
·
You're experiencing the "condition not met" behavior where conditional runs clear existing data when conditions aren't satisfied. Alternative approach: Use filtered views instead of conditional runs - filtered views only enrich rows you're viewing, preserving existing data while preventing new enrichments on unwanted rows. For scoring updates: Consider duplicating your table as a backup before making changes, or use Lookup columns to reference existing enriched data from other tables to avoid re-enriching.
Sources: Guide: Ways to save Clay credits | Documentation | Clay University Guide: Ways to save Clay credits | Documentation | Clay University

Loading comments

Clay
APP
·
·
Currently, Clay doesn't have version history or the ability to restore previous table versions. However, you can create a backup by duplicating your table and moving it to a separate workbook - this preserves the structure without data. Consider adding '[Template Do Not Delete]' to the backup table title for clarity. This workaround lets you maintain a clean copy before making risky changes to your enriched data.
Umer I.
·
·
+1 Henry S., great point - I’m in a similar situation. A lot of my data is already enriched, and when I try to stop old data from running, I use a date-based conditional run. That helps prevent reruns of old data, but when the condition isn’t met, the old data gets wiped out. For example, I have a scoring criteria in place that I want to update. But if I change it, it affects the entire table. And if I apply a date condition, it removes old data under the “condition not met” logic. So yeah, we definitely need a better solution for this.
🙏1
Clay
APP
·
·
You're experiencing the "condition not met" behavior where conditional runs clear existing data when conditions aren't satisfied. Alternative approach: Use filtered views instead of conditional runs - filtered views only enrich rows you're viewing, preserving existing data while preventing new enrichments on unwanted rows. For scoring updates: Consider duplicating your table as a backup before making changes, or use Lookup columns to reference existing enriched data from other tables to avoid re-enriching.
Sources: Guide: Ways to save Clay credits | Documentation | Clay University Guide: Ways to save Clay credits | Documentation | Clay University