Article Details
Id:13372
Product:finPOWER Connect
Type:FIX
Version:2.03.03
Opened:20/10/2015
Closed:21/10/2015
Released:30/10/2015
Job: J016421
Breaking Change

Process Direct Debit Payments; fails with a "Record was not updated" error

The Process Direct Debit Payments wizard may fail with a "Failed to commit Account Direct Debit Payments. Record was not updated. This record may have been deleted or edited by another User." error during a commit.

To recreate:

  1. Create an Account with multiple "Owner" Clients and that have the same Client Type, e.g. "I".
  2. Have a Direct Debit Payment ready to process for the Account.
  3. Open the Account Direct Debit Payments wizard and enter a Client Type Range of "I" and select only that Account (this makes it simple to see the issue).
  4. Click next and review the list. There will be duplicate items shown, one for each Client of the Account with a Client Type of "I".

Clicking "Finish" causes this error as the items are processed more than once. The whole commit is rolled back as if nothing had happened.

Note, the same issue applies to both the Client and Client Group ranges.

A change has been made so only the "Main", i.e. the first, Client for an Account will be factored into the range filtering. This makes it consistent with other range filters such as Account Processes.

In addition, the following wizards have been updated to follow the same logic - although they did not cause an issue this this.

Close Accounts wizard Export Bank Transactions wizard

And finally the list of Bank Transactions for a Client, as displayed on the Transaction page for an Account, will now only show for the main Client.