Thursday, September 12, 2024
14 changes · master
New functionality added to Odoo
Spreadsheet pivot tables now let users show measures in alternative formats, such as percentages of row or column totals. This makes it easier to compare results and understand relative performance directly in documents and spreadsheets.
Original PR description
This commits adds the "Show value as" feature to measures. This allow users to display the value of a measure in a different way, like percentage of column total, percentage of row total, etc. Task: [4045799](https://www.odoo.com/odoo/2328/tasks/4045799?cids=1)
Enhancements to existing features
Indian payroll now has a dedicated structure type that groups all Indian payroll structures together. This makes payroll configuration clearer and easier to manage for companies operating in India.
Original PR description
This PR enhances the payroll structure and types by introducing a new structure type and integrating all Indian structures into it. task-3505344
Resolved issues and error corrections
This change removes automation-related setup from the Approvals app because it could unintentionally move customers from the standard price plan to a custom plan. Approvals users keep the expected app behavior without triggering an unwanted pricing change.
Original PR description
Approvals app has a dependence on automation and automation makes user go from standard price plan to custom price which shouldn't happen.
The Aged Receivable report now lets users look a set number of days beyond a past reporting date while still excluding later invoices, credit notes, and receipts. This helps auditors and finance teams identify debts that were still unpaid after a defined follow-up period, supporting doubtful debt assessment.
Original PR description
Add a "X days after" filter to the Aged Receivable report. This computes the report at "as of date" + X days but excludes any invoice/credit note/receipt with accounting dates > "as of date." This filter helps identify doubtful debt at a past date while applying later reconciliations, ignoring irrelevant entries after the specified date. Example: - Invoice in December - Payment in January - Matching in February => In April, the auditor asks the status of all the lines of the report on the 31/12 which are not matched at the 31/03, to create doubtful debt. task-4008838
Accounting teams can now create exceptions that effectively remove a lock date, rather than only moving it to another date. This makes lock date management more flexible while preserving the existing exception workflow.
Original PR description
Currently we do not allow removing lock dates completely with an exception (except in the special 'everyone' / 'forever' case in which we just change the actual lock date instead of creating an exception). It was designed like this for technical reasons. An exception stores a "new date" for all the lock date field; a missing value for a lock date field means "no change". E.g.: `exception.sale_lock_date == False` means the exception does not change the sale lock date. After this commit we (pseudo-) allow removing a lock date with an exception. We "simulate" the removal of a lock date by setting the "new date" to a very early date. 1000-01-01 was chosen for technical reasons. It should be before any needed accounting entries. (See comment in the code). related: task-3891414 (lock dates rework)
Accounting entries are now secured when they are posted rather than later in the process, helping ensure records are protected earlier and more consistently. A new Secure Entries wizard also helps companies secure past accounting entries up to a chosen date, supporting stronger compliance workflows.
Original PR description
### commits #### [IMP] account: back to hash on post In the related community PR we move from hash on send (back) to hash on post See community PR. This commit adapts enterprise to the changes. #### [IMP] account: new secure entries wizard In the related community PR we add the Secure Entries Wizard. It's a wizard to secure (hash) all moves up to including a certain dates. See community PR. This commit adapts enterprise to the changes. ### task community PR: https://github.com/odoo/odoo/pull/178915 documentation PR: https://github.com/odoo/documentation/pull/10906 upgrade PR: https://github.com/odoo/upgrade/pull/6458 task-4095970
The Indian payroll yearly salary reports now generate PDFs directly and include both completed and paid payslips. Employee reports adjust to the selected date range up to 12 months, and currency symbols follow the current company for clearer local reporting.
Original PR description
In this PR, - The preview of the report is removed from the yearly salary by head The report will now generate the PDF directly - Payslips in done and paid state are calculated in the yearly salary by head report - Yearly salary by employee is dynamic based on the start-end date, which is not going to exceed 12 months. - The currency symbol is based on the current company. Task - 3981488
Customers can now see cancellation guidance even when an appointment has already been paid, avoiding confusion on the validation screen. If cancellation is not allowed from the summary page, they receive a clearer alert with available staff contact details when possible.
Original PR description
Before, users were sometimes lost when it came to cancelling a paid appointment, as the validation screen did not have any cancelling link. In this PR, we show the link even for paid bookings. However, we do not allow cancelling from the event summary page. Therefore, we display an alert when trying to cancel a paid event. The wording is improved to include name, email and phone of the staff user. It is also updated in existing 'no-cancel' message and status (to `no_time_left`). To do this, the controller is slightly reworked to include an overridable method to return the cancel status. Task-4143212
Sales orders and projects can no longer be moved to a different company when they are linked to shifts belonging to another company. This prevents inconsistent company data and ensures teams update the related shifts first before changing the sales order or project company.
Original PR description
After this commit, it is no longer possible to change the company of an SO or a project if they have been tied to shifts that are not in the company we want to change the SO/project. One must change the company of the shifts before changing the company of the SO/project. Ther rationale is that we want to avoid inconsistent situations where the shifts and the SO/project have different companies. task-3857690
Businesses in Brazil can now import official NF-e XML files for vendor bills related to goods, reducing manual entry and improving compliance with local invoicing standards. The import fills bills using existing company data and can automatically create the vendor when needed; service bills remain out of scope due to city-specific formats.
Original PR description
This adds support for importing electronically invoiced vendor bills for goods. We follow the official Brazilian specification [1]. Service bills are out of scope because each city has its own format.
This populates the bill with data that already exists in the database, the only exception is that the vendor will be automatically created if it doesn't yet exist.
task-3860901
[1] Esquema XML NF-e/NFC-e - Pacote de Liberação nº 9o on
https://www.nfe.fazenda.gov.br/portal/listaConteudo.aspThe UAE payroll module now uses updated payslip printouts tailored to employee status. Active employees receive the monthly salary slip format, while archived employees receive the end-of-service payslip, helping payroll teams provide the right document automatically.
Original PR description
Link to task: [#4133896](https://www.odoo.com/web#model=project.task&id=4133896) This update to the UAE HR payroll module introduces the following changes: - New EOS Payslip Printout: This format will be used as the primary payslip for archived employees. - Updated Monthly Salary Slip Printout: This format will be used for active employees. These enhancements ensure the correct payslip format is automatically selected based on the employee's status.
The Accounting dashboard has been refreshed to better support accountants in reviewing key financial information. This improvement should make day-to-day reporting and monitoring clearer and more useful for business users.
Original PR description
…hboard Task: 4109556
This fix prevents a validation error when adding a new work order step to a manufacturing order after another step has already started. It keeps work order dependencies in the correct sequence, so production teams can update operations without creating false circular dependencies.
Original PR description
### Steps to reproduce: - Create a MO for a product without BOM (no need of components) - Go to the "Work Orders" tab and create 2 operations: op1 and op2 - Confirm the MO - Start the operation…
### Steps to reproduce: - Create a MO for a product without BOM (no need of components) - Go to the "Work Orders" tab and create 2 operations: op1 and op2 - Confirm the MO - Start the operation waiting for an other WO (op2) - Create a third operation: op3 - Save #### > Validation Error: You cannot create a cyclic dependency. ### Cause of the Issue: During the creation of op3, all the workorders of our MO will be confirmed to ensures that the links of the 3 operations are correctly made: https://github.com/odoo/odoo/blob/d2ce6622f2d6f1917dc319112a688e35a73c2088/addons/mrp/models/mrp_workorder.py#L469-L474 This will trigger a call of the `_link_workorders_and_moves` to re-link them all. However, during this call since op2 has been started the order of the workorders will be op2 > op1 rather than op1 > op2 and sincethe MO has no bom nor `operation_id` the records will not be reordered correctly before being linked: https://github.com/odoo/odoo/blob/d2ce6622f2d6f1917dc319112a688e35a73c2088/addons/mrp/models/mrp_production.py#L1472-L1473 https://github.com/odoo/odoo/blob/d2ce6622f2d6f1917dc319112a688e35a73c2088/addons/mrp/models/mrp_production.py#L1485-L1487 This will create a loop on the m2m dependency since op1 will be blocked by op2 and op2 is already blocked by op1. This is detected by the framework which raises the error. opw-4105603 X-original-commit: dda575f8c9fcdfcb3a1a72429d5c05ede86a7c4e
The barcode app now uses text buttons instead of relying on icons alone, making actions easier for users to understand. Related manufacturing and self-order kiosk dialogs were also adjusted for a more consistent, centered presentation.
Original PR description
*: mrp_workorder, pos_self_order_iot This commit aims to add more text to the UI of the barcode app, in case users don't know the meaning of the illustrations. A text is shown in a button now instead. For the IOT module, the template has been tweaked, to allow visual consistency with the Install Kiosk action dialog. Titles are centered horizontally. task-4160938