Daily updates from Odoo
Tuesday, March 4, 2025
8 changes
4 changes
Enhancements to existing features
Payroll users can now populate Individual Accounts reports without automatically generating PDFs for every eligible employee. They can choose specific employees or generate/post all relevant PDFs from the available report actions, giving teams more control and reducing unnecessary document creation.
Original PR description
Problem ---------- When you click on populate in "Individual Accounts" report, it trigger the pdf generation automatically for all eligible employees Objective ---------- We want to let the user decide if he wants to generate all the pdfs or if he wants to select which of them should be generated. Solution ---------- - The populate button not trigger the generate pdf action. - In Employee declaration view, the "Generate PDF(s)" button is always visible. - If the user select some of the employees, the button will trigger the pdf generation only for them. Else, if the user does not select anyone, all pdfs are generated. task-4161348
Recruitment teams now use a clearer signature request flow for applicants, with the applicant's email filled in by default instead of the current user's email. Users can also send signature requests to multiple applicants from the list view, reducing manual work and avoiding duplicate wizard options.
Original PR description
Problem ---------- - In an application form view, There are 2 Signature Request wizard accessible from the cogwheel menu. We have to use only the wizard from sign. And not our custom one in…
Problem ---------- - In an application form view, There are 2 Signature Request wizard accessible from the cogwheel menu. We have to use only the wizard from sign. And not our custom one in hr_recruitment_sign. - Change this sign wizard to replace the user mail with the applicant mail. - In case of selection of multiple application in list view. We have to be able to send signature request to all of them with a new wizard in the action cogwheel menu. This wizard must be the same as the sign request for employee one. Objective ---------- - Remove our sign request wizard in the cogwheel menu of applicant form view. - Adapt the sign wizard to display the applicant email by default. - Add the multiple sign request wizard in the cogwheel menu of list view. Solution ---------- For the multiple sign request : I use the previous customized wizard in hr_recruitment_sign (replaced by the sign one). Just adapt it to be usable with multiple records. So now the "signature request" action available in the cogmenu is display only in list view for multiple sign requests. Finally, for the sign request wizard in form view. To make it custom for the hr_applicant model. I needed to adapt and override the context of the cogmenu item to add the default signer and the active model. And adapt and override the sign_send_request to change the default signer. task-4260572
Appointment events are being simplified so each booking can link directly to its resource instead of relying on separate booking lines. This should make resource changes and calendar/grouped view editing easier for teams managing appointments.
Original PR description
Prior to this, each event had an o2m relation with booking lines. This made validation easy but also makes some tasks such as modifying the resources used and editing grouped views more cumbersome. We remove the booking lines and replace them with a direct m2o relation between events and appointment resources. task-338900
Deleting recurring shifts now consistently shows a confirmation dialog in list, kanban, and calendar views, matching the existing behavior in the form view. This helps users choose how to handle recurring shifts and reduces the risk of accidentally deleting the wrong planning entries.
Original PR description
[IMP] planning: improve recurring shifts deletion Before this commit: - Deleting recurring shifts from the form view would display a dialog with options for handling the deletion of recurring shifts. However, this behavior was inconsistent in the list, kanban and calendar views, where deleting a recurring shift would delete the shift without showing any dialog. After this commit: - List view: when some shifts are recurring, the modal is displayed - Kanban and Calendar view: when the shift is recurring, the modal is displayed. task-4149099
4 changes
Enhancements to existing features
Invoices now automatically use the salesperson assigned to the customer when one is set, rather than defaulting to the person creating the invoice. This helps keep sales ownership consistent from customer records through invoicing and improves reporting accuracy.
Original PR description
For `sale.order`, the salesperson (`user_id`) on the order is set to the partner's salesperson (`user_id` on `res.partner`) if set. Currently, `account.move` sets the salesperson (`invoice_user_id`) to the user creating the invoice. With this commit, `invoice_user_id` is set to the partner's salesperson if exists. task-4374265
Bill details fetched from Indian e-invoices are now handled more reliably, including portal attachment limits, reverse charge taxes, and taxes missing from the local setup. Temporary portal errors are also retried automatically, reducing manual follow-up and improving accounting completeness.
Original PR description
This PR introduces the following improvements: - **Attachment Name Update**: Restricts the attachment name to 45 characters to comply with e-invoice portal limitations. - **Handling Missing Taxes**: Includes journal items for taxes not found in the system to ensure proper accounting. - **Enhanced Tax Matching**: Updates the tax-finding mechanism to include RCM taxes when the bill transaction's `RegRev` parameter is marked as `Y`, in addition to regular taxes. - **Error handling**: Handle `EINV30109` error code to schedule a retry cron after 10 minutes and log a message.
Point of Sale now supports configurable limits for how many products and customers are loaded. This helps businesses tune POS performance and data availability based on their store size and operational needs.
Original PR description
- Introduced `ir.config_parameter` settings for product and customer limits in POS. - Refactored partner loading to use configurable customer limit. community PR: https://github.com/odoo/odoo/pull/199923 task-id: 4610131
Accounting report XLSX exports now include a separate currency code column next to foreign-currency amounts. This makes exported reports clearer and helps users identify the currency behind each amount after symbols are lost in spreadsheets.
Original PR description
Issue: When we export a report to xlsx containing some amounts in foreign currency, those amounts are exported as values in the file, and loose any kind of currency symbols. It then becomes impossible to know what currency they were expressed in. Solution: When a column has an expression label with the 'currency' word inside, adds a new column right next to it, with the currency 3 letters code as value. This is done in the accounting reports framework and so is used on all reports using a custom engine. task-4011008