Tuesday, April 8, 2025
9 changes · 17.0
Resolved issues and error corrections
The Point of Sale test setup was corrected so automated checks no longer reference a missing product category. This helps keep the validation pipeline stable and reduces delays caused by false test failures.
Original PR description
Fix tests that were using unexisting category in runbot. Removing the category from the product since categ_id isn't necessary in PoS tests. runbot error: 162900
The demo product “Drawer” now uses lot tracking to match the sample inventory records already linked to a lot. This prevents confusion when reviewing demo inventory data and keeps product settings consistent with existing stock examples.
Original PR description
The demo product 'Drawer' was initially configured to be tracked by quantity, but a lot was incorrectly created, and the stock quant was subsequently created for the 'Drawer' with lot. Steps to reproduce =============== - Install the 'stock' module with demo data. - Navigate to Inventory > Products > Products and search for 'Drawer'. - Observe that 'Drawer' is set to track by quantity (Tracking field). - Check Inventory > Operations > Physical Inventory and locate the stock quant for 'Drawer'. - Note that a lot exists and is linked to the product 'Drawer', despite the quantity tracking setting. This commit modifies the demo data to enable lot tracking for the product, aligning its configuration with the existing lot and stock quant data for consistency.
The Nilvera unit code mapping has been moved into the shared Turkish Nilvera module so both e-invoice and e-despatch processes can use it. This helps ensure consistent document data across Nilvera integrations and avoids duplicate logic in separate document features.
Original PR description
The UNECE code mapping for Nilvera was done in l10n_tr_nilvera_einvoice. here at #193030 However later that was needed in l10n_tr_nilvera_edespatch and that too in stock_move. This PR moves the mapping from l10n_tr_nilvera_einvoice to l10n_tr_nilvera so that it can be used by both einvoice and edespatch. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change fixes an internal stock module test that could fail unpredictably because product records were checked in an inconsistent order. It helps keep automated builds reliable without changing day-to-day user behavior.
Original PR description
### Issue:
The test `test_orderpoint_replenishment_view_3` is failling its assertRecordValues on the replenishments since these are created using the `set` of product ids. However, when the ids are 191, 192 and 193, `list(set(191, 192, 193)) == [192, 193, 191]`. In addition the sorted('product_id') added in the assertion does not change the order by a yota since the `product_id` is a relational field so that the order used in the sorted method is the order `__lt__` of Base model that is the order of record inclusion (and hence is False in each comparaisons).
runbot-162792
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prText entered into website editor tables now wraps within table cells instead of spilling over nearby content. This improves readability and editing reliability on both small and large screens when users add tables with long content.
Original PR description
When you add a table via "/table" when you're in editing mode, and if there's a lot of content, then the content overlaps. This is noticable in the small devices as well as bigger devices. We'll stop the overflow by using overflow-wrap: break-word. Steps To Reproduce on Runbot: 1. Go to editor via website/elearning. 2. Add table via command "/table" 4. Make the table like size 11*2, and keep typing on a cell, eventually the text will start overflowing. opw-4317744
Closing a production order from the shop floor no longer sends users to the backend when backorders are set to always be created. This keeps shop floor workers in the right screen and avoids workflow interruptions.
Original PR description
### Before this PR If the backorder is "always", on the shopfloor when clicking "close production" on the "production overview", it redirects to the backend ### After this PR Clicking on close production it does not redirect to backend
This fixes a missing permission so purchasing users can read the Kenya OSCU stock compliance data needed by the system. It helps prevent related automated checks and workflows from failing due to insufficient access.
Original PR description
adding missing access rule (read permission to the group_purchase_user) for the test that checks it build_error-70728
This fixes Spanish translations for Peruvian stock operation types so they match official SUNAT terminology. Users working with Peruvian inventory documents will see the correct regulated labels, reducing confusion and reporting errors.
Original PR description
Some keys were not correclty translated Steps to reproduce: ------------------- * Install l10n_pe_reports_stock * Switch to PE Company and Spanish language * In Stock create a new operation * Open the dropdown Type of Operation (PE) > Observation: Why the fix: ------------ Based on official values https://www.sunat.gob.pe/legislacion/superin/2015/anexo3-rs169-2015.pdf Tabla 12 opw-4653572
This fixes an issue where Amazon order synchronization could fail when it encountered older offer records stored in a legacy format. These unused references are now ignored during order sync, allowing sales operations to continue while regular stock synchronization handles any future updates.
Original PR description
Following commit 6b5acdde9998fb1ee0d4d4aee0ab2375e50d7703 we ensured that we stopped the stock synchronization when there was a discrepancy between an offer fulfilment channel and an order fulfilment channel. This bugfix didn't consider the cases of offers that were synced once then never updated with the changes of the new API, thus not being the string of a dictionary, but instead, being the string of an int. Thus raising an attribute error, and not a JSON error nor a TypeError. These offers, though, don't need that safety net, and can thus just be ignored. If their stock needs to be sync someday, the stock cron will take care of these. opw-4684657 opw-4684605