For vendor bank accounts we are populating the routing number (configured as source code for UK), bank account number and IBAN. The fields are validated through the IBAN format defined in Cash and bank module so it's very unlikely that there would be a mistake in one of these values as they are all validated against each other.
I am trying to track changes to any/all of these fields using the Approve vendor bank accounts workflow, which is in preview.
The system tries to track each change individually, even though there are dependencies for the 3 fields.
For example (these are dummy numbers):
Routing number: 123456
Bank account number: 98765432
IBAN: GB82WEST12345698765432
Scenario: The bank account number is incorrect and should be 98765433.
When I change the bank account number, the system immediately gives me the option to save or discard the change AND gives me an error that the IBAN number is not correct. It then keeps the old bank account number of 98765432 on the main form, as the change has not been approved yet.
If I then try to change the IBAN number as well to GB82WEST12345698765433, I get the same error that the bank account (which is the unsaved value of 2 and not 3) is wrong. The change to 3 is sitting on the Pending changes form, but I can't approve this without also first changing the IBAN number as part of the same change set.
I have to first approve the changes for the changes for the bank account number change (which the system allows) but technically this overrides the logic between the bank account number and the IBAN number.
Is there another way to process both changes (bank account number + IBAN) simultaneously without removing the IBAN format?
Share
Report
All responses (
Answers (
301,079
