This documentation supports the 23.3 version of BMC Helix ITSM.To view an earlier version, select the version from the Product version menu.

Importing records with higher ID numbers than those currently issued by system

When uploading records for transactional data and if those records have higher ID numbers than are currently available in the system, you must adjust the nextId counter on the HPD:CFG Ticket Num Generator form to avoid encountering the following AR Systemerror: "ARERR 382 - Unique Index violations".

Use the following example for reference: 

Related topics

Loading-Foundation-data-by-using-Data-Management

Populating-the-dataload-spreadsheets

Data-Management


Example

A system administrator is using the Data Management Transactional_Incident.xlsx spreadsheet to import several hundred incident tickets to a freshly installed BMC Helix ITSMsystem. The incident request IDs of the imported records start at 1 and goes sequentially to 500. That is, INC000000000001, INC000000000002, INC000000000003, INC000000000004, and so on.

After the import completes successfully and the system is ready for production, the end users begin creating new incident requests. Because this is a new BMC Helix ITSM system, the system assigns the following ID number to the first newly created incident request: INC000000000001. As soon as the end user tries to save the new request, the AR Systemissues the following error message, because the user is creating a record with an ID number that is assigned to another record:

"ARERR 382 - Unique Index violations"
=== The value(s) for this entry violate a unique index that has been defined for this form : schema: HPD:Help Desk, entry: INC000000000206, 2 unique index(es), field(s): 1000000161 179 (ARERR 382) ===

To prevent this error, the administrator must perform the following steps:

  1. Before performing the import, determine the range of Incident IDs that are being imported through Data Management.
  2. On the newly installed system, update the nextId counter for the HPD:CFG Ticket Num Generator form in AR schema to a value higher than the highest ID number in the import.
    For example, if the highest ID number is 500, the administrator can update the nextId counter to 1001. Leaving a large gap between the two numbers ensures that there is no overlap with the incident requests numbers.
  3. Restart the AR System servers.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*