Clarifying Deduplication Behavior: Oldest vs. Manual Deduping

Christian Haskins (Sculpted) · 2024-12-04 00:28:23.089591+00

Does this follow the same behavior as manually deduping? By oldest does it just mean the one lower down in the view?

Clarifying Deduplication Behavior: Oldest vs. Manual Deduping | Clay

5 comments

· Sorted by Oldest

Christian Haskins (Sculpted)
·
·
I ask because I want it to get rid of the oldest. I have the view sorted by create date so the newest ones are at the top
Channeled
APP
·
·
The information I've found doesn't specifically address how automatic deduplication handles records based on their creation date or sorting order. Auto-dedupe in Clay allows you to select a column to deduplicate, but it doesn't mention any criteria related to record age or sorting.To enable auto-dedupe: 1. Click the Auto-dedupe icon at the bottom right of your table 2. Select "Enable automatic deduplication" 3. Choose a column to dedupe 4. Click "Save Changes"For more specific information about how auto-dedupe handles records, could you tell me which particular column you're using for deduplication? This might help me provide a more accurate answer about the deduplication process. Source: Auto-update and Auto-dedupe Table
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!
Bo (Clay)
·
·
Hey Christian! Let me explain how the deduping behavior works since this is pretty important to get right. The system will actually keep the first values that come into the table - not the ones lower down in your view. So even though you've got it sorted by create date with newest at the top, that's just affecting how you're seeing the data, not how the deduping works. If you want to remove the oldest entries, here's a better way to do it: 1. Create a formula to number your rows 2. Set up a filter to catch rows that were created before others and have a number greater than 1 Let me know how it goes!
Channeled
APP
·
·
Hi Christian Haskins (Sculpted)! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Christian Haskins (Sculpted)
·
·
I ask because I want it to get rid of the oldest. I have the view sorted by create date so the newest ones are at the top
Channeled
APP
·
·
The information I've found doesn't specifically address how automatic deduplication handles records based on their creation date or sorting order. Auto-dedupe in Clay allows you to select a column to deduplicate, but it doesn't mention any criteria related to record age or sorting.To enable auto-dedupe: 1. Click the Auto-dedupe icon at the bottom right of your table 2. Select "Enable automatic deduplication" 3. Choose a column to dedupe 4. Click "Save Changes"For more specific information about how auto-dedupe handles records, could you tell me which particular column you're using for deduplication? This might help me provide a more accurate answer about the deduplication process. Source: Auto-update and Auto-dedupe Table
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!
Bo (Clay)
·
·
Hey Christian! Let me explain how the deduping behavior works since this is pretty important to get right. The system will actually keep the first values that come into the table - not the ones lower down in your view. So even though you've got it sorted by create date with newest at the top, that's just affecting how you're seeing the data, not how the deduping works. If you want to remove the oldest entries, here's a better way to do it: 1. Create a formula to number your rows 2. Set up a filter to catch rows that were created before others and have a number greater than 1 Let me know how it goes!
Channeled
APP
·
·
Hi Christian Haskins (Sculpted)! This thread was recently closed by our Support team. If you have a moment, please share your feedback: