...
The Service Import allows the User to INSERT and UPDATE Service Records. Child records of the Service is association records only. Each Service type requires its own distinct Service Import. For example, Auth Codes are imported using an Auth Code Service import. This accommodates the service-specific fields used by different Service types. For example, Phone Service uses Service Host as a field choice that is not available for other Service types.Insert excerpt
Matches On
The Import attempts to match the Service ID. If there is no match, the record from the Import will INSERT. If there is a match, the remaining fields can UPDATE.
...
Service Catalog
Datatype is Hierarchical String.
Conditionally Required IF the Import is trying to INSERT a new record.
...
Dept. Hierarchy Owner
Datatype is Hierarchical String.
This Import expects Only the Code From the Dept. Hierarchy code, not the Descriptionis expected.
Location
Datatype is Hierarchical String.
Conditionally Required if Status is Active AND if the Service Catalog flag Location Required is set.
...
The USE_RATING_GROUP Configuration flag is set to True.
SLA Catalog
Datatype is Hierarchical String.
Reference
Datatype is String.
...
The only Service Type permitted to have blank Service IDs is Other Services .
Child Records
Charges Tab
...
GLAs added to a Service with the Service Import ONLY adds an association between the existing GLAs and the selected Service in the Import File. The Service Import cannot INSERT or UPDATE GLA records.
GLA
Datatype is Hierarchical StringString.
GLA must be the full GLA Path with all Components separated by the GLA_CONCATENATOR.
Multiple levels of a hierarchy "path" (like Locations, GLAs, and Catalogs) are connected by the HIERARCHYPATH_SEPARATOR string.
The default value for this string is right angle-brace (>) with a space on either side: " > ".
When importing nested Locations, the separator you use for each level of the hierarchy must match the concatenator string.
For example, Site A > Building B > Room C.
GLA Expense Type
Conditionally Required if GLA is provided.
...
The Equipment fields try to identify an existing Equipment record to add to the Equipment tab of the Service. They are checked in the order of the list below. If a value is blank, it is ignored by the Import process. If the value is filled in, the Import attempts to do the lookup.
An Equipment can only be associated if the Service Status is 'Active' or 'Suspend'. And the existing Equipment Status must be 'Assigned'.
If the Service Location and Equipment Location are different, it will cause an import Warning, but the association will still get created.
By default, Equipment will get appended to any existing Equipment already on the Service. See the Flags below to change this behavior.
Equipment Asset
Datatype is String.
...
Equipment Location
Datatype is Hierarchical String.
The Equipment Location value is used only with a non-blank Equipment ID. If a non-blank Equipment ID is not provided, then the Location value is ignored. You cannot lookup an Equipment with just a Locationfull Location Path hierarchy in a single string, with individual parts of the Location Hierarchy separated by the HIERARCHYPATH_CONCATENATOR.
Multiple levels of a hierarchy "path" (like Locations, GLAs, and Catalogs) are connected by the HIERARCHYPATH_SEPARATOR string.
The default value for this string is right angle-brace (>) with a space on either side: " > ".
When importing nested Locations, the separator you use for each level of the hierarchy must match the concatenator string.
For example, Site A > Building B > Room C.
The Equipment Location value is used only with the Equipment ID.
Equipment Serial Number
Datatype is String.
Equipment Mac Address
Datatype is String.
Equipment
...
Record
Datatype is Number.This is the RECID field from the Equipment record. This is usually not visible, but it can be obtained from an export. This method will always provide a unique number. It is useful for Equipment with blank values for all of the other key fieldsString.
If the lookup fails,
...
the Import stops and output an error message. This error does not affect the Service INSERT or UPDATE, only the Equipment tab association.
Flags / Conditional Logic
...
- True: Setting the flag to True appends Pools to matching Service ID Pools and does not clear any existing Pools.
- False: Setting the flag to False clears existing Pools on matching Service IDs and updates the Pool on the first instance of that Service. Any additional Service ID Pools are appended after the first instance.
Errors
When an Import Line fails, it is usually because the Line falls into one of the following categories:
...
| Cloak |
|---|
|
...
| Cloak |
|---|
|
...
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 display if the Service INSERT or UPDATE fails:
- Error : No Service ID Specified
- Error : No Status provided for new Service '<SERVICE_ID>'
- Error : Invalid Contact '<OWNER_CONTACT>'
- Error : Invalid Dept Hierarchy '<OWNER_DEPT_HIERARCHY>'
- Error : Inactive Service Catalog '<SERV_CATALOG>'
- Error : Invalid Service Catalog '<SERV_CATALOG>'
- Error : Inactive Service Catalog '<SERV_CATALOG>'
- Error : No Service Catalog Specified
- Error : Invalid Service Host '<SERVICE_HOST>'
- Error : Provided Service Host not permitted for this service catalog
- Error : Invalid Location '<LOCATION>'
- Error : Invalid Location Type '<LOCATION_TYPE>'
- Error : Provided Location not permitted for this Service Catalog
- Error : Invalid GLA Percent '<percent>'
- Error : Missing GLA Expense Type
- Error : Missing GLA Percent
- Error : Invalid GLA '<gla>'
- Error : Missing GLA
- Error : Invalid Service Pools '<service_pool>'
- Error : Invalid Billing Group '<BILLING_GROUP>'
- Error : Invalid Class Of Service '<class of service>'
- Error : Missing Auth Code type for new Auth Code '<SERVICE_ID>'
- Error :
...
- Can't assign Equipment unless Service Status is Active or Suspend
- Error : Can't assign Equipment unless Equipment Status is Assigned
- Error : This Equipment Catalog type is restricted from being on this Service Catalog type
- Error : Failed to save Service record; <errorMessage>
- Error : Service <serviceId>, GLA type <expenseTypeListsRecid>; <errorMessage>
- Error : Service <serviceId>, GLA type <expenseTypeListsRecid>, Percents add up to <sum> (should be 100)
- Error :
...
- Invalid Equipment Asset Tag '<asset>"
- Error :
...
- Error : Failed to save Service record; <errorMessage>
- Error : Service <serviceId>, GLA type <expenseTypeListsRecid>; <errorMessage>
...
- Invalid Equipment Location '<location>'
- Error : Invalid Equipment for Equipment ID '<equipmentId>'
- Error : Found multiple existing Equipment for Equipment ID '<equipmentId>'
- Error : Invalid Equipment Serial Number '<serialNumber>'
- Error : Found multiple existing Equipment with Serial Number '<serialNumber>'
- Error : Invalid Equipment MAC Address '<macAddress>'
- Error : Found multiple existing Equipment with MAC Address '<macAddress>'
- Error : Invalid Equipment RECID '<recid>'
These messages are NOT indications that the Service INSERT or UPDATE to failed. The Service will INSERT or UPDATE. However, the subsequent Child record may have a warning generate and the child record is not added to the Service. They are non-essential for the Service or they happen after the Service save.
- Warning : Invalid SLA Catalog '<SLA_CATALOG>'
- Warning : Invalid Service Host '<SERVICE_HOST>'
- Warning : Invalid Available Service Host '<SERVICE_HOST>'
- Warning : Service Location doesn't match Equipment Location
Notes
The ability to append Pools to a Service was added. The default behavior for adding Pools is to clear the Pool list for the first instance of a Service ID in the import file. Then, append to the Pool list for every instance of the Service ID after the first. This can be changed with the APPEND_POOLS flag as described in the Flags section.
...
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.Child pages (Children Display)