Company: Link Technologies
Case No: L12009. Project: 11.40: LinkSOFT Version 11.4
Logged By: Alvis (Link Technologies) on 13 Jul 2020 11:58AM
Priority: High
Product: Point of Sale
Group: Software Defect
Time Taken: 7.00 (Weight: 7.00)
Version: 11.4.0903
Assigned To: Rashna (Edge Business Solutions)
Circulation: Alvis, Rashna, Sanjay
Resolve By: Monday, 13 July 2020 04:26 PM [1382 days since logged date]
Status: Closed
Subject: POSCASH customer created with incorrect ID in the new month
Summary:    

Issue:

When the configuration "Concatenate year/month to POSCASH account code" is set to "Month", the ID for the record is incorrectly created.

This causes replication sync issues as the replication requires the ID to be the same value in all the servers.

Audit Notes:Edited by alvis on 08/12/20 08:37. Edited by alvis on 13/07/20 11:58. Edited by alvis on 13/07/20 10:26. 
13 Jul 202010:26AM Comment 1 by Alvis (Link Technologies) Case L12009 added to project 11.4
13 Jul 202010:37AM Comment 2 by Sanjay (Link Technologies) Assigned To: Alvis (Link Technologies) Followup Date: 13-07-2020 04:26 PM Time Taken: 2.00 Notes: Edited by alvis on 13/07/20 12:05. 

Development work for this case has been completed.

The change will be available in version:11.4.0713, 12.0.0713

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

  1. Corrected the customer ID created from procedure "LBS_POS_Customer_Update" to use format "Company-Code". This is required for replication to sync data across servers. The customer ID is used to link the records for synchronization.

2. Affected Areas:

  1. Replication for customer Masterfile
  2. Time Maintenance -> Customer, Customer Projects, Customer Project Limit
  3. Union Maintenance -> Rates
  4. Verify customer projects, limits, Union Rates and time entry are linked after upgrade

3. The issue can be reproduced by:

  1. Setup replication between 2 servers
  2. Set the configuration "Concatenate Year/Month for POSCASH" to "Month"
  3. Stop replication process
  4. Do a cash sale in both servers. The cash sale process will create a customer record in each server.
  5. Enable the replication process. The event log will show the replication error.

4. Notes: 
5. Next Step: System test

----------------------

Development Reference:


13 Jul 202011:58AM Comment 3 by Alvis (Link Technologies) ETC was changed from 13/07/2020 to 13/07/2020
13 Jul 202001:56PM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 13-07-2020 07:25 PM Time Taken: 2.00
System test completed

13 Jul 202004:12PM Comment 5 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 13-07-2020 10:11 PM Time Taken: 1.00
Hi Rashna, please proceed with UAT before release.

15 Jul 202012:46PM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 15-07-2020 06:24 PM Time Taken: 2.00
QA Results
Tests carried out according to requirements specified on the case header

Test Results Summary

Table 1 - Summarised list of issues
NoTest DescriptionPass/Fail
1
  1. Installed version 11.4.507 from the website
  2. Setup replication between LinkSOFT-HQ and LinkSOFT-B1 databases.
  3. Set the configuration "Concatenate Year/Month for POSCASH" to "Month" in both databases.
  4. Stopped the replication process by disabling SQL Agent.
  5. Performed a cash sale on both servers. The cash sale should create a POSCASH customer for July 2020.
  6. Enable SQL Agent. Validate the event log for errors.
    1. Error - Cannot insert duplicate key row in object 'dbo.LBS_POS_Customer_all' with unique index 'UX_LBS_POS_Customer_all_CompanyID_Code'. The duplicate key value is (1001, POSCASH-202007).
  7. Upgraded the database to version 11.4.713.
  8. Confirmed that the sales are replicated without errors.
  9. Perform steps 4 and 5 after the upgrade. The sale should be replicated without errors
Pass
2
  1. ?Installed version 11.4.507 from the website
  2. Created below records under Time Maintenance in database LinkSOFT-HQ
  3. Customer - RPL
  4. Project - INS
  5. Activity - Wiring
  6. Mapped project "INS" to customer "RPL".
  7. Mapped activity "Wiring" to project "INS".
  8. Added the Customer, Project, and Activity to union rates for "Union Northern Division"
  9. Upgraded database to version  11.4.713. 
  10. Validated that the above mappings and links existed after the upgrade
Pass

Environment Details

  1. OS version: Windows Server 2012
  2. Application version: 11.4.713
  3. Setup: Demo
  4. Server : 10.0.0.12
  5. Database: LINKSOFT-HQ and LINKSOFT-B1

Next Step: 

  1. Closure

    If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L12009 in the subject line of all emails regarding this issue.

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