TABLE OF CONTENTS
- Import Errors
- 1. Remove Periods from the File Name
- 2. Eliminate Extra Tabs
- 3. Delete Helper Rows
- 4. Remove Formatting
- 5. Check for Hidden Characters
- 6. Save as CSV
- 7. Verify Mandatory Fields
Import Errors
Encountering an error while importing via Excel? Here’s how to resolve common issues:
1. Remove Periods from the File Name
Periods in the Excel file name can cause errors. Replace them with dashes or another symbol.
Example: Change Member Import 8.5.2025 to Member Import 8-5-32025.
2. Eliminate Extra Tabs
Ensure your Excel file contains only one tab. Additional tabs can disrupt the import process.
3. Delete Helper Rows
When you created your import template, you may have included additional information in your Excel sheet by checking these two boxes (a):
These appear on your Excel sheet as Rows 2 and 3 (b) and provide additional field guidance, however, your sheet will be rejected if they are not deleted prior to import.
4. Remove Formatting
Clear any special formatting in your Excel sheet to avoid compatibility issues by selecting your sheet and clicking "Clear Formats".
5. Check for Hidden Characters
Data exported from platforms like SurveyMonkey or Google Forms may include hidden characters.
Quick Tip: Highlight your entire document and apply a filter. If you see columns with filters but no visible data, hidden characters are present. Delete these columns to resolve the issue.
6. Save as CSV
If import issues persist after removing formatting, save your file as a CSV and then back to an Excel. This can clear hidden formatting.
7. Verify Required Fields
If your Impact Suite requires certain fields during reporter enrollment, bulk imports will fail unless this information is included.
Missing required fields will trigger an error message like this:
Fields marked in red with an asterisk (*) are mandatory. To adjust these settings, follow the guide on making fields required for the reporter enrollment process.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article