-
-
Notifications
You must be signed in to change notification settings - Fork 526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[16.0][IMP] Take allow_out_payment into account on payment order #1340
base: 16.0
Are you sure you want to change the base?
[16.0][IMP] Take allow_out_payment into account on payment order #1340
Conversation
9a523ec
to
386628a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GJ 💪
Just a minor change 🙏
386628a
to
5f1064e
Compare
5f1064e
to
a02bcff
Compare
/ocabot merge minor |
Hey, thanks for contributing! Proceeding to merge this for you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have stopped the merge. AFAIK, @sbidoul commented that wants to be able to add the lines, but not to confirm the order, and this is pre-filtering the non-allowed bank accounts previously if I understand the code right.
@adrienpeiffer your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-1340-by-adrienpeiffer-bump-minor. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@pedrobaeza Not sure to understand. The check is done in draft2open method. |
I mean this code for example: It's avoiding to include the lines in the order. |
Isn't that exactly the code approved in #1177 ? |
OK, I based my review in #1177 (comment). Let me check again. |
@lmarion-source Could you remove blank lines (cfr pedro's review) |
It is my impression that Odoo Enterprise works like that, and it makes sense to me, since the process of preparing payment orders is distinct from the process of validating bank accounts, and often done by different persons. So I think it's better to let both processes run in parallel and block at the last moment. Cherry on the cake would be a warning when an non validated bank account is used in a payment line, but that can be done in another PR. |
a02bcff
to
565a13b
Compare
Hmm, we solved this completely differently. I get the minimal touch here, but we made a seperate module that hit all the places Odoo gets this wrong, mostly purchase order and account move but also payment with a single function on bank to get a valid out payment bank account. Then overrode |
565a13b
to
5be3c4b
Compare
5be3c4b
to
1cd2603
Compare
A previous MR existed but only when payment order was triggered from invoices. We added the case also directement from confirm button on payment order original PR: OCA#1177
1cd2603
to
adb3c59
Compare
A previous MR existed but only when payment order was triggered from invoices.
We added the case also directly from confirm button on payment order
Original PR: #1177