common-import-errors-and-how-to-resolve-them

• The row did not cause an update because there is no existing record that matches the duplicate check

• This is actually not an error. The import tries to update Maximizer entries. But there is no entry matching the record in the CSV file. Therefore upgrade doesn’t happen

• Company (or another record type) -> The row was not imported because the record exists and there were no fields that required an update

• This happens if the user chooses “Only update existing Maximizer records with new data from the import file” and “Update only empty Maximizer fields with data from the import file” in the Rules steps of Import and matching records had empty fields.

• The cell value 'Amelia Island Amelia IslandAmelia IslandAmelia IslandAmelia IslandAmelia IslandAmelia IslandAmelia IslandAmelia IslandAmelia IslandAmelia Island' is too long to fit in the field; which fits 79 characters

OR

• The row could not be processed because updating the database failed.  The error returned from Maximizer.Web.Data is Unable to set the value of a data field. The string supplied must be in the allowable length range.

• This error happens when the string in the import file is too big to fit into the field in Maximizer.
• Increase the size of Maximizer UDF if possible or adjust the import string.

• Company  (or another record type)-> The row was not inserted because there is at least one existing record that matches the duplicate check

• This happens if the user chooses “Add only new records currently not in Maximizer” in the Rules step of Import and there is already an entry matching the record in the import file.

• In column Account Manager mapped to AccountManager: The cell value 'Alain Agostini' is not a valid User ID for the field

• CSV file for import only supports user ID; not the user name. If the mapped field is related to users; e.g. account manager or opportunity leader; using the display name will cause an error
• Change the user name to a user ID in CSV file.
• UPDATE: Newer versions of Maximizer (v 2023 .11 or higher) now support user names and user IDs.

• contact -> The row was skipped because all of the fields in the duplicate check were blank

• The error occurs because the matching field(s) do not have a value for the row.
• Make sure all fields used for matching have a value (if multiple fields are used; at least one has a value).

• Inserting to the database failed.  The error returned from Maximizer.Web.Data is AbEntry: failed to create AbEntry. Maximizer.Data message: Unable to perform an operation without the setting of a mandatory field.

• The error occurs because a system mandatory field is blank. For example; import a company but the company name is blank. Or import a contact but the last name is blank.
• Find the field and enter a value

• lead -> Updating the database failed.  The error returned from Maximizer.Web.Data is Nullable object must have a value.

• This message will be displayed if the lead status in the CSV file includes Converted or Abandoned.
• The status in the CSV file should be the active status; including New; Working; and Nurturing.

• Individual -> In column Shared\Program Affiliation(s)**(*) mapped to Udf/$TYPEID(45): The item 'Semester in Dialogue ' in cell value 'Semester in Dialogue ' does not match a table item of the mapped field

• The table item was called “Semester in Dialogue“; import value was “Semester in Dialogue ”. The issue was a space after the e at the end of the spreadsheet value. Remove space and retry – success.
• UPDATE: In newer versions of Maximizer (v 2023.11 or higher); leading and trailing spaces are automatically removed during the import process. 

• company -> The row did not cause an update because there is more than one existing record that matches the duplicate check

OR

• contact -> The row did not cause an update because there is more than one existing record that matches the duplicate check

• Make sure that all the duplicate checking fields are populated. If there are blank fields; the import would fail.  
• Check if there are duplicate entries in the Address Book. If there are; you may want to add another duplicate checker to help Maximizer identify which record to modify.

• Individual -> In column SIN mapped to Udf/$TYPEID(1182): The cell value '000 000 000' is not a number (in the culture that is selected in Preferences) (2020 R1)

• The field is numeric field; spaces between the 0’s are not numeric characters; remove spaces and import again. FORMAT: 000 000 000 -> 000000000

• The row could not be processed because the query to check for existing records failed.  Please try a different set of fields for the duplicate check.  The error returned from Maximizer.Web.Data is Maximizer.Data failed to read AbEntry. Maximizer.Data message: Unable to pre-process the given search string. It may be missing or have extraneous parentheses or double quotes. (2020 R1)

• This error happens if fields used for matching have some special characters.
• Try removing characters possibly causing the issue from the import string