Hi,
In 1.0, we were able to set the account field on the customer payment by setting ‘undepfunds’ to ‘F’ and then setting the account. I’ve tried this same flow in 2.0 where I transform an invoice -> customer payment, set ‘undepfunds’ to false and try to set the account. This results in an error that false is an invalid value for undepfunds. ‘F’ is also ignored as its 2.0 so false should be the correct value. I’ve also tried just setting the account directly and no go as well. I’ve tried both dynamic/regular mode and there is no difference. Is there something special in 2.0 that you have to do in order to get this to work? Seems like a bug since the radio button for ‘undepfunds’ won’t accept a boolean. I CAN select the same account manually if I accept payment, manually check account and then select the account I want.
Update:
There are two issues here. One is that it appears you don’t need to set the “undepfunds” field to anything and can set the account directly. It also appears that what is causing the account to be overwritten is setting the native “paymentmethod” field on the customer payment record. This is overwriting the account regardless if it is set before or after setting the account. I’m still not sure if this is a bug but it does seem a bit weird.
Thanks!
This is a cached copy. Click here to see the original post.