Company: Link Technologies
Case No: L12615. Project: 13.03: LinkSOFT version 13.03
Logged By: Sanjay (Link Technologies) on 13 Oct 2021 10:51AM
Priority: High
Product: Framework
Group: Software Defect
Time Taken: 16.00 (Weight: 18.00)
Version: 13.03.0917
Assigned To: Development
Circulation: Development, Sanjay
Resolve By: Friday, 08 October 2021 11:59 PM [922 days since logged date]
Status: Closed
Subject: Batch ID for Replication API Queues causes Non-Unique ID's when using high-performance machines

Batch ID for Replication API Queues causes Non-Unique ID's when using high-performance machines. Error Message is:

Violation of PRIMARY KEY constraint 'PK_LT_SYS_ProcessMaintenanceDetailLog'. Cannot insert duplicate key in object 'dbo.LT_SYS_ProcessMaintenanceDetailLog'. The duplicate key value is (ND.20210913.091810.4688116.1-Replication-Send.URL.POST).

Audit Notes:Edited by sanjay on 13/10/21 10:51. Edited by sanjay on 13/10/21 10:39. 
13 Oct 202110:39AM Comment 1 by Sanjay (Link Technologies) Case L12615 added to project 13.03
13 Oct 202110:44AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 13-10-2021 04:39 PM Time Taken: 12.00 Notes: Edited by sanjay on 13/10/21 10:51. 
PART A - Development work for this case has been completed.

Batch ID is a Time function that uses the format "YYYYMMDD. HHMMSS.6DigitMicrosecond" Example: ND.20210901.152521.7784618
The issue was caused by Batch ID's being generated too fast causing the same batch ID allocated to the API Queue.

To resolve the issue, we have added a GUID to the end of the Batch ID, changing the format to: "YYYYMMDD. HHMMSS.^DigitMicrosecond_GUID"
e.g: ND.20211007.132441.737.1_B7353D2C-B827-4E6F-8E82-F44D14AD7FF8

1. The change will be available in version:13.03.0917

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

  1. Change Batch Identifier format

3. Affected Areas:

  1. Replication using Web API

4. The issue was caused by:

  1. Batch ID Uniqueness Test did not allow for high-performance machines

5. Other Relevant Notes
6. Next Step
(Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT

13 Oct 202110:46AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 13-10-2021 04:44 PM Time Taken: 4.00
The following tests were performed:

Table 1 - Test Results
#Test Case DetailsPass/FailComments
 1Check Batch ID created by updated batch ID function

Old Format:ND.20210901.152521.7784618
New Format:ND.20211007.132441.737.1_B7353D2C-B827-4E6F-8E82-F44D14AD7FF8

Environment Details

  1. OS version: Win10
  2. Application version: 13.03.0923
  3. Setup on:
    1. Server: LinkQA4
    2. Database: CLIENT-NAYANS-PillingRoad
    3. LinkSOFT URL: HTTP://
  4. Login Details: Standard username and password for user "admin"

Next Step: Closure 

13 Oct 202110:51AM Comment 4 by Sanjay (Link Technologies) ETC was changed from 08/10/2021 to 08/10/2021
If you have any queries regarding this support incident, please email and include the Case No: L12615 in the subject line of all emails regarding this issue.

Document size: 7.7 KB
For call complaints, please contact the Managing Director of the company using this form