.png){kind=logo}
Issues with CSV Import: Blank Cells when Copying Rows
Importing csv creates blank cells. I tried copying multiple rows from the source, but doesn’t work. Copy paste single cells work
Blank cells during CSV import or when copying multiple rows often result from formatting issues in the CSV file, such as mixed or incorrect column separators, hidden formatting, or unsupported columns. Clay supports CSVs with either commas or semicolons as separators, but mixing both can cause problems. To resolve this: ** Ensure your CSV uses a consistent separator (preferably commas) and is UTF-8 encoded. ** Avoid including unsupported columns like "created at" or "updated at." ** Try uploading your data to a public Google Sheet, then download it as a CSV and re-import it into Clay—this can help clean up hidden formatting issues. ** Keep your CSV file name short. If these steps don’t resolve the issue, you can request human assistance by clicking on "Talk to a person" in this chat for further troubleshooting.
Let me talk to a human
If importing a CSV or copying multiple rows results in blank cells, even after trying previous suggestions, here are some additional steps to troubleshoot: ** Double-check that your CSV uses a consistent separator (commas or semicolons, but not both) and is UTF-8 encoded. Mixing separators can cause data to be misread and create blank cells. ** Remove any unsupported columns, such as "created at" or "updated at," and ensure your file does not exceed 72 columns or 50,000 rows. ** Try uploading your data to a public Google Sheet, then download it as a CSV and re-import. This can help clean up hidden formatting issues that may cause blank cells. ** Keep your CSV file name short, as long names can sometimes cause issues. If these steps do not resolve the issue, you can request human assistance by clicking "Talk to a person" in this chat for further troubleshooting.
Uuuhhh. I updated the space and now it works
Owen C.··Hey Daniel, thanks for reaching out! Just want to make sure you're all taken care of here, anything still causing issues?
All good. Seems like a lag that was fixed with reload of the page. Thanks!
- Owen C.··
Okay incredible! Of course. :)