[17.0] [MIG] fieldservice_account_payment#1490
Open
Conversation
rrebollo
force-pushed
the
17.0-mig-fieldservice_account_payment
branch
2 times, most recently
from
2620af0 to
71b6078
Compare
edescalona
suggested changes
Jan 14, 2026
edescalona
left a comment
edescalona
left a comment
There was a problem hiding this comment.
Code review. Great work @rrebollo , if you could complete the tests.
Co-authored-by: Daniel Reis <dreis@opensourceintegrators.com>
Currently translated at 100.0% (9 of 9 strings) Translation: field-service-14.0/field-service-14.0-fieldservice_account_payment Translate-URL: https://translation.odoo-community.org/projects/field-service-14-0/field-service-14-0-fieldservice_account_payment/it/
Currently translated at 100.0% (9 of 9 strings) Translation: field-service-14.0/field-service-14.0-fieldservice_account_payment Translate-URL: https://translation.odoo-community.org/projects/field-service-14-0/field-service-14-0-fieldservice_account_payment/es_AR/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: field-service-15.0/field-service-15.0-fieldservice_account_payment Translate-URL: https://translation.odoo-community.org/projects/field-service-15-0/field-service-15-0-fieldservice_account_payment/
Currently translated at 100.0% (5 of 5 strings) Translation: field-service-15.0/field-service-15.0-fieldservice_account_payment Translate-URL: https://translation.odoo-community.org/projects/field-service-15-0/field-service-15-0-fieldservice_account_payment/it/
inject `default_customer_id` in context in tests to stick to the required fields in `fsm.location` in `fieldservice_account_analytic` wrong inbound_payment_method_line on bank journal
rrebollo
force-pushed
the
17.0-mig-fieldservice_account_payment
branch
from
71b6078 to
92e69cf
Compare
rrebollo
force-pushed
the
17.0-mig-fieldservice_account_payment
branch
from
4096483 to
9577996
Compare
rrebollo
force-pushed
the
17.0-mig-fieldservice_account_payment
branch
from
9577996 to
13526a1
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
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.
Standard migration based on #1489
We had to make a "regression" on the test suite, using the old
setUpapproach given thatfieldservice_accounttest class was merged with this approach.Edit: but then we had an issue when creating the locations (because
fieldservice_account_analytic): required customer_id field. At the end we did a mix of v15,v16 and OCA suggested approach for v17.#1132
@BinhexTeam