...
This Import allows Users to Import Usage records and is functionally similar to the Calls Import.
The resulting usage will appear in the Usage Details and Usage Detail Errors grids.
Matches On
Usage matches on the Service ID field.
Fields
Service ID
Required
Datatype is String.
You can provide a formatted or unformatted value for this field. If you provide a formatted value, it must match the formatted value in the Service table. For example, "555-123-4567" will not match "(555) 123-4567".
You can also provide an Alias value of an existing Service. The provided Alias value must exactly match the format in the Alias record.
Service RECID
Datatype is Number.
Default
...
is blank.
This is used to specify the Service Record for Services that have a blank Service ID.
If this is provided, the provided value must be a valid existing Service RECID.
If it is not, it will cause an error.
If a Service RECID value is provided, the Service ID field will be ignored.
Bill Date
Datatype is String.
Default value is blank.
Cost
Datatype is StringNumber.
Default value is blank.
Description
...
Default value is blank.
Quantity
Datatype is StringNumber.
Default value is blank.
Service Type
...
The Service can exist as any Service Type.
If the Import Format specifies a particular service type, only services from that type will be considered in the Service ID lookup.
Usage Time
Data type Datatype is String.
Default value is blank.
...
Default value is blank.
Usage Date/Time
Data type is StringRequiredif Usage Date and Usage Time are not provided.
Datatype is DateTime.
Default value is blank.
If this is assigned in Conditional Logic, then the value is expected to be in this format: "MM/DD/YYYY HH:MM:SS", or a number of seconds since Jan 1, 1970.
If separate Date and Time field values are provided, as well as the single Date/Time field value, then the Date/Time value will be used, and the separate fields will be ignored.
Usage Type
Data type is String.
...
There are no current Conditional Logic flags for the Usage import.
Errors
Because of the very large volume of Imported data that can occur for Calls and Usage Imports, the Error reporting is done very differently. For other Imports, if an Error happens, the Error is reported in the Imported Records grid. For Calls and Usage, the Error is stored as a code in the Call or Usage record. The available codes are in this list. This list is shared for Calls and Usage. Some of these are specifically for Calls and never happens for Usage.
...
happen for Usage.
After running a Usage import, you can go to the Usage Details or Usage Detail Errors grids, and these Error Codes will be under the "Error" column. If you use the Usage Details grid, you will need to remove the default Filter on the Status column to see the records with errors.
Errors
An error occurred during the Import File Processing. This re-tries each night.
| Toggle cloak |
|---|
| Cloak |
|---|
|
...
|
...
|
...
|
...
|
Unrecoverable Errors
An error occurred that cannot be fixed. It does not try again each night.
| Toggle cloak |
|---|
| Cloak |
|---|
|
...
|
Rating Errors
An error during the rating process. This re-tries each night.
| Toggle cloak |
|---|
| Cloak |
|---|
|
...
|
...
...
Billing Errors
Indicates an error occurred during the billing process.
| Toggle cloak |
|---|
| Cloak |
|---|
|
Notes
- A Service must exist for each Usage record.
- The Service can exist as any Service type.
- If the Import Format specifies a particular Service Type, only Services from that type is considered in the Service ID lookup.
...