...
- True: If set to True, new Contacts attempts to INSERT with an Inactive Status.
- False: If set to False, the new Contact attempts to INSERT with an Active Status.
Errors
There are a large number of possible errors for Imports. There are two types: errors that prevent the record from importing, and those that don't but cannot update related Import record information.
The following errors occur if the Contact INSERT or UPDATE fails:
- Error : No Contact Number or Name or Email specified
- Error : Found multiple duplicate customer numbers and emails in existing records for Customer Number <customerNumber>
- Error : Found multiple duplicate names in existing records for Name <firstName> <lastName>
- Error : FLAGS.NEW_CONTACT_DEFAULT_CONTACT_TYPE value '<defaultContactType>' is invalid
- Error : Billing group is required for new Customer contacts for Contact '<contactId>'
- Error : Failed to save Contact record <database error Message>
These do NOT cause the Contact INSERT or UPDATE to fail. The Contact will INSERT or UPDATE. However, the subsequent Child record may have a warning generate, and the child record is not added to the Contact. They are non-essential for the Contact, or they happen after the Contact save.When an Import Line fails, it is usually because the Line falls into one of the following categories:
The value provided from another table was not found within the Database
Toggle cloak Cloak - Warning : Could not find the Permission GLA for <GLA>
- Warning : Could not find the Dept Hierarchy '<Dept Hierarchy>' for Contact '<contactId>'
- Warning : Could not find Default SLA '<Default SLA Catalog>' for Contact '<contactId>'
- Warning : Could not find Default Incident SLA '<Default Incident SLA Catalog>' for Contact '<contactId>'
- Warning : Could not find Default GLA '<Default GLA>' for Contact '<contactId>'
- Warning : Could not find Billing Group '<Billing Group>' for Contact '<contactId>'
- Warning :
...
- Could not find Approval GLA '<Approval GLA>' for Contact '<contactId>'
The value provided from another table has multiple possible values
Toggle cloak Cloak - Error : Found multiple duplicate customer numbers and emails in existing records for Customer Number <customerNumber>
- Error : Found multiple duplicate names in existing records for Name <firstName> <lastName>
A blank value was provided, for a field with a required value
Toggle cloak Cloak - Error : Billing group is required for new Customer contacts for Contact '<contactId>'
...
- Error : No Contact Number or Name or Email specified
The value provided is not acceptable for the record type being created
Toggle cloak Cloak - Warning : Minimum Amount is greater than Maximum Amount for Approval GLA '<Approval GLA>' for Contact '<contactId>'
- Warning : Contact '<contactId>' is not type User, so cannot have Approval GLAs"; "Error adding email, email belongs to someone else
...
- Error : FLAGS.NEW_CONTACT_DEFAULT_CONTACT_TYPE value '<defaultContactType>' is invalid
The System was unable to save the record
Toggle cloak Cloak - Error adding email
- Error adding phone number
- Error : Failed to save Address record <database error Message>
- Error : Failed to Add Contact Address record; <database error Message>
- Error : Failed to Save null GLARestrict record; <database error Message>
- Error : Failed to Save GLA Restrict record; <database error Message>
- Error : Failed to Save GLA Approval record; <database error Message>
- Error : Failed to Save Contact Type record; <database error Message>
- Error : Failed to save Contact record <database error Message>
If you experience any of these Errors, without another accompanying Message about what might have caused the Save Failure, please submit a Ticket to PCR.
UDF Associations
User Defined Fields on any given Import are all handled the same way with Conditional Logic. For more information about adding a UDF to the Import, see the User Defined Fields section of the Imports main page.
...