So the original sheet ( companies sheet) had the first several companies from a csv file. Last night I added like 3,000 new companies from the clay search companies actions. Once I did that all the csv uploadedcompanies disappeared. The first ~650 rows are blank. That’s where those companies from the csv were.
This issue can occur when adding a large number of new companies to an existing table. It's likely that the new companies were added, but the original CSV-imported companies were pushed down the list. To resolve this: 1. Check if the first ~650 rows are blank, as you mentioned. This suggests the original companies are still there but not visible. 2. Try scrolling down in your table to see if the original companies appear further down. If you can't find your original companies, it might be related to how Clay tracks imported records. In some cases, when new records are added and the previous ones are deleted, Clay may reject the import if the limit is set lower than the number already in the table. If you need further assistance or can't locate your original data, please request human support by clicking on "Talk to a person" for a more detailed investigation of your specific case.
what should I do in the future to prevent this
To prevent losing data when adding a large number of new companies to an existing table, follow these steps: 1. Before importing, turn off auto-update for your table. 2. Import the new companies using the appropriate method (e.g., HG Insights or other sources). 3. After importing, use the de-duplication feature on the company name column to remove any duplicates. 4. Turn auto-update back on once the process is complete. This approach will help maintain your existing data while adding new companies. If you encounter any issues, consider duplicating your table before making changes to preserve the original data.
Talk to a human
prev thread from support - This behavior is due to how we manage column source dependencies. Each column is tied to a specific data source, and when you imported the CSV, the dependency was set to that particular column from the CSV. Later, when you parsed your company search data into the same columns where the CSV data was living, that original dependency was overwritten. Think of each column like a power outlet that can only be plugged into one power source at a time — if you switch the plug, the original power source gets disconnected. Similarly, switching the data source reassigns the dependency and overwrites what was there before. This is a current limitation of the product which I will flag to our product team for addressing in the product. As a workaround, I recommend merging the outputs into a single set of columns (f.e. company name csv, merged with company name from the company search, into a single column using our merge functionality) when working with multiple sources — especially when one of them is a CSV import.
I just imported csv > mapped csv columns to clay columns And then Clay automatically creates a new column “Imported Companies” when the action is run as a data source and maps company info to clay columns Wouldn’t this setup should circumvent that issue?
Hey Addison, Let’s try deleting the first 650 rows and re-importing them and can you do this on a Loom just so we can see maybe what's going wrong?—this should help ensure everything maps correctly this time. I’m happy to add the credits back. From what I can see right now, those rows are just empty, so redoing the import is the best way forward. Really sorry about the trouble here.
.png){kind=logo}
