This article covers common datasheet import issues in Finalsite CMS, including how to diagnose line ending problems and resolve failed or single-row uploads.
💡 Quick answers
- What causes a datasheet import to fail or show all data in one row? Mismatched line endings, the hidden characters that mark the end of each row. Files saved from Excel for Mac or exported from another system are common sources.
- What is the fastest fix? Open the file in Google Sheets and download it again in the format the import article requires, such as Tab Separated Values (.tsv) or CSV.
- Which Excel save option should be used? Text (Tab delimited) (.txt) or CSV UTF-8 (Comma delimited) (.csv), matching the import article. Avoid CSV (Macintosh).
- What else can cause similar symptoms? A leftover instructions column or row, or a file saved in the wrong file type.
- Where can help be found if the import still fails? Contact Finalsite Support with the file and the import being attempted.
In this article
- Identify line ending problems
- Fix line ending problems
- Prevent line ending problems
- Related articles
Identify line ending problems
Every row in a datasheet ends with a hidden character. Different systems use different characters, and an import can fail when the file does not use the one the upload expects.
Line endings at a glance
Windows files typically end each row with a carriage return and line feed (CRLF). Mac and Linux use a line feed (LF). Some older Mac exports use only a carriage return (CR).
Common signs of a line ending problem include:
- The upload fails without a clear reason.
- All of the data appears in a single row.
- Records merge together, or blank rows appear between records.
- The file looks correct when opened in Excel or Google Sheets.
⚠️ Important Note
Before changing line endings, confirm that the instructions column or row was deleted and that the file was saved in the file type the import article requires. Leftover instructions and the wrong file type can cause similar failures.
Fix line ending problems
Re-saving the file from Google Sheets or Excel writes clean line endings. Use the format that matches the import article for the data being uploaded.
Re-download the file from Google Sheets
- Step 1: Upload the datasheet to Google Drive and open it in Google Sheets.
- Step 2: Select File, then Download.
- Step 3: Choose the format the import article requires, such as Tab Separated Values (.tsv) or Comma Separated Values (.csv).
-
Step 4: If the import article calls for a .txt file, rename the downloaded .tsv file so the extension is
.txt. - Step 5: Try the import again.
Re-save the file from Excel
- Step 1: Open the datasheet in Excel.
- Step 2: Select File, then Save As.
- Step 3: Choose Text (Tab delimited) (.txt) or CSV UTF-8 (Comma delimited) (.csv), matching the import article.
- Step 4: Avoid CSV (Macintosh) and MS-DOS CSV, which can produce line endings the import does not expect.
- Step 5: Try the import again.
Prevent line ending problems
- Start from the datasheet template in the import article.
- Avoid editing the file in a plain text editor.
- Delete the instructions column or row before saving.
- Save in the file type the import article specifies each time, rather than reusing an older exported file.
- For data from another system, such as an SIS export, open and re-save the file in Google Sheets before importing.
Related articles
- Upload recipients to a Messages List in bulk with a datasheet
- Upload constituent data to Constituent Manager in bulk
- Upload student and parent data in bulk
- Import events in bulk to New Calendars module
- Add posts in bulk to the Posts module
- Finalsite CMS Error Codes Guide
Did not fix the problem? Reach out to Finalsite Support.
Comments
Please Sign in to leave a comment if you don't see the comment box below.