-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
[10.0] [contract_payment_auto] IntegrityError raised when token is related to the partner and not the contract #165
Comments
fcayre
added a commit
to fcayre/contract
that referenced
this issue
May 23, 2018
When a contrat had no payment token but the corresponding partner had one, the transaction was created without an acquirer, leading to an integrity error in postgres. This change makes sure the token used to test the ability to pay an invoice is passed along to the transaction creation call. Tests were also added to check the ability to use the contract token if present, but the partner's in the opposite case. This change fixes OCA#165.
Closing this as there's now a PR. |
pedrobaeza
pushed a commit
that referenced
this issue
May 28, 2018
…en (#167) When a contrat had no payment token but the corresponding partner had one, the transaction was created without an acquirer, leading to an integrity error in postgres. This change makes sure the token used to test the ability to pay an invoice is passed along to the transaction creation call. Tests were also added to check the ability to use the contract token if present, but the partner's in the opposite case. This change fixes #165.
norlinhenrik
pushed a commit
to norlinhenrik/contract
that referenced
this issue
Dec 19, 2019
…en (OCA#167) When a contrat had no payment token but the corresponding partner had one, the transaction was created without an acquirer, leading to an integrity error in postgres. This change makes sure the token used to test the ability to pay an invoice is passed along to the transaction creation call. Tests were also added to check the ability to use the contract token if present, but the partner's in the opposite case. This change fixes OCA#165.
fcayre
added a commit
to fcayre/contract
that referenced
this issue
Mar 3, 2022
…en (OCA#167) When a contrat had no payment token but the corresponding partner had one, the transaction was created without an acquirer, leading to an integrity error in postgres. This change makes sure the token used to test the ability to pay an invoice is passed along to the transaction creation call. Tests were also added to check the ability to use the contract token if present, but the partner's in the opposite case. This change fixes OCA#165.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Traceback looks like:
A pull request is coming soon. The bug is due to an inconsistency between the payment token existence tests in
_pay_invoice
and in_get_tx_vals
.The text was updated successfully, but these errors were encountered: