is there a way to dedupe records to based on the most recently updated record?
Our auto-dedupe feature retains the oldest row and deletes duplicates, not the most recently updated one. You can enable auto-dedupe by clicking the auto-dedupe icon at the bottom right of your table, toggling on "Enable automatic deduplication," and selecting a column to identify duplicates. For keeping the most recent record instead, you'd need to manually dedupe by right-clicking a column header and selecting "Dedupe > Delete Duplicate Row" to choose which specific rows to remove.
ok, that should be an option! whether you want to dedupe based on oldest or newest record.
Hey, Just to understand better—what’s your goal with deduping based on the most recently updated record? If you can share a bit more about what you’re trying to do, I can pass it along with clearer context to the team. Let me know!
Cool, basically if I need to update rows with more variables, then it would be better to have the most recent version. Like on this table, https://app.clay.com/workspaces/369580/workbooks/wb_0szg5i7qFXbMFeNwW5Y/tables/t_0szfs0tSWh6dCGBTTuA/views/gv_0syag58hy9xbXb9qspA for whatever reason the company name didn't seem to write to the other data table. So I tweaked it and reran it but I have the destination table: https://app.clay.com/workspaces/369580/workbooks/wb_0syt45sfP3TAtemBPEx/tables/t_0syt460x5GGvVMS3reb/views/gv_0syt460ndu56V3ZV8tk on autodedupe because I pull info from that table using email as an anchor reference. So if I'm able to fix the record, I'd like it to update and populate where that record exists in multiple tables.
Curious—what’s the end goal here? Are you trying to update the CRM, or is it more about consistently pushing the same values across tables? Would be helpful to get a quick overview from the top.
More about the iteration process. Using it for contact enrichment, email writing and auto replying workflow. So sometimes I'll tweak the template or want to add an extra variable in the email that needs to get pushed into the contact database to keep it updated. But the central database table can't be updated because it dedupes only on the first record, not the most recent one.
Hey - Thanks for this! We're always looking to make the product better and this feedback is super helpful for us. We're going to pass this over to our product team so they can better evaluate things and see if/where this might fit into the roadmap as a future improvement.
no prob!
While I'm here, one thing I think would be huge would be automatic rerun of errored cells. We're looking to automate a lot of these processes but need to trust they'll rerun if they hit a rate limit or something
Got it — what types of errors are you usually seeing, and which ones would you want to automatically rerun? Would be helpful to know if it’s mostly rate limits or something else.
I'd like to do it through clay but need to make sure it's not going to hit too many bugs
Hey — really appreciate you sharing this. We’ve passed the feedback to our product team so they can evaluate where auto-reruns for errors like rate limits might fit in the roadmap. Clay’s infrastructure can handle high volume, but scaling smoothly often depends on how providers handle rate limits. I’ll make sure the team’s aware that this is something you’re looking for. Let me know if you have more questions.
Cool sounds good!
Hey - Thanks for this! We're always looking to make the product better and this feedback is super helpful for us. We're going to pass this over to our product team so they can better evaluate things and see if/where this might fit into the roadmap as a future improvement.