Daily updates from Odoo
Tuesday, September 24, 2024
8 changes · master
Resolved issues and error corrections
Uploading vendor bills with OCR now correctly completes the automatic posting step after the bill details are refreshed. This prevents bills from being incorrectly treated as manually changed, reducing follow-up work and keeping invoice processing smoother.
Original PR description
When uploading a bill and using the OCR, autoposting of the bill is broken. This is because when clicking the "Refresh" button, the OCR updates the values of the bill therefore `is_manually_modified` is set to `True`. Adding the context key `is_manually_modified` to the `_check_ocr_status` fixes this. Also, after filling all fields with the OCR, we now automatically post the bill using the helper method `_autopost_bill` of `account.move`. task-id: none Community PR: https://github.com/odoo/odoo/pull/180184
Approval rules now better distinguish directly assigned approvers from people added through delegation, preventing delegated approvals from unintentionally replacing or expiring the original approver list. Notifications and tracking around approval groups, approver changes, and kanban delegation are also clearer, helping teams manage approval responsibilities with more confidence.
The financial budget menu item is no longer limited to debug mode, making it available through the normal interface as intended. This fixes an unnecessary access restriction that could prevent business users from finding budgeting options.
Original PR description
The aim of this commit is removing the debug mode on the financial budget menu item. It was introduced by this commit [[1]], and finally we don't want that. no task id [1]: https://github.com/odoo/enterprise/commit/d96b46bc9d17e279c5d4094270c61e610e09ef36
The room booking page has been corrected so it once again fills the available vertical space. This improves the user experience by preventing the page from appearing visually constrained or incorrectly sized.
Original PR description
Purpose: -------- Currently, the room frontend view no longer occupies the full vertical space of the page. This issue was introduced by [1]. To fix this issue, the wrapper element (`div#wrapwrap`) is removed from the room frontend view. This simplifies the DOM structure and allows the main container to take the full available space. [1]: https://github.com/odoo/odoo/pull/98429 Task-4207291
Point of Sale sessions in Belgium now always load the special products needed for enabled features such as tips or discounts, even when a database has more than 20,000 products. This prevents missing functionality during session startup for large product catalogs.
Original PR description
Steps to reproduce : -------------------------- - Install point_of_sale - Enable some special functionalities (ex. tip, discount etc) - Open session with lots of products. (More than loading limit 20,000) Issue : --------- Sometimes the special products required to smoothly run all functionalities enabled are not loaded. Cause : ---------- We have set a limit of 20,000 and if the special product is not in those products it won't be loaded. Fix : ----- Now we ensured that all special products must be loaded without the interference of the products loading limit and no need to apply domain on those 20,000 products so removed _get_available_product_domain() function. Related PR: https://github.com/odoo/odoo/pull/175796 task: 4072726
Field Service mobile task views now better preserve navigation context, so users can move between tasks and return from signed reports without losing the correct menus or simplified layout. The update also keeps the project field hidden when only one Field Service project exists and clarifies the phone field on mobile.
Original PR description
## [FIX] industry_fsm: hide project in form view if only 1 fsm project exists Before this commit, the project in the form view is no longer hidden in mobile in My Tasks of Field Services due to some…
## [FIX] industry_fsm: hide project in form view if only 1 fsm project exists
Before this commit, the project in the form view is no longer hidden in
mobile in My Tasks of Field Services due to some changes in the form
view of tasks.
This commit updates the form view to make sure to project field is
correctly hidden in mobile when there is only one fsm project.
This commit also adds a placeholder to partner_phone to make sure the
user knows which field it is in mobile view since its label is not
displayed in mobile view.
## [IMP] industry_fsm{_report}: make sure to keep the right context for pager
Before this commit, when the user is in mobile and go to field service
app and click on a task in the kanban view, he cannot use the pager in
the form view, because a new action is called and the action does not
have the active_ids, that is the records displayed in the kanban view.
This commit makes sure the action called to open a simplified form view
in mobile get the active_ids to be able to use the pager.
## [FIX] industry_fsm: make sure to go to backend with the right action
Before this commit, when the user goes to fsm task, start a timer and
stop it and then sign report. The user will go to the portal view, if he
clicks on the button to go back to the backend view, he first no longer
have tags, SO, project, ... fields hidden if he was in mobile view.
Second, he has no longer the different menus available in the mobile dashboard
or the menu bar in desktop.
This commit makes sure to load the main action to correctly get the
different menu in FSM when the user goes back to the backend view.
task-4189791When creating a field service task, users now receive a warning if the assigned person is unavailable during the selected dates. This helps planners avoid assigning work to people who are on leave, matching the behavior already available in the planning app.
Original PR description
Steps to reproduce: 1- Field service app > planning by user 2- Open form to create a new task 3- Choose a user and dates where the user is off => No warning displayed like in planning app Source: On creation, self.user_ids = res.users(<NewId origin=1>,). Accessing self.user_ids.employee_id returns empty record Solution: Accessing self.user_ids._origin.employee_id task-3965161
A tax report could fail because one value was handled in the wrong format during calculation. The fix ensures the value is converted correctly so the report can complete as expected.
Original PR description
We were trying to divide a float by a string. We make sure that the string `net_value` is converted to a float.