This table explains import errors, what they mean, and how to fix them.
Error | Meaning | Fix |
<fieldname> is required | A required field is missing from the import file. | Add the field into every row of the import file. |
Account number is required when Household is mapped | Household fields are mapped but household account numbers are not in the import file. | Add household account numbers into every row of the import file that contains household fields. |
<value> is not a valid value for the field <fieldname> | A field contains an invalid value. For instance, a date field has a dollar amount. Or a field uses commas to separate multiple values. | Correct the values in the field. |
($ amount) is not a valid value for the field 'Amount' | The amount is a negative number. | Enter a positive number for the amount. |
No matching Bloomerang account number | A matching individual or organization account number doesn't exist. | Correct account numbers or don't include them. Tip: Household data can't be imported. |
Importing values for numeric pick multiple field <fieldname> is not supported | The import file includes values for a pick multiple field. | Remove the pick multiple field. Manually add these to constituents. |
Column headers cannot be more than 255 characters. | The import file has at least one really long column header. | Shorten the column header to 255 characters or fewer. |
Oh no! Every line in your file has an error. Please go back to the mapping and verify you have mapped it correctly. | Nothing can be imported. | Correct the mapping for the import file. |
You cannot import to automatically-managed groups. Import to a new or existing group that you manage. | The import file includes one or more group names identical to one or more groups that Bloomerang CRM automatically manages. | Remove or rename any groups from your import file that are identical to groups that Bloomerang CRM automatically manages. For a list of groups, see View Groups. |