NOTE: This article references "Real Magnet" -- a previous name of the Higher Logic Communications Enterprise product.
When you perform a mass upload of email addresses, some records might be rejected. Communications Enterprise collects these rejected records in a text-based Reject File. The "reject" file has a multi-character name that includes your account name, the date of the export, and it ends in .rej.txt.
To retrieve a reject file:
- Access the Admin interface.
- Navigate to Settings > Reports.
- Select Upload & Export Job Status.
- In the Uploads section, locate the upload job.
NOTE: If you don't see the upload, click Display Previous Uploads to expand the section.
- Click the download icon (down arrow in a red circle) to save the report.
- Navigate to where you want to store the report file, give it a memorable name, and click Save.
TIP: Navigate to the saved file and review it.
Your file will contain a line item of each user record that was rejected and why.
NOTE: Communications Enterprise requires an email address for every upload.
"Non-ASCII email address"
"Invalid email address (column N)"
The email address is evaluated to make sure the text is ASCII (characters 0 to 127). Records with a non-ASCII email address are rejected. This means that Communications Enterprise may have found invisible data characters in the file. This can happen when exporting your data source from a different location, or there may not be an email address in the email field.
Duplicate Email Addresses
"Duplicate contact by email address"
"Duplicate contact by email address or by first name, last name, and fax number"
"Duplicate contact by custom member ID" (custom Id case insensitive de-duplicate)
"Duplicate contact with custom member ID" (custom Id case sensitive de-duplicate)
In de-duplicate processing, duplicates are determined based on the unique ID for your account. Communications Enterprise will not upload a duplicate unique ID to the account. You’ll want to ensure that these records are removed from your file.
Records that are matched to unsubscribed or suppressed recipient are not uploaded to Communications Enterprise.
"Unsupported Email Address"
Records that are considered Role Addresses are not allowed into the Communications Enterprise system.
You can find a list of these email addresses in Why Can’t I Upload Certain Email Addresses?.
Missing Unique ID
"Email address missing"
Email address and fax number missing"
“Custom member ID missing"
"Email address and fax number missing or custom member ID missing"
Communications Enterprise validates every upload to ensure that the Unique ID for your account is contained in the record. If your Unique ID is Custom ID, this field is required for every record on upload. Communications Enterprise requires an email address for every upload, if Fax is enabled for this account, then this field is also required.
"Invalid date field (column N)"
Custom fields that are defined by the customer as containing dates are validated to make sure they have a valid date format. Quite a few common formats are supported and only unusual dates are rejected (i.e., Monday, January 1 8:30 PM 2006 would be rejected).
TIP: See Custom Date Fields for more information on using these fields.
Too Few Columns
"Too few fields in line (found N, expected M)"
This will occur if you upload a list, and opted to map 5 fields in Communications Enterprise. A record with fewer columns than the columns defined in the format file is rejected. This can occur if there are delimiters in your record, for example you have commas inserted into a Company name.
In the message, N is the number of fields found in the record, and M is the number of fields we expected in the record.
"Line has no data"
A record with every field empty (i.e., no characters) is considered "empty" and is rejected. However, records at the end of the file that are empty are ignored because Microsoft Excel export files traditionally can have hundreds of blank rows at the end of a file.
Character Limit Exceeded
"Field is too long (field N is M characters, but it cannot exceed Q)"
A record with a field that is too long to be stored in the database field where it is mapped is rejected.