-
Notifications
You must be signed in to change notification settings - Fork 23.2k
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
[FW][FIX] account_edi_ubl_cii : Fix constraints #162628
Closed
fw-bot
wants to merge
1
commit into
odoo:saas-17.1
from
odoo-dev:saas-17.1-16.0-fix-ubl-constraint-aboo-Tdgn-fw
Closed
[FW][FIX] account_edi_ubl_cii : Fix constraints #162628
fw-bot
wants to merge
1
commit into
odoo:saas-17.1
from
odoo-dev:saas-17.1-16.0-fix-ubl-constraint-aboo-Tdgn-fw
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR targets saas-17.1 and is part of the forward-port chain. Further PRs will be created up to master. More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
@aboo-odoo @JulienVR ci/runbot failed on this forward-port PR |
This was referenced Apr 19, 2024
fw-bot
force-pushed
the
saas-17.1-16.0-fix-ubl-constraint-aboo-Tdgn-fw
branch
from
April 22, 2024 07:18
e1197b6
to
d6baa08
Compare
Problem --------- Because of this PR: 155896, the customer default value for the UBL export values has been modified from commercial partner to partner. However, in 16.0, some constraints have been added to verify that some fields were properly set up before generating the XML. Those restrictions clash with the said changes. Indeed: 1 - Create NO company 2 - Set up UBL on invoice journal 3 - Create a new NO customer and set up UBL in the same way 4 - Create an invoicing address for that customer 5 - Create an invoice for with the customer set as the invoice address set up in step 3. 6 - Send & Print with UBL selected >> An error is added to the export errors while it should not. Solution --------- Use the commercial partner when checking constrains of all fields other than addresses. OPW-3848367 X-original-commit: 201ddbe
fw-bot
force-pushed
the
saas-17.1-16.0-fix-ubl-constraint-aboo-Tdgn-fw
branch
from
April 22, 2024 07:26
d6baa08
to
d41f7ce
Compare
@robodoo r+ |
robodoo
pushed a commit
that referenced
this pull request
Apr 24, 2024
Problem --------- Because of this PR: 155896, the customer default value for the UBL export values has been modified from commercial partner to partner. However, in 16.0, some constraints have been added to verify that some fields were properly set up before generating the XML. Those restrictions clash with the said changes. Indeed: 1 - Create NO company 2 - Set up UBL on invoice journal 3 - Create a new NO customer and set up UBL in the same way 4 - Create an invoicing address for that customer 5 - Create an invoice for with the customer set as the invoice address set up in step 3. 6 - Send & Print with UBL selected >> An error is added to the export errors while it should not. Solution --------- Use the commercial partner when checking constrains of all fields other than addresses. OPW-3848367 closes #162628 X-original-commit: 201ddbe Signed-off-by: Julien Van Roy (juvr) <juvr@odoo.com> Signed-off-by: Antoine Boonen (aboo) <aboo@odoo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Because of this PR: 155896, the customer default value for the UBL export values has been modified from commercial partner to partner.
However, in 16.0+, some constraints have been added to verify that some fields were properly set up before generating the XML. Those restrictions clash with the said changes.
Indeed:
1 - Create NO company
2 - Set up UBL on invoice journal
3 - Create a new NO customer and set up UBL in the same way 4 - Create an invoicing address for that customer
5 - Create an invoice for with the customer set as the invoice address set up in step 3.
6 - Send & Print with UBL selected
Solution
Use the commercial partner when checking constrains of all fields other than addresses.
OPW-3848367
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: #162366
Forward-Port-Of: #160523