I have a spreadsheet that refuses to upload into Clay. I've rebuilt the spreadsheet, rebuilt the Clay table, and still, it refuses to upload. All other spreadsheets & tables are working just fine... minus this one spreadsheet.
Since you're having issues with a specific spreadsheet, here are the steps to troubleshoot the upload: 1. First, ensure you're following the correct import process: • Go to the Source panel via Actions > Import for existing tables • Choose CSV import option • Either browse files or drag and drop your spreadsheet 2. Try these alternative approaches: • If you're using Google Sheets, export it as a CSV file first, then import into Clay • Verify your column headers are properly formatted • Check if there are any special characters or formatting in your spreadsheet that might cause issues 3. When importing, make sure to: • Properly map your columns to Clay table fields • Choose the correct import option (Add to current table, Create new table, or Replace current table)If you're still experiencing issues after trying these steps, you may want to ask for human support to investigate the specific problem with your spreadsheet. Sources: How to import your CSV into Clay | Documentation | Clay University Table sources overview | Documentation | Clay University Import CSV [Clay 101] - Clay University
This doesn't work.
Hey Aly, thanks for reaching out and sorry to hear this. Do you mind uploading the CSV into a Google Sheet, then sharing it with me so I can take a closer look and help resolve this?
Here's the spreadsheet: https://docs.google.com/spreadsheets/d/1qU5j1SPBJBIxBbelLyPiEz5eJuTbWdr3NrtR6KSi0mU/edit?usp=sharing Here's the Clay Table: https://app.clay.com/workspaces/349495/tables/t_qBerutH6wf6W/views/gv_zxqGJYnHDaYN
Interesting! Thanks for sending this over. Just tested this out on my end by exporting the Google Sheet as a CSV and re-importing this into the table URL mentioned in your message. It seems to be working! Sometimes hidden characters or formatting can mess up the importing process and using Google Sheets as an intermediary can help workaround this if your CSV is super large. Apologies for the inconvenience. Hope this helps! The rows seem to have fully loaded, let me know how else I can help here. :)
The rows loaded but none of the formulas populated. Never seen that happen before and no idea how to fix it.
Hey Aly, which formulas are you referring to? Given this is a large data set, upon importing the CSV I didn't run any other enrichments or columns which are likely upstream of these formulas. Would recommend setting a row limit to 10 to avoid incidental credit spend and begin running the intended enrichment columns. :) https://downloads.intercomcdn.com/i/o/w28k1kwz/1340651353/d02d1ba396c986c70be3f58bdfc5/CleanShot+2025-01-17+at+17_02_05%402x.png?expires=1737153000&signature=4c3273fe6f9a7ca3fed89c26e9933f7763f83a70191d041ddde885a9660ed401&req=dSMjFs97nIJaWvMW1HO4zQOIoW%2FTM1tCHANMBp3HsyNKjQAlBus39SIkxVtM%0AOrhd%0A
Look at the columns labeled Opt1-Email, Opt2-Email, Opt3-Email, etc. Essentially this table is using different email variations/options to find the correct email address. Those formula columns should have automatically filled, even if other columns haven't run.
Got it. After looking at these formulas specifically it appears as though they are referencing a column that does not exist within this table. Or this value hasn't ran yet. Regardless, after clicking "Generate formula" again in this initial column it appears to have updated the formula to reference the correct domain which populates the formula. This appears to be the case for the other columns as well. If you click "regenerate formula" it should resolve the problem. However I'd love to make sure we get this fixed, do you mind clarifying where you got this template from? https://downloads.intercomcdn.com/i/o/w28k1kwz/1340690423/55dff487c0d59c3b81bb24119464/CleanShot+2025-01-17+at+17_55_23%402x.png?expires=1737157500&signature=fa6681b0d2976344264f7f39c2d57c309804489467efab65b0175ce551bb4ca0&req=dSMjFs93nYVdWvMW1HO4zS5ByqBXmgXIUT6pE2WPYM3YkfyfaTxoXxX%2BNWoZ%0AhuOt%0A https://downloads.intercomcdn.com/i/o/w28k1kwz/1340690439/0a44e2ce39b19d54dae0a8dc7511/CleanShot+2025-01-17+at+17_55_46%402x.png?expires=1737157500&signature=e19243f27e9f2260380203bb30e75ced30a41d86c706fb7cbb14b0ac4cfe9ef1&req=dSMjFs93nYVcUPMW1HO4zY2U1Y3vtU8nGSAw75xnZ6dmdSpSh2yVpJFLFW%2Ft%0AJ72g%0A
So I hit Run on the domain normalization column and that fixed half the problem, but it stops after 10 rows.
Hey Aly! When you're in a view with a restricted row count (which happens when you set a row limit by clicking on the row count at the top > row limit), here's the fix: 1. Keep your current view as is 2. Duplicate the view 3. Click on the domain normalization column header 4. Select "run column" 5. Choose how many rows you want to run I've got a quick video that walks through this exact process: https://cln.sh/rG2S2zc3 This will let you run the normalization on all your rows while keeping your original view intact. Let me know if you run into any other snags!
