Company: Link Technologies
Case No: L12172. Project: 12.40: LinkSOFT Version 12.40 - 12.41
Logged By: Sanjay (Link Technologies) on 15 Feb 2021 09:39AM
Priority: Low
Product: Framework
Group: Enhancement
Time Taken: 5.00 (Weight: 40.00)
Version: 12.40
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Sanjay
Resolve By: Friday, 30 April 2021 11:59 PM [1157 days since logged date]
Status: Closed
Subject: Review Error Logging to prevent multiple entries for the same error
Review Error Logging to prevent multiple entries for the same error, e.g: Error Message "Product [DC001] price is not setup" is raised by:
  1. LT_POS_Inventory_SelectByID
  2. LT_POS_Inventory_SelectByID_OUTPUT
  3. and twice by .NET
  4. Review Errr consolidations in Event Log


  1. The logging function checks the error severity number to log the message. If the severity number is 16, it will log the message. Any numbers less than 16 is not logged. This implies the error message has already been logged previously.
  2. Utilise the error severity to determine if logging is required.
  3. This change will need to be implemented in all procedures in the database.
  4. Change the error logging by .NET to read the error severity and send that to the error logging function.

For example:

  1. LT_POS_Inventory_SelectByID - system logs this error with a severity number of 16 and raises it to the calling procedure with a severity of 11.
  2. LT_POS_Inventory_SelectByID_OUTPUT - logs the error with severity of 11. Since the severity is less than 16, the system will not log this error.
  3. and twice by .NET 
Audit Notes:Edited by sanjay on 19/04/21 13:24. Edited by sanjay on 13/04/21 11:38. Edited by sanjay on 12/04/21 14:36. Edited by alvis on 25/02/21 10:44. Edited by sanjay on 25/02/21 10:41. Edited by sanjay on 25/02/21 10:37. 
25 Feb 202110:15AM Comment 1 by Sanjay (Link Technologies) Case L12172 added to project 12.4
25 Feb 202110:37AM Comment 2 by Sanjay (Link Technologies) ETC was changed from 20/02/2021 to 20/02/2021
25 Feb 202110:41AM Comment 3 by Sanjay (Link Technologies) ETC was changed from 20/02/2021 to 19/03/2021
12 Apr 202104:50PM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 14-04-2021 04:49 PM
Review error logging and analyse how best to manage this

13 Apr 202111:38AM Comment 5 by Sanjay (Link Technologies) ETC was changed from 19/03/2021 to 30/04/2021
21 Apr 202104:01PM Comment 6 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 23-04-2021 03:55 PM Time Taken: 1.00
PART A - Development work for this case has been completed.

1. The change will be available in version: 12.41

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

  1. When an error has occurred in a SQL procedure, we log this error and re-raise it with severity 11. The UI has been configured not to log this error. Errors with severity 10 or under are ignored by the UI.
  2. The error logging procedure will not log entries with a severity less than 16.
  3. As the procedures are modified we will implement this rul.

3. Affected Areas:

  1. Framework error logging

4. The issue was caused by:

  1. improvementnt

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


PART B - Development Reference (Place descriptor for objects changed):

1. Changes implemented was according to the approved design (Y/N):

2. Other relevant notes:


Before Development is started, ensure the following is ready:
1. The case has a clear definition of the issue or change required
2. A test plan is in place
3. Change has been approved by Sanjay

a. System Test is performed by development in the "Finalised" Development environment ({version}
b. UAT is performed using the installation provided

26 Apr 202101:47PM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 28-04-2021 01:45 PM Time Taken: 4.00
Error logging has been tagged to log only if the severity is greater than 15.

If you have any queries regarding this support incident, please email and include the Case No: L12172 in the subject line of all emails regarding this issue.

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