| Id: | 13305 |
| Product: | finPOWER Connect |
| Type: | NEW |
| Version: | 2.03.03 |
| Opened: | 16/09/2015 |
| Closed: | 18/09/2015 |
| Released: | 30/10/2015 |
| Job: | J016247 |
 Breaking Change |
|
Transactions; not updating record timestamp when it should be incremented
When updating a record in the AccountTransaction and BankTransaction tables, the Timestamp and Updated User + Date/Time were not always updated.
This could mean other functions, where the Transaction timestamp is checked in the commit, eg Transaction Adjustment, would continue without an error where the Transaction has changed in another process. This typically should not be allowed.
Changes have been made to the following processes to ensure the Transaction timestamp is now updated:
- Transaction Reverse
- Bank Transaction Reverse
- Account Status changing from Open to Closed and Closed Pending To Open
- Account Restructure
- Creating Account Statements
- Reversing Account Statements
- Process Direct Debit Payments
- Disbursement Account Payments
- Generate Tax Certificates
- General Ledger Export
- Close Accounting Period
- Close Tax Period
Note, this change has been flagged as a breaking change. If you have scripts that use any of the function listed above, please retest your code. The change made here may mean that Transaction information held in memory, in particular the Timestamp, may be out-of-date, and Business Layer functionality that used to work will now fail with an error like "No record was updated. This record may have been deleted or edited by another User.".