When importing a CSV file, either as a one-time upload or through a business adapter, you might encounter an error stating that a required column is missing.
This issue is often caused by hidden Byte Order Mark (BOM) characters at the beginning of the file. A BOM is an invisible marker that indicates a file’s encoding, and it can interfere with how column headers are recognized during import. Microsoft Excel adds a BOM when you save a file using the CSV UTF-8 (Comma-delimited) format. These extra bytes can alter the header row, making it unrecognizable to the import process.
The following screenshot is an example of what a column looks like with BOM characters that have been unexpectedly added in front of the Purchase Order Number Column in the Purchase Order import template.
Common causes
- CSV saved with UTF-8 BOM: Saving a CSV file in Excel using the UTF-8 format inserts a BOM, which becomes part of the first column’s name.
- Manual file edits: Editing a CSV in other programs may retain BOM characters even after saving.
To avoid import errors caused by BOM characters:
- Save as a standard CSV
Open the file in Excel and choose CSV (Comma delimited) instead of CSV UTF-8 (Comma delimited). This prevents Excel from adding a BOM. - Use a clean template
If the BOM persists, download a fresh copy of the import template. Copy your data (excluding the header row) into the new file and save it as a standard CSV.
For this example, you’d download a copy of the Purchase Order import template from Data Collection > IT Assets Inventory Tasks > Data Imports.
Once downloaded, copy your data (excluding the header row) into the new template and save it as CSV (Comma delimited) to avoid BOM-related errors.
Related Articles
Fix the “Failed to import Fargate services” error caused by too many security groups 3Number of Views Fix stateful node import or launch failures caused by disk redundancy and zone settings 6Number of Views Resolve GKE launchSpec update errors caused by missing node pools 2Number of Views Resolve Okta domain verification errors caused by IDP regex limits 7Number of Views Build Errors Caused By Windows Installer CAB File Format Limitations 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago