Friday, March 7, 2025
36 changes
4 changes
Resolved issues and error corrections
A recent internal change missed a related adjustment in the India reporting module, which could cause errors when using certain linked record fields with avatars. This fix restores the expected behavior so users can continue working in India reports without that disruption.
Original PR description
In the commit [1], we refactor the many2one widgets but the specialisation in this module was missed and caused an error. [1]: bcaa9e9b23d637edfe05baff83aea2ac18d9f4b2
Activating developer mode with the India reports module installed no longer triggers a validation error. This helps administrators and support teams use debug tools without being blocked by an unexpected issue.
Original PR description
This PR fixes an issue where activating developer mode triggers a validation error due to an invalid `component` object. Steps:- 1. Install the `l10n_in_reports` module. 2. Enable debug mode. 3. Receives a validation error.
Manual runs of the reconciliation process now record automated follow-up actions as performed by Odoobot instead of the person who clicked the button. This keeps invoice and activity history consistent with background reconciliation runs and avoids misleading user attribution.
Original PR description
The aim of this commit is to make all the action triggered by clicking the "Run manually" button in the reconcile.model from view performed by Odoobot. Motivation: - information consistency: As this…
The aim of this commit is to make all the action triggered by clicking the "Run manually" button in the reconcile.model from view performed by Odoobot. Motivation: - information consistency: As this is just a button triggering a bunch of automated action, we don't want the user clicking on the button to be tagged in the chatter as performing ALL the side effect action. For example, if an invoice gets reconciled by the process, before this commit, the invoice would be marked as paid by the user that clicked the button. After this commit, it will be marked as performed by Odoobot. - behavior consistency: The end of the method triggers a CRON that will perform this action again on the remaining statement line to process but in the background. This will use the Odoobot user instead of the user that clicked the button. For example, before this commit, an invoice auto-reconciled in the second run of the method will be marked as paid by Odoobot while the invoices autoreconciled in the first run were mark as paid by the user clicking the button. task-id: None (This was brought up during investigation on 4393854)
Clicking a cell in payroll payslip pivot reports no longer triggers an error. This keeps payroll reporting usable by preventing the system from sending users to the wrong payroll screen.
Original PR description
Issue: when clicked on any pivot cell it raise error Solve: remove the js_class as it was forcing the redirect into hr.payroll Task: 4626207
7 changes
Resolved issues and error corrections
This fixes issues in Documents where some embedded actions, such as creating a vendor bill from the Finance folder, could not be removed. It also ensures those actions remain available when documents are accessed through shortcut folders, improving consistency for users.
Original PR description
First commit: Fix a bug which prevents un-embedding actions: Reproduce: 1. Install documents_account 2. Go to the finance folder 3. Try to un-embedd the action "Create a Vendor Bill" 4. You can't This occurs because we created the embedded actions by passing a group in the data, but we can't do that in the UI, so we cannot un-embed the existing action. This also means that groups cannot be enforced at the embedded actions level using their groups_id field, but rather the groups_id field of the related server action, and it was actually redundant. Thankfully these records are correct. Second commit: Fix using embedded actions when viewing documents from a container shortcut. Task-4525850
The barcode interface no longer shows the return products option where it cannot be used, such as delivery batches or transfers that are not completed. This prevents users from hitting an error and keeps warehouse actions aligned with valid return workflows.
Original PR description
Steps to Reproduce the Bug: - Install stock_picking_batch. - Go to Barcode > Operations > Delivery Orders > Batches. - Select any batch: - Click on the Parameters button > In the Operation section: -…
Steps to Reproduce the Bug:
- Install stock_picking_batch.
- Go to Barcode > Operations > Delivery Orders > Batches.
- Select any batch:
- Click on the Parameters button > In the Operation section: - Click on Return Products.
Problem:
A traceback is raised:
"The method 'stock.picking.batch.action_create_return_picking' does not exist."
The function “action_create_return_picking” belongs to the “stock.picking” model, not to “stock.picking.batch” records. We are not supposed to be able to return products from a batch.
Moreover, even for “stock.picking” records, products can only be returned from done pickings. However, this button is displayed in all picking states except the done state:
https://github.com/odoo/enterprise/blob/2d5dbb93e6b33c2be786f9b2361c993f715d1a7f/stock_barcode/static/src/components/main.xml#L119
Solution:
Have the same condition for done pickings as in:
https://github.com/odoo/enterprise/blob/2d5dbb93e6b33c2be786f9b2361c993f715d1a7f/stock_barcode/static/src/components/main.xml#L165-L170
opw-4624039Kiosk orders paid through a terminal are no longer sent to the preparation display before payment is completed. This prevents staff from preparing unpaid orders while still supporting orders that will be paid at the counter.
Original PR description
to reproduce: ============= - Setup kiosk on POS shop using Stripe or other payment terminal - Open the Preparation display for the shop and start the kiosk - When an order is sent to the terminal on the kiosk, the order appears on the prep display immediately before payment is completed Problem: ======== the issue is introduced when we allowed for he customer to pay on the counter, the order is sent to the preparation display before the payment is completed Solution: ========= add a flag in context to tell if payment should be done in kiosk or on the counter opw-4556029
This update improves how Ecuadorian delivery guides are generated, especially for companies operating in multiple-company setups. It helps ensure the correct company-specific issuing details, customer receiver information, product codes, sequences, and authorization dates are used in electronic and PDF documents.
Original PR description
- For a multicompany environment it is useful to be able to restrict the unique emission point and entity point per company. - The support of the commercial partner is needed for electronic and pdf documents. We use the commercial_partner_id for the receiver. - We place the main code and auxiliary code as in the other documents. The main code is the result of the barcode or default_code or N/A (is required field in xml) - We improve the creation of the sequence in a warehouse when the record is not yet committed. - To generate the authorization number we use the start date of the delivery guide
This fix changes how DIAN demo mode is stored so existing databases are not broken when the module has not been updated. It helps keep Colombian electronic invoicing configurations stable during regular updates.
Original PR description
Issue ----- This commit[^1] added a field in stable version which breaks the database if the module is not updated. Fix --- Instead of using a column in stable, use a config param. [^1]: a6d593a406be75995454eb0666d1d
Resetting invoices to draft now correctly removes deferred entries that were never posted, instead of creating unnecessary reversals. This prevents leftover scheduled accounting entries and keeps deferred revenue or expense records cleaner when audit trail is enabled.
Original PR description
Steps to reproduce: - 1. Activate audit trail. 2. Make a customer invoice with start and end date [end date should be in future months], and post. 3. Reset the invoice to draft - Result: All deferred entries are reversed with new entries at the date of the reset to draft. The unposted deferred entries are still there with auto post At Date. Cause: - Audit trail alone doesn't prevent the moves from being deleted if they were not posted before, so the check shouldn't be only on the company_id.check_account_audit_trail, but also we should consider move.posted_before and if not, it should be deleted not reversed. Fix: - Replace the company_id.check_account_audit_trail check with _is_protected_by_audit_trail() which includes checking if the move is posted before or not. opw - 4562732
Saving a restaurant table appointment could fail when the linked point of sale configuration had no active session. The fix sends appointment updates to the correct reserved-table sessions, preventing the error and allowing staff to save appointments normally.
Original PR description
Steps to reproduce: 1. Open new table appointment form from the appointment app 2. Select a table ressource that is linked to a pos_config that has no current_session_id 3. Save Traceback is shown Fix: When notifying the tables of the appointment update the wrong session object was used. This commit ensure that the correct object is used in order to notify the sessions linked to the reserved tables