Tuesday, September 24, 2024
6 changes · saas-17.2
Resolved issues and error corrections
This fix prevents an error when users with limited timesheet permissions choose an employee on a timesheet. It makes the employee filtering work correctly, improving reliability for restricted-access users.
Original PR description
Issue ----- Traceback when selecting the employee of a timesheet with a user having limited timesheets rights. Change ----- Provide a domain in the correct form to `expression.AND` opw-4163104
This fix keeps related sales, purchase, and manufacturing documents correctly connected during multi-step order flows. It helps teams preserve traceability between customer demand, supplier purchasing, and production, reducing confusion and manual follow-up.
Original PR description
Follow-up on #179964, but this time properly checking if the link is still usable from both sides (i.e. both PO *and* SO). Also fixes the issue with the link from PO <-> MO in the same way. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where Peru and Argentina point-of-sale users could not choose a customer identification type when editing customer details. The POS now loads the correct identification options for the active company, including shared Latin American types, reducing customer data entry errors.
Original PR description
Currently, when modifying customer details, the selection for the identification type is empty. Steps to reproduce: ------------------- * Install **l10n_pe_pos** * Switch to the **PE Company** * Open…
Currently, when modifying customer details, the selection for the identification type is empty. Steps to reproduce: ------------------- * Install **l10n_pe_pos** * Switch to the **PE Company** * Open pos session * Try modifying a customer > Observation: The selection for the field **Identification Type** is empty Why the fix: ------------ In the customer editor view, the selection is loaded with `t-foreach="pos['l10n_latam.identification.type']"`. This field is supposed to be set in the pos data with `this["l10n_latam.identification.type"] = this.data["l10n_latam.identification.type"];` However, `this.data["l10n_latam.identification.type"` is an empty list. We follow the instuctions from the new relational model https://github.com/odoo/odoo/commit/28b7d698be8255f933ba5314e44e7059746fc234 to retreive the fields. We also change the domain used when loading the `l10n_latam.identification.type` to the pos session to account for database that have installed multiple localization. If you install both `l10n_pe_pos` and `l10n_ar_pos`, and you are currently using the PE Company, you will alse see the types that are related to the AR company and not the current one. We alse include those coming from the base `l10n_latam` module and are not related to a specific country. opw-4178323 Enterprise PR: https://github.com/odoo/enterprise/pull/70177
Fixes an error that could block users from merging multiple customer contacts when the Indian localization is active. This helps keep customer records clean and avoids interruptions during routine contact management.
Original PR description
When we select multiple customers and attempt to merge their contacts by removing one of the customers, this error occurs. Steps to reproduce: - Install the ``l10n_in`` module - Switch to ``IN company`` - Invoicing > Customers >Customers - Go to list view > Select all Customers > Actions > Merge - Click on ``Deco Addict``, now come back and remove it - Click on ``Merge Contacts`` Traceback: ``ValueError: Expected singleton: res.partner(50, 46, 43, 36)`` This error occurred at [1] because multiple values are getting in ``self``. This commit will fix the above error by adding it to the loop. [1]- https://github.com/odoo/odoo/blob/737f3af4c2f058bb1f5ef6f0c6f8968bbfa60850/addons/l10n_in/models/res_partner.py#L32-L35 sentry-5800636882 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where mass mailing theme templates could appear squeezed or in a mobile-like layout on large screens. The editor layout now gives the template preview enough room while keeping the snippet panel usable, improving the email design experience.
Original PR description
Purpose ======= Fix the theme templates which are displayed in compressed mode on large screen sizes. Specification ============= Following the extension of the chatter's width, the iframe width became too small to be considered as a large viewport meaning all the bootstrap lg rules aren't correctly applied. Making sure the iframe width is large enough by making it position absolute so that it takes the full form width. Preventing the website snippets from overlapping the template by adding a padding right to the layout. Choosing the iframe to be position absolute instead of the website snippets to make sure the snippets drag to scroll feature still works. related commits: https://github.com/odoo/odoo/commit/916ac1712c7fae4623ec176e688ba13af01be015 https://github.com/odoo/odoo/commit/cf6cd5ef46287f4e71fe96ad6b404ba9b08c1066 Task-4086474 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update addresses a problem in the web interface related to form view button boxes. The fix helps ensure users see and use form action buttons more reliably, reducing confusion during everyday workflows.
Original PR description
Steps to reproduce ================== Cause of the issue ================== Solution ======== opw-4164661 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