Daily updates from Odoo
Wednesday, March 8, 2023
10 changes · master
Enhancements to existing features
Users viewing Argentine VAT report details now see a purpose-built form instead of a generic system-generated layout. This makes drill-downs from pivot reports clearer and easier to read, improving day-to-day usability without changing the underlying data.
Original PR description
before this commit, there is no form view defined for the model account.ar.vat.line and thus on opening the form view by clicking on the pivot view cells, it is returning an odoo generated view, which is not looking great. after this commit, as form view is defined for the model, clean form view will be shown to the end user.
Resolved issues and error corrections
A small issue in the Website Knowledge feature was corrected after an earlier internal update changed how field information is passed. This helps ensure copy-to-clipboard fields keep working reliably for users.
Original PR description
This commit fixes a bug introduced by a change in the standardFieldProps changed in [this commit](https://github.com/odoo/odoo/commit/688986f888f2fe2371d58b74ded81315ba6bb353#diff-1aae968392d4816e198af17d114c02b971d75d3634e8330d026fd6c9741feb38) We need to remove the key *value* from the props of the CopyClipboardCharField component, the Component in the template was forgotten when transitioning to the new standardFieldProps. task-3223259
Field Service task search screens now include the same property fields already available in Project task searches. This fixes an inconsistency and helps teams find and filter Field Service tasks using the expected custom property information.
Original PR description
Property fields introduced in the task search views in https://github.com/odoo/odoo/pull/101901 were only appearing in the Project tasks search views. This PR adds them to the Field Service search views too. Community: https://github.com/odoo/odoo/pull/114647
This fixes an unstable automated test for Mexican point-of-sale invoicing by ensuring it selects a paid order only after paid orders are actually loaded. The change reduces false test failures and helps keep delivery checks reliable without changing user-facing behavior.
Original PR description
In the tour `tour_invoice_previous_order`, we create, validate and pay an order. Then, we go to the menu presenting the existing orders. In this menu, we can filter the orders to get only the paid ones. Clicking on one of these filters triggers a fetch to the server and the records are sometimes loaded with a tiny delay.
This delay is causing an indeterminism: since the next step is to select the first order in menu (`div.order-row:first`), we sometimes select the current empty order, because the paid orders have not been loaded yet. Adapting the trigger to select only the first *paid* order solves the issue (`div.order-row:contains('Paid'):first`).
See for instance: https://runbot.odoo.com/runbot/build/24777641Code cleanup and technical improvements
This update removes repeated setup details that Odoo already fills in automatically for many actions. It does not change how users work with the system, but it makes the configuration files cleaner and easier to maintain.
Original PR description
The type fields of actions already defaults to the model name in the base model definition. Therefore, specifying `ir.actions.server`, `ir.actions.act_window` & so on as type is useless (and adds noise since it's the same as the action model). Community PR: https://github.com/odoo/odoo/pull/114539
This change simplifies how the system tracks edited fields in form views by keeping specialized translation logic where it is actually used. It should not change day-to-day behavior for users, but it makes the code easier to maintain and reduces the risk of future issues.
Original PR description
The logic of dirtyTranslatableFields is only needed in one place in the form view. We will therefore remove this function from the model. We'll take the opportunity to replace dirtyFields with isDirtyField because all uses of dirtyFields want to check with the name of a field if it is dirty or not. Part of Task: 3179751
Miscellaneous changes
Steps: - Install indian payroll(l10n_in_hr_payroll) - Create an employee. - Create contract on that employee. - Generate payslip. - Go to employee app > Reprort . - Print the `Hr monthly Employee Salary` or `Employee Yearly Salary`. Issue: - traceback when trying to print report. Cause: - restrict `BaseModel` to assing a variable to reduce memory usage in [1] PR but forget to remove from indian payroll because moving payroll to enterprise and [1] task merged at same time period.
Original PR description
Steps: - Install indian payroll(l10n_in_hr_payroll) - Create an employee. - Create contract on that employee. - Generate payslip. - Go to employee app > Reprort . - Print the `Hr monthly Employee Salary` or `Employee Yearly Salary`. Issue: - traceback when trying to print report. Cause: - restrict `BaseModel` to assing a variable to reduce memory usage in [1] PR but forget to remove from indian payroll because moving payroll to enterprise and [1] task merged at same time period. [1] https://github.com/odoo/odoo/pull/51075 Fix: - deprecate some of the method and move most of the logic to new methods in order to take customisation into account. task-3102201 Forward-Port-Of: odoo/enterprise#35451
When a link is created via the "/Appointment" or "/Calendar" commands inside an existing link (e.g. a button in website), we get nested anchor tags in the DOM as result. This PR avoids such result by changing the existing link's href and content instead of creating a new one in such case. task-3130947 opw-3096108 CE PR: https://github.com/odoo/odoo/pull/112904 Forward-Port-Of: odoo/enterprise#37604 Forward-Port-Of: odoo/enterprise#36839
Original PR description
When a link is created via the "/Appointment" or "/Calendar" commands inside an existing link (e.g. a button in website), we get nested anchor tags in the DOM as result. This PR avoids such result by changing the existing link's href and content instead of creating a new one in such case. task-3130947 opw-3096108 CE PR: https://github.com/odoo/odoo/pull/112904 Forward-Port-Of: odoo/enterprise#37604 Forward-Port-Of: odoo/enterprise#36839
date_close should not be updated when re-opening and closing an appraisal task - 3147639 Forward-Port-Of: odoo/enterprise#37869
Original PR description
date_close should not be updated when re-opening and closing an appraisal task - 3147639 Forward-Port-Of: odoo/enterprise#37869
This commit fixes the typo made in - odoo/enterprise#31305 task - 3193649 Forward-Port-Of: odoo/enterprise#37871 Forward-Port-Of: odoo/enterprise#37272
Original PR description
This commit fixes the typo made in - odoo/enterprise#31305 task - 3193649 Forward-Port-Of: odoo/enterprise#37871 Forward-Port-Of: odoo/enterprise#37272