-
-
Notifications
You must be signed in to change notification settings - Fork 109
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][FIX] intrastat_product: Prevent error when adding transaction details on invoices #237
[16.0][FIX] intrastat_product: Prevent error when adding transaction details on invoices #237
Conversation
…s on invoices The exclude_from_invoice_tab field does not exist in v16
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.
Fast-tracking as pretty straight-forward:
/ocabot merge patch
What a great day to merge this nice PR. Let's do it! |
@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-237-by-pedrobaeza-bump-patch. 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. |
1 similar comment
@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-237-by-pedrobaeza-bump-patch. 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. |
Agh, copier template is not updated... on it. |
Update at 542c62f /ocabot merge patch |
Hey, thanks for contributing! Proceeding to merge this for you. |
It looks like something changed on |
Congratulations, your PR was merged at aedac20. Thanks a lot for contributing to OCA. ❤️ |
Prevent error when adding transaction details on invoices
The exclude_from_invoice_tab field does not exist in v16.
Please @pedrobaeza and @sergio-teruel can you review it?
@Tecnativa