Conversation
Related lock-date fields on res.config.settings inherited the
company_id.hard_lock_date label ("Hard Lock Date"), triggering Odoo's
duplicate-label warning on module upgrade/load.
Journal form xpaths used a rigid /list/field path that can fail when
account_payment (or similar) alters the payment-method list structure;
switch to descendant //field matching.
Co-authored-by: Cursor <cursoragent@cursor.com>
Owner
|
hi @ezoer , thank you |
odoomates
added a commit
that referenced
this pull request
Sep 18, 2026
…heck and journal xpath om_hr_payroll_account - Confirming a payslip raised "Missing Debit Or Credit Account in Salary Rule" whenever no single salary rule carried both accounts, even though the debit and the credit side may legitimately come from two different rules. The check now looks at the accounts of the whole payslip. Reported in PR #135. om_account_accountant - The journal xpath required the payment method fields to sit directly inside a <list>, so it broke as soon as another module wrapped or altered it. Reported in PR #198.
odoomates
added a commit
that referenced
this pull request
Sep 18, 2026
…heck and journal xpath om_hr_payroll_account - Confirming a payslip raised "Missing Debit Or Credit Account in Salary Rule" whenever no single salary rule carried both accounts, even though the debit and the credit side may legitimately come from two different rules. The check now looks at the accounts of the whole payslip. Reported in PR #135. om_account_accountant - The journal xpath required the payment method fields to sit directly inside a <list>, so it broke as soon as another module wrapped or altered it. Reported in PR #198.
odoomates
added a commit
that referenced
this pull request
Sep 18, 2026
…heck and journal xpath om_hr_payroll_account - Confirming a payslip raised "Missing Debit Or Credit Account in Salary Rule" whenever no single salary rule carried both accounts, even though the debit and the credit side may legitimately come from two different rules. The check now looks at the accounts of the whole payslip. Reported in PR #135. om_account_accountant - The journal xpath required the payment method fields to sit directly inside a <list>, so it broke as soon as another module wrapped or altered it. Reported in PR #198.
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
2 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.
Summary
Two Community accounting issues observed on Odoo 18 production (Elementure):
om_fiscal_year—tax_lock_date/sale_lock_date/purchase_lock_date/hard_lock_dateonres.config.settingsare allrelated='company_id.hard_lock_date'without explicitstring=. Related fields inherit the comodel label, so Odoo warns that multiple fields share "Hard Lock Date" (and Sentry captures it when logging includes warnings).om_account_accountant— journal form xpath//field[@name='inbound_payment_method_line_ids']/list/field[@name='payment_account_id']failed during view combine (ValueError: Element ... cannot be located in parent view) when the payment-method list structure differs (e.g. withaccount_paymentinheritance). Using descendant//field[@name='payment_account_id']is more resilient and matches patterns already used in Odoo coreaccount_paymentviews.Changes
om_fiscal_year/models/account_settings.py: set explicitstring=on each lock-date related field.om_account_accountant/views/account_journal.xml: change xpath to//field[@name='…_payment_method_line_ids']//field[@name='payment_account_id'].Test plan
om_fiscal_yearon Odoo 18; confirm noTwo fields … have the same label: Hard Lock Datewarning in logs.account_paymentinstalled; confirm no view inheritance error and payment account columns still optional=show.Made with Cursor