This update ensures Odoo can correctly validate Brazilian CNPJs, which are transitioning to an alphanumeric format due to government expansion. This change avoids a dependency issue with an older validation library and prepares Odoo for future Brazilian business registrations. It’s a necessary update to support Brazilian businesses accurately.

Purpose: The Brazilian Federal Government, through the Brazilian Federal Revenue Service (Receita Federal do Brasil), is implementing the alphanumeric CNPJ to address the imminent depletion of its capacity to generate new CNPJ numbers. The current, exclusively numeric model is approaching its limit. The transition to a format that includes letters and numbers expands the number of possible combinations, ensuring the future availability of registrations for new companies. With the government expanding the CNPJ numbers, we need to implement a solution to support the alphanumeric CNPJ that will be issued starting July 2026.

Current Behavior: The method, `is_valid,` from stdnum is currently used to determine whether the CNPJ is valid or not. This is now considered an outdated method to determine the validation.

Changed Behavior: The new validation logic by stdnum, found here https://github.com/arthurdejong/python-stdnum/commit/d3ec3bd7fefe0d0a708b6594a66de28777eb9b8d, is patched into `check_vat_br.` The reasoning for patching this rather than calling stdnum is because using stdnum will cause library dependency issues for older versions of Odoo.

task-5234869
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#262939
Forward-Port-Of: odoo/odoo#260516

This update ensures the demo data for Brazil (l10n_br) is accurate and reliable. The changes update product and company information, improving the quality of testing and providing a more realistic demonstration of the Brazil localization features within Odoo. This helps ensure accurate reporting and configuration for businesses using the Brazil module.

Updated Brazil Product and company demo data to ensure accurate testing

task-6159933

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#261636

This update improves the Brazil demo data within Odoo Enterprise to ensure accurate testing of the l10n_br_avatax module. The changes include updated product and company data, allowing for more reliable testing of Brazil-specific tax calculations and reporting. This ensures the demo environment reflects the latest requirements.

Updated Brazil Product and company demo data to ensure accurate testing

task-6159933

Forward-Port-Of: odoo/enterprise#115361

This update ensures Odoo can correctly validate Brazilian CNPJs, which are transitioning to an alphanumeric format due to government changes. This change avoids a dependency issue with an older library and prepares Odoo for future CNPJ registrations. It’s a necessary update to support Brazilian businesses accurately.

Purpose: The Brazilian Federal Government, through the Brazilian Federal Revenue Service (Receita Federal do Brasil), is implementing the alphanumeric CNPJ to address the imminent depletion of its capacity to generate new CNPJ numbers. The current, exclusively numeric model is approaching its limit. The transition to a format that includes letters and numbers expands the number of possible combinations, ensuring the future availability of registrations for new companies. With the government expanding the CNPJ numbers, we need to implement a solution to support the alphanumeric CNPJ that will be issued starting July 2026.

Current Behavior: The method, `is_valid,` from stdnum is currently used to determine whether the CNPJ is valid or not. This is now considered an outdated method to determine the validation.

Changed Behavior: The new validation logic by stdnum, found here https://github.com/arthurdejong/python-stdnum/commit/d3ec3bd7fefe0d0a708b6594a66de28777eb9b8d, is patched into `check_vat_br.` The reasoning for patching this rather than calling stdnum is because using stdnum will cause library dependency issues for older versions of Odoo.

task-5234869
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#262939
Forward-Port-Of: odoo/odoo#260516

This update improves the demo data for Odoo's Brazil localization (l10n_br) module. The changes ensure the demo data accurately reflects Brazil's tax and business regulations, making it more reliable for testing and showcasing the module's functionality. This update primarily impacts the demonstration of the l10n_br module.

Updated Brazil Product and company demo data to ensure accurate testing

task-6159933

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#261636

This update improves the accuracy of the Brazil demo data within Odoo Enterprise. The changes to product and company data ensure that testing of the l10n_br_avatax module runs smoothly and reflects current Brazilian tax regulations. This supports ongoing development and validation of the Brazil localization features.

Updated Brazil Product and company demo data to ensure accurate testing

task-6159933

Forward-Port-Of: odoo/enterprise#115361

This update ensures Odoo can correctly process Brazil's new alphanumeric CNPJ business registration numbers, which are being implemented to avoid registration number limitations. The change utilizes a new validation library to accommodate this format, preventing future issues with company registration data. This update is crucial for accurate financial reporting and compliance in Brazil.

Purpose: The Brazilian Federal Government, through the Brazilian Federal Revenue Service (Receita Federal do Brasil), is implementing the alphanumeric CNPJ to address the imminent depletion of its capacity to generate new CNPJ numbers. The current, exclusively numeric model is approaching its limit. The transition to a format that includes letters and numbers expands the number of possible combinations, ensuring the future availability of registrations for new companies. With the government expanding the CNPJ numbers, we need to implement a solution to support the alphanumeric CNPJ that will be issued starting July 2026.

Current Behavior: The method, `is_valid,` from stdnum is currently used to determine whether the CNPJ is valid or not. This is now considered an outdated method to determine the validation.

Changed Behavior: The new validation logic by stdnum, found here https://github.com/arthurdejong/python-stdnum/commit/d3ec3bd7fefe0d0a708b6594a66de28777eb9b8d, is patched into `check_vat_br.` The reasoning for patching this rather than calling stdnum is because using stdnum will cause library dependency issues for older versions of Odoo.

task-5234869
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#262939
Forward-Port-Of: odoo/odoo#260516

This update ensures the demo data for Brazil (l10n_br) in Odoo is current and reliable. The changes to product and company information improve the accuracy of testing and demonstrations for this specific Odoo localization. This is an important improvement for developers and consultants working with the Brazil tax compliance features.

Updated Brazil Product and company demo data to ensure accurate testing

task-6159933

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#261636

This update improves the Brazil demo data within Odoo Enterprise to ensure accurate testing of the l10n_br_avatax module. The changes include updated product and company data, aligning the demo environment with current tax regulations for Brazil. This ensures developers and testers can reliably evaluate the module's functionality.

Updated Brazil Product and company demo data to ensure accurate testing

task-6159933

Forward-Port-Of: odoo/enterprise#115361

This update ensures Odoo can correctly process Brazil's new alphanumeric CNPJ format for company registration. The Brazilian government is transitioning to this format to avoid registration limits, and this change updates Odoo's validation process to accommodate the new standard. This ensures accurate data processing for Brazilian businesses.

Purpose: The Brazilian Federal Government, through the Brazilian Federal Revenue Service (Receita Federal do Brasil), is implementing the alphanumeric CNPJ to address the imminent depletion of its capacity to generate new CNPJ numbers. The current, exclusively numeric model is approaching its limit. The transition to a format that includes letters and numbers expands the number of possible combinations, ensuring the future availability of registrations for new companies. With the government expanding the CNPJ numbers, we need to implement a solution to support the alphanumeric CNPJ that will be issued starting July 2026.

Current Behavior: The method, `is_valid,` from stdnum is currently used to determine whether the CNPJ is valid or not. This is now considered an outdated method to determine the validation.

Changed Behavior: The new validation logic by stdnum, found here https://github.com/arthurdejong/python-stdnum/commit/d3ec3bd7fefe0d0a708b6594a66de28777eb9b8d, is patched into `check_vat_br.` The reasoning for patching this rather than calling stdnum is because using stdnum will cause library dependency issues for older versions of Odoo.

task-5234869
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#262654
Forward-Port-Of: odoo/odoo#260516

This update ensures the sample dashboards within Odoo Enterprise accurately reflect the latest design and functionality changes. These updated dashboards provide more current and relevant examples for users exploring the platform's reporting capabilities. This improves the user experience and helps demonstrate the current state of the system.

This commit updates the sample dashboards to reflect the recent changes made in the dashboards.

Task: 5076188

This update enhances the appearance of online order notifications within the Point of Sale interface. By using a full-width layout and improved alignment, the notifications now display more clearly on smaller screens, providing a better user experience for customers. This change was implemented to improve visual consistency and usability.

In this commit:
-------------------
- Use a full-width layout on small screens by removing container padding and
improving alignment with `justify-content-between`.

task: 6054267

Forward-Port-Of: odoo/enterprise#116478
Forward-Port-Of: odoo/enterprise#111614

This update introduces a new 'Vertical Percentage' comparison mode for accounting reports, allowing users to easily see the percentage difference between report lines and a chosen reference line. This enhances report analysis and provides more flexible insights into financial data. The change limits comparison options to efficient report lines.

Added a new comparison method 'Vertical Percentage' in the accounting reports comparison menu. This feature allows users to compare all report lines against a specific, user-selected line to display the percentage difference.

Key updates:
  - Introduced a new comparison method: vertical_percentage.
  - Added a comparison option displaying as 'Vertical Percentages based on: <selected option>'.
  - Limited available comparison options to lines using the domain or aggregation engines.

This enhancement improves report analysis by allowing flexible percentage comparisons against a defined reference line.

task-5144252

Related Community PR: https://github.com/odoo/odoo/pull/251129

This update modifies the way annual tax calculations (atn) are handled in the Odoo Enterprise's Belgian payroll module. Specifically, the calculation now uses a yearly atn, aligning with current Belgian tax regulations. This ensures accurate and compliant payroll processing for employees in Belgium.

. Update car_atn to yearly atn

task-6128621

This update introduces a mobile preview toggle within the snippet selection dialog, allowing users to see how snippets will look on mobile devices before they are added to a website. This improves the user experience by ensuring snippets are appropriately formatted for different screen sizes, leading to more consistent and visually appealing websites.

This commit introduces a mobile preview toggle in the snippet selection
dialog, allowing users to preview how snippets will appear on mobile
devices before inserting them into the page.

Changes:
1.Added a mobile view toggle button in the dialog header.
2.Enabled switching between desktop and mobile preview modes.
3.Adapted dynamic snippets to ensure mobile-specific appearance
in the preview dialog.

task-5062953

This update allows users to directly view videos within social stream posts, enhancing content engagement. The system now handles different video formats from platforms like Facebook and Instagram, and redirects Twitter videos to the original post. Technical changes improve data handling and the user interface for video display.

Purpose
========
To enable video support in social stream posts.

Specification
==============
Videos can now be played directly from the Media Carousel Dialog.

Note: Twitter videos are currently unavailable and will redirect to the original post.

Technical
==========
- Rename the model 'social.stream.post.image' to 'social.stream.post.attachment'.
- Add the 'type' field to specify the content type.
- Add the 'thumbnail_url' field to specify thumbnail of video.
- Update all class names to reflect the changes.
- Rename the field 'stream_post_image_ids' to 'stream_post_attachment_ids'.
- Rename the field 'stream_post_image_urls' to 'stream_post_content_json'.
- The 'stream_post_content_json' field is now computed as a key-value pair containing
the content type, url and thumbnail url.
- Rename the component 'ImagesCarouselDialog' to 'MediaCarouselDialog'.
- Introduce an optional 'media_type' prop in MediaCarouselDialog to support redirection
for twitter video.

social_facebook:
- For single content, the API returns 'video_inline' and 'animated_image_video' for
video formats.
- For albums, the API returns 'video' for any video or GIF content.

social_instagram:
- The API specifies content types as either 'VIDEO' or 'IMAGE'.

social_linkedin:
- GIFs are received as image files.

social_twitter:
- The API provides only 'preview_image_url' for videos and GIFs, so we store post link in
content_url and preview_image in thumbnail.
- Clicking on a preview in the MediaCarouselDialog redirects to the Twitter post.

Task-3897765

This update enhances the way employee records are linked within the Odoo Enterprise payroll system. Specifically, new fields have been added to create a linked list between employee records, improving data consistency and accuracy. This change supports future system updates and ensures reliable payroll processing.

This update enhances the Gantt view within the field service module by reducing the display precision to the quarter level. This simplifies the view and prevents it from becoming cluttered with excessive data, improving readability and usability. The total aggregate calculation has also been removed to further optimize the display.

This commit changes the day scale precision to quarter in the gantt view of field service. Additionally, the total aggregate is removed because otherwise the view would be polluted by too many information on tiny spaces.

task-6200910

This update enhances the manufacturing order Gantt chart by allowing users to quickly view related work orders when filtering by product, displaying product quantity and UoM, and improving the overall user experience. The changes streamline the Gantt chart for better visibility and efficiency in managing production schedules.

Changes requested:

1. Clicking on the product in the row header (when grouped by product) should open a list view of MOs for that product. (Requires overriding the Gantt renderer template.) **Done**
2. Append the product quantity and the UoM to the MO name in each pill. **Done**
3. Disable the action for clicking on the table itself. **Done**
4. Rename the edit button on the pill popover to 'Open Manufacturing Order'. **Done**
5. Minimum space between product internal reference and the status widget in the pill popover. **Done**
6. ~~Set a grey background colour for weekends. (Might require computing unavailabilities for a Gantt API function in the model?)~~

Additionally, the `mrp_workorder` frontend files were stowed into their own directory out of `/static/src/` basedir.

Task ID: [6088506](https://www.odoo.com/odoo/my-tasks/6088506)

This update allows users to manually set CST codes for ICMS, PIS, COFINS, and IPI on EDI invoices, addressing a previous limitation where Avalara lacked a direct configuration option. This change simplifies the process for NF-e invoices, improving user experience and saving time by overriding Avalara's automatic calculations for EDI invoice requests.

Before this Commit:
- Avalara does not have a dedicated field/configuration on its website to allow users to set the right CST for all taxes.

After this Commit:
- We added new fields to Operation Types to manually override Avalara's CST calculation for ICMS, PIS, COFINS, and IPI.
- All these new field values will be sent only for the EDI Invoice Request (submit-invoice-goods) not for Avatax calculation.
- Now the user can manually override the CST value using the field of operation type for NF-e (EDI goods invoice).
- Improve the user experience and save the user time.

task-5404891

This update improves the Brazil demo data within Odoo Enterprise, specifically for the l10n_br_avatax module. The changes ensure the demo data accurately reflects Brazil's tax regulations, leading to more reliable testing and validation of the module's functionality. This supports better development and testing of the Brazil localization features.

Updated Brazil Product and company demo data to ensure accurate testing

task-6159933

Forward-Port-Of: odoo/enterprise#115361

This update enhances the logging process during cloud storage migration, providing more detailed information about the migration's progress. Previously, logging was limited, making it difficult to track and troubleshoot issues. Now, users will receive clearer logs, streamlining the migration process and improving overall reliability.

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