13120 – Logging duplicate line when changing default contract and then the credit limit on a Sales Ledger records multiple times
Version Reported In
Sicon Audit Log v221.0.18
Detailed Description
When attempting to amend a Sales Ledger account’s credit limit after modifying another record on the same account, such as updating a secondary contact, the Audit Log will still record the changes made to the previous amendment.
- Within the Sage 200 menu, go into Sicon Auditing and select Settings.
- Inside the Auditing Setting pop-up, select SOP and tick Enable Auditing. Press Save.
![]() |
3. Now go to Sales Ledger > Customer list and select the Sales Ledger record and press the Amend button.
4. Go to the Contacts tab and select another contact to be a default contact (select record and press the Set as Default Press Save and enter a comment.)
5. Now, go back and amend the Sales Ledger account.
6. On the Company tab, change the Credit Limit and press Save.
7. Now the Audit Log will show the credit limit change, plus the previous contact change.
Impact: Low
- Urgency | Ability to work not affected; inconvenient.
- Impact | All users affected.
Workaround
Having the extra line does not impact the process you are trying to undertake. You may have a duplicate line; however, the information will still be correct. If you need the audit log output to be accurate, please follow the instructions below. Between amending the record for the second time, we suggest:
- Within the Customer List screen, find another record you need to amend, select it, and press the Amend button.
- Make a change to the selected record and save it.
- Now conduct the credit limit change within the original Sales Ledger account, and the audit log will only show one item.
To further prevent this issue, we recommend making multiple changes in one go to have everything logged in one area.
Development Priority Voting
Please let us know your development priority for this Known Issue by providing us with a star rating based on the below;
- Not causing any problems – not a priority.
- It’s annoying, but not causing too many problems – not a priority.
- Would be nice to be fixed, but not essential – not a high priority.
- It would be helpful to have this fixed – fairly high priority.
- Really needs to be fixed as soon as possible – high priority.