...
By default, the first time a Department Hierarchy is encountered in an Import File and a Permitted GLA is provided, the Permitted GLA list is cleared. Then, the provided value is added. After the first occurrence, the values are appended. If you want to append to the existing list without clearing it, the APPEND_PERMITTED_GLA flag should be set to True.
Errors
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 or multiple matches found within the Database
Toggle cloak Cloak - Error : Could not find the Billing Group '<BillingGroup>'
- Error : Could not find the Default SLA '<SLA>'
- Error : Could not find the Default Incident SLA '<SLA>'
- Error : Could not find the Default GLA '<GLA>'
- Error : Could not find the Permission GLA '<GLA>'
- Error : Invalid parent Dept Hierarchy Code <DeptHierarchyCode>
A blank value was provided, for a field with a required value
Toggle cloak Cloak - Error : Missing or Blank Dept Hierarchy Code
The System was unable to save the record
Toggle cloak Cloak - Error : Failed to save Dept Hierarchy <DeptHiearchyCode>; <errorMessage>'
- Error : Failed to Save null GLARestrict record; <errorMessage>'
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.
...