Thursday, February 15, 2024
2 changes · saas-17.1
Resolved issues and error corrections
This fix ensures localization-specific fields are available immediately when users create new records for companies in affected countries. It prevents missing country-dependent information during setup, reducing confusion and avoiding incomplete data entry.
Original PR description
Install `l10n_ar` Switch to an AR company Create a new currency => the field `l10n_ar_afip_code` is not visible Go on an existing one => it is visible The compute is not triggered before the save. We should add a default to have the fiscal_code. We can even remove the compute (and keep the store=False), to avoid duplicating the code. Linked to runbot error 45392, 45417 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Creating a new landed cost now correctly applies the company’s fiscal country by default. This ensures the Mexican customs number field is shown when needed, helping users enter required customs information without extra workarounds.
Original PR description
To reproduce: Having installed `l10n_mx_edi_landing`, go to landed costs. Create a new one => `l10n_mx_edi_customs_number` is not visible The reason being that the `fiscal_country_code` is not computed at creation. We should add a default.