Daily updates from Odoo
Wednesday, May 14, 2025
33 changes · master
Enhancements to existing features
The underlying evaluation logic used by payroll calculations has been simplified to remove outdated options and make behavior more predictable. This reduces confusion for developers maintaining payroll rules while keeping business functionality unchanged.
Original PR description
This PR simplifies `safe_eval` which, up until now, allowed passing global and local namespaces. There is no usecase for this anymore. We want safe_eval exec mode to begave like a top-level module scope. `nocopy` is not needed anymore either. It's a relic of when the context could be dynamic (e.g. for already deleted `RecordDictWrapper` or `QWebContext`). Passed in context is always a dict. It will always be mutated with the local eval namespace dict after evaluation. This all makes `safe_eval` API less confusing. See: odoo/odoo#206846 See: odoo/upgrade-util#265 task-4378806
Financial report formulas can now round values more flexibly, including to tens or hundreds and with selectable rounding methods. Conditional report calculations also handle zero values correctly, helping avoid inaccurate results when checking thresholds.
Original PR description
==== Improve the round() subformula of the aggregation engine in two ways: Add support for negative precision, similarly to how python's round() works. Providing a negative precision will round to…
==== Improve the round() subformula of the aggregation engine in two ways: Add support for negative precision, similarly to how python's round() works. Providing a negative precision will round to the nearest 10/100/... Also add support for providing the rounding method, defaulting to 'HALF-DOWN' similarly to how it works today. These options can be mixed together to increase by a lot the rounding possibilities. ==== Take the use case of three expressions: A: simple expression with a result of 2500 B: simple expression with a result of 0 C: aggregation for which we want to get the value of A only if B is below 50 This will not work, because _aggregation_apply_bounds will return the unbound_value and cast it to a bool then int to get the multiplier. If the unbound value is 0, it will set the result to 0 even though 0 is indeed below 50. We now return "None" from _aggregation_apply_bounds when the value is out of bound instead of 0, to remove any possible confusion.
Menu syncing for UrbanPiper point-of-sale integrations now uses only active option values, reducing the chance of sync errors caused by outdated or inactive product options. This should make menu updates more reliable while simplifying the underlying process.
Original PR description
Before this commit: === - Iterated over each product and its attribute lines to fetch product template attribute values (PTAVs). - Risk of expected singleton error when multiple PTAVs (active/inactive) existed. After this commit: === - Fetch only active PTAVs directly using a filtered search. -Simplified the loop and removed redundant product-option search.
This update lets Odoo’s read-only route logic use values captured directly from the web address, such as an ID or keyword in the URL. It avoids duplicate processing and makes route behavior more accurate for document-related pages.
Original PR description
The signature of `collable` inside `@route(readonly=callable)` was:
class ...(http.Controller):
def callable(self) -> bool:
...
It was possible to access the path, query-string and body via the globalish `request` object:
request.httprequest.path
request.httprequest.args
request.httprequest.get_data()
But it was not possible up to this point to get the parameters extracted from the path.
Take for example the following endpoint:
@route('/endpoint/<word>', readonly=callable)
def endpoint(self, word):
....
The `callable` function has no way to get `word` unless we match the endpoint again.
With this PR we change the definition of those readonly callable once again, this time to include:
- `rule`: the endpoint that was matched along with its `routing` dictionnary (the `@route` extracted informations)
- `args`: a dict containing the arguments extracted from the path.
task-4572591Colombian withholding reports have been reorganized to show clearer descriptions, better grouping, and an added concept column for ICA reports. This makes Fuente and ICA reporting easier to review and helps ensure report figures are based on the correct local tax codes.
Original PR description
- Adding 'concepto' column to ICA reports, using automatically filled account_move_line.name for it. - Applying proper grouping descriptions for Fuente reports by tax type rather than accounts. - Adjusting withholding tax domains to be by l10n-specific codes rather than account used. - Separating Fuente and ICA in cert~templates.xml because there is no reason for them to be confusingly together. - Adjusting 'if bimestre' and 'if account' logic to 'if expanded' to properly reflect what it is doing and apply to the new columns as well. - Adjusting how empty columns are handled to allow labels to correctly show up when not expanded. - Adding tests for the adjusted reports. task-4315210
Resolved issues and error corrections
This update aligns Odoo’s spreadsheet features with the latest spreadsheet engine release. It restores the ability to insert cells in pivot tables and moves shared chart options so dashboards can use them more consistently.
Original PR description
See https://github.com/odoo/odoo/pull/209731
This fixes two IoT-related actions that were still using an outdated internal message name after a recent change. It helps ensure self-order kiosks open correctly and delivery labels can be printed without interruption.
Original PR description
In commit 313bde6, the `_send_message` method was renamed to `send_message`, but not all of its usages were updated. This commit fixes the remaining usages (opening kiosk and printing delivery labels).
Code cleanup and technical improvements
This update streamlines internal AI agent code by removing inputs that the system can already determine automatically. It reduces maintenance complexity without changing the visible user experience.
Original PR description
Some method args can be removed because they can be inferred from `self` and its field values like the `topic_ids`.
Point of Sale order synchronization was streamlined so updates can be shared in real time with less duplicate processing. This should make related flows such as preparation displays, self-ordering, receipts, and local invoicing integrations more reliable and easier to maintain.
Original PR description
task- 4766757
Miscellaneous changes
During uninstall, fields (columns) bound to the module get deleted first, so the columns used for the search don't exist anymore and the search fails, which leads to the tables not being properly dropped, which can then lead to the module reinstallation not being clean e.g. because there are rows left in the table which can lead to constraints not being addable on install. This has been the cause of `resource` failing forever in the uninstall nightly test: it's most likely been failing since
Original PR description
During uninstall, fields (columns) bound to the module get deleted first, so the columns used for the search don't exist anymore and the search fails, which leads to the tables not being properly dropped, which can then lead to the module reinstallation not being clean e.g. because there are rows left in the table which can lead to constraints not being addable on install. This has been the cause of `resource` failing forever in the uninstall nightly test: it's most likely been failing since this hook was introduced. Forward-Port-Of: odoo/enterprise#85439
Description ------------ For non-admin users, loading the default kanban view of the Appointment application triggers the compute method `_compute_appointment_counts`. This is quite slow as it calls an override of `_read_group`, which adds an elaborate domain for privacy in `_get_default_privacy_domain`. This patch optimizes domains to generate more efficient queries by: - Simplifying useless sub-queries of the form `fkey in (select id from comodel where id = X)` to `fkey in (X)` where
Original PR description
Description ------------ For non-admin users, loading the default kanban view of the Appointment application triggers the compute method `_compute_appointment_counts`. This is quite slow as it calls an override of `_read_group`, which adds an elaborate domain for privacy in `_get_default_privacy_domain`. This patch optimizes domains to generate more efficient queries by: - Simplifying useless sub-queries of the form `fkey in (select id from comodel where id = X)` to `fkey in (X)` where it makes sense (in `sudo` context) - Adding supporting indexes Benchmark ---------- On odoo.com, the time for a regular user to open the default kanban view of appointments is: | Before (hot) | After (hot) | Speedup | |--------------|-------------|---------| | 11s | 1.2s | 9.2x | Reference --------- task-4744275 Community PR: https://github.com/odoo/odoo/pull/207015 Forward-Port-Of: odoo/enterprise#85401 Forward-Port-Of: odoo/enterprise#83916
Version: - saas-18.3 Steps to reproduce: - Add one template. - Add two signer. - Try to send/sign now template Issue: - The second signer (the one added last) doesn't appear in the signing wizard. Cause: - The saveBeforeAction() function calls signStatus.save(), which tries to save multiple document iframes at once but doesn't wait for all of them to finish saving. Solution: - Modify the save() method to return a Promise that resolves only after all Document saves are complete
Original PR description
Version: - saas-18.3 Steps to reproduce: - Add one template. - Add two signer. - Try to send/sign now template Issue: - The second signer (the one added last) doesn't appear in the signing wizard. Cause: - The saveBeforeAction() function calls signStatus.save(), which tries to save multiple document iframes at once but doesn't wait for all of them to finish saving. Solution: - Modify the save() method to return a Promise that resolves only after all Document saves are complete. Forward-Port-Of: odoo/enterprise#85367
Steps to reproduce: === - Install the pos_urban_piper module. - Configure UrbanPiper credentials. - Place a test order. - Open the preparation display. - The display remains blank, and a Traceback occurred. Issue: === - Traceback or incorrect behavior while accessing delivery information. - Duration countdown is not working properly. - Some UI issues due to missing field references. Cause: === - Preparation display was revamped (https://github.com/odoo/odoo/pull/201170, https:/
Original PR description
Steps to reproduce: === - Install the pos_urban_piper module. - Configure UrbanPiper credentials. - Place a test order. - Open the preparation display. - The display remains blank, and a Traceback occurred. Issue: === - Traceback or incorrect behavior while accessing delivery information. - Duration countdown is not working properly. - Some UI issues due to missing field references. Cause: === - Preparation display was revamped (https://github.com/odoo/odoo/pull/201170, https://github.com/odoo/enterprise/pull/78493). - preparationDisplay renamed to prepDisplay. - Wrong field access in delivery information. Fix: === - Updated preparationDisplay to prepDisplay. - Fixed condition to properly show scheduled delivery time. task-4755595 Forward-Port-Of: odoo/enterprise#84256
Commit odoo/odoo@abd909498e4fd relaxed the multi-company rule for hr.employee (more records are visible). Instead the action domains were updated to include the restricted company rules (see only from your company) The domains in the Employee dashboard was not updated though. It means the dashboard takes into account employees from other companies (as allowed by the ir.rule) opw-4777122 Forward-Port-Of: odoo/enterprise#85212 Forward-Port-Of: odoo/enterprise#84972
Original PR description
Commit odoo/odoo@abd909498e4fd relaxed the multi-company rule for hr.employee (more records are visible). Instead the action domains were updated to include the restricted company rules (see only from your company) The domains in the Employee dashboard was not updated though. It means the dashboard takes into account employees from other companies (as allowed by the ir.rule) opw-4777122 Forward-Port-Of: odoo/enterprise#85212 Forward-Port-Of: odoo/enterprise#84972
…queryCount Extra query made by the tax engine to retrieve the country from the company. Forward-Port-Of: odoo/enterprise#85315 Forward-Port-Of: odoo/enterprise#85092
Original PR description
…queryCount Extra query made by the tax engine to retrieve the country from the company. Forward-Port-Of: odoo/enterprise#85315 Forward-Port-Of: odoo/enterprise#85092
Beofre this commit: Products with both positive and negative sales order lines in SO can result it total quantity = 0 when calcuating average cost. Causing division by zero error. After this commit: Added a check to prevent division if total quantity of product is zero. Negative order lines are usually used for return of product, it is not included in shipping request. opw-4655713 Forward-Port-Of: odoo/enterprise#84201 Forward-Port-Of: odoo/enterprise#83500
Original PR description
Beofre this commit: Products with both positive and negative sales order lines in SO can result it total quantity = 0 when calcuating average cost. Causing division by zero error. After this commit: Added a check to prevent division if total quantity of product is zero. Negative order lines are usually used for return of product, it is not included in shipping request. opw-4655713 Forward-Port-Of: odoo/enterprise#84201 Forward-Port-Of: odoo/enterprise#83500
Before this commit, the test_automatic_invoice_token test would fail with the following traceback: FAIL: TestSubscriptionController.test_automatic_invoice_token Traceback (most recent call last): File "/data/build/enterprise/sale_subscription/tests/test_subscription_controller.py", line 157, in test_automatic_invoice_token subscription = self._portal_payment_controller_flow() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/data/build/enterprise/s
Original PR description
Before this commit, the test_automatic_invoice_token test would fail with the following traceback: FAIL: TestSubscriptionController.test_automatic_invoice_token Traceback (most recent call last):…
Before this commit, the test_automatic_invoice_token test would fail
with the following traceback:
FAIL: TestSubscriptionController.test_automatic_invoice_token
Traceback (most recent call last):
File "/data/build/enterprise/sale_subscription/tests/test_subscription_controller.py", line 157, in test_automatic_invoice_token
subscription = self._portal_payment_controller_flow()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/data/build/enterprise/sale_subscription/tests/test_subscription_controller.py", line 235, in _portal_payment_controller_flow
self.assertEqual(subscription.invoice_ids.sorted('id').mapped('state'), ['posted'])
AssertionError: Lists differ: ['posted', 'posted'] != ['posted']
First list contains 1 additional elements.
First extra element 1:
'posted'
- ['posted', 'posted']
+ ['posted']
The issue was detected when the test was running on the last day of the
month.
When we were not on the last day of the month, in the controller /my/subscriptions/<int:order_id>/transaction
invoice_to_pay was None because there was only once invoice already paid.
As a result, amount_to_invoice was 0.0 in this code:
amount_to_invoice = invoice_to_pay.amount_total if invoice_to_pay else order_sudo.amount_to_invoice
a tx with an amount equal to 0 would be created in the controller and
in payment_transaction.py, during the postprocess, a "partially paid tx" would be found as the amount would not match (2.3 and 0.0).
We prefer to fix the test by making sure an amount is set in the parameters of the controller. It will make the flow more coherent and realistic.
\# Explanation
When /my/subscriptions/<int:order_id>/transaction was called the second
time in the test, no amount kwarg was provided. As a result the
following line would be called in the controller:
amount_to_invoice = invoice_to_pay.amount_total if invoice_to_pay else order_sudo.amount_to_invoice
invoice_to_pay is always None and therefore the amount_to_invoice is
equal to order_sudo.amount_to_invoice
When we look,at _compute_amount_to_invoice, we have:
is_invoice_due = (
not order.last_invoice_date
or (order.next_invoice_date <= today and order.last_invoice_date <= today)
)
if not is_invoice_due:
line.amount_to_invoice = 0.0
continue
We will compare when the code run on the 30th of march or on the 31th of
march.
\## 30th of March
next invoice date is 2025-04-30
start date is 2025-03-30
last_invoice_date is 2025-03-30
next_invoice_date <= today is False
last_invoice_date <= today is True
is_invoice_due = (
not order.last_invoice_date
or (order.next_invoice_date <= today and order.last_invoice_date <= today)
)
Therefore is_invoice_due is False and we enter the condition and set the amount_to_invoice equal to 0.0
\## 31th of March
next invoice date is 2025-04-30
start date is 2025-03-31
last_invoice_date is False
next_invoice_date <= today is False (same)
last_invoice_date <= today is False because last_invoice_date is not set
Therefore, is_invoice_due is True and we set amount_to_invoice to the recurring total of the SO.
The issue is occuring because next invoice date is 2025-04-30 in both situations !
2025-03-30 + relativedelta(months=1) is equal to 2025-03-31 + relativedelta(months=1)
In the definition of last_invoice_date, we compare the next invoice date - billing_period to today:
last_date = order.next_invoice_date and order.plan_id.billing_period and order.next_invoice_date - order.plan_id.billing_period
\# When we start the 30th of March:
\# last_date = 30th of april - 1 month = 30th of march
\# When we start the 31th of March:
\# last_date keep the same value because the next_invoice_date is the
same.
start_date = order.start_date or fields.Date.today()
if order.state == 'sale' and last_date and last_date >= start_date:
order.last_invoice_date = last_date <-- 30th of March >= 30th of March (today when we start on the 30th
else:
order.last_invoice_date = False <-- 30th of March is not larger than 31th of March (today when we start on the 31th)
runbot error: 162144
Forward-Port-Of: odoo/enterprise#84542Fixed the following issues in the SLSP reports: ~~When filters "Including Partners Without TIN" and "Including Importations" are updated, the lines are not refreshed~~ ~~When the filters above are updated, the name of the current active filters are not refreshed~~ - When "Including Partners Without TIN" is enabled, the grand total does not consider lines from those partners - When exported, amounts from the previous row are carried forward to the current row, if the current row has no
Original PR description
Fixed the following issues in the SLSP reports: ~~When filters "Including Partners Without TIN" and "Including Importations" are updated, the lines are not refreshed~~ ~~When the filters above are updated, the name of the current active filters are not refreshed~~ - When "Including Partners Without TIN" is enabled, the grand total does not consider lines from those partners - When exported, amounts from the previous row are carried forward to the current row, if the current row has no value for that amount 4748216 Forward-Port-Of: odoo/enterprise#85336 Forward-Port-Of: odoo/enterprise#85249
**issue:** When a task with an allocated time > 0.0 but no timesheets is created in a shared project (with edit rights), the portal user incorrectly sees 0.0 as the allocated time. **Steps to reproduce:** - Ensure the sale_timesheet module is installed. - Create a new project. - Create a task with allocated time and no timesheets. - Share the project with a portal user (edit permission). In the portal user's kanban view, the allocated time of the task is displayed as 0.0 instead o
Original PR description
**issue:** When a task with an allocated time > 0.0 but no timesheets is created in a shared project (with edit rights), the portal user incorrectly sees 0.0 as the allocated time. **Steps to reproduce:** - Ensure the sale_timesheet module is installed. - Create a new project. - Create a task with allocated time and no timesheets. - Share the project with a portal user (edit permission). In the portal user's kanban view, the allocated time of the task is displayed as 0.0 instead of the correct allocated time. opw-4582705 Forward-Port-Of: odoo/enterprise#84706 Forward-Port-Of: odoo/enterprise#82171
After this commit, the orders that have a preset_time and that are to be prepared for the same day will only be shown if the preset_time is lower than next time slot. related: https://github.com/odoo/odoo/pull/208975 task-4725279 Forward-Port-Of: odoo/enterprise#84957
Original PR description
After this commit, the orders that have a preset_time and that are to be prepared for the same day will only be shown if the preset_time is lower than next time slot. related: https://github.com/odoo/odoo/pull/208975 task-4725279 Forward-Port-Of: odoo/enterprise#84957
Steps to reproduce the bug: - Create a quality point with the following settings: - Measure on: Operation - Picking Type: Manufacturing - Product Category: "All" - Create a storable product “P1”: - Product Category: "All" - BoM: - components: - 1 unit of P1 - Create a manufacturing order to produce one unit of P1 - Confirm it Problem: The manufacturing order is confirmed, but the corresponding quality check is not created. This issue occurs when a quality
Original PR description
Steps to reproduce the bug: - Create a quality point with the following settings: - Measure on: Operation - Picking Type: Manufacturing - Product Category: "All" - Create a storable product “P1”: -…
Steps to reproduce the bug:
- Create a quality point with the following settings:
- Measure on: Operation
- Picking Type: Manufacturing
- Product Category: "All"
- Create a storable product “P1”:
- Product Category: "All"
- BoM: - components: - 1 unit of P1
- Create a manufacturing order to produce one unit of P1
- Confirm it
Problem:
The manufacturing order is confirmed, but the corresponding quality check is not created.
This issue occurs when a quality point is configured with "Measure on:
Operation". In that case, the quality check should be created for
manufacturing orders here:
https://github.com/odoo/enterprise/blob/18.0/quality_mrp/models/stock_move.py#L49-L51
However, an empty record is passed for the product parameter.
As a result, the domain defined here:
https://github.com/odoo/enterprise/blob/18.0/quality_mrp/models/stock_move.py#L19-L21
is evaluated with both product and category set to False, which
prevents the created quality point from being matched and thus no
quality check is created.
https://github.com/odoo/enterprise/blob/6ee3472937118e758399a9577251efad8c4c1195/quality_control/models/quality.py#L175-L177
opw-4762914
Forward-Port-Of: odoo/enterprise#85186
Forward-Port-Of: odoo/enterprise#84683To ease multi-company usage, we introduce the company_id field on insurance views since one insurance per company has to be created Forward-Port-Of: odoo/enterprise#85238 Forward-Port-Of: odoo/enterprise#84968
Original PR description
To ease multi-company usage, we introduce the company_id field on insurance views since one insurance per company has to be created Forward-Port-Of: odoo/enterprise#85238 Forward-Port-Of: odoo/enterprise#84968
If the user deleted some leave types, the payroll app will not be able to function anymore, in this PR we fallback and only browse for the ones that were not deleted Forward-Port-Of: odoo/enterprise#85237 Forward-Port-Of: odoo/enterprise#85119
Original PR description
If the user deleted some leave types, the payroll app will not be able to function anymore, in this PR we fallback and only browse for the ones that were not deleted Forward-Port-Of: odoo/enterprise#85237 Forward-Port-Of: odoo/enterprise#85119
- This fix backport some of the changes made in the `master` PR (https://github.com/odoo/enterprise/pull/80267) to the `saas-18.2 branch`. - Multiples issues were appearing when invoicing a POS order containing settling lines. In this fix we put the quantity of the settling lines to 0 before sending it to the backend (as it's done in `master`), that way when invoicing the settling order it just act as a note and does not create a new debt. - When paying an order with customer account and gener
Original PR description
- This fix backport some of the changes made in the `master` PR (https://github.com/odoo/enterprise/pull/80267) to the `saas-18.2 branch`. - Multiples issues were appearing when invoicing a POS order…
- This fix backport some of the changes made in the `master` PR (https://github.com/odoo/enterprise/pull/80267) to the `saas-18.2 branch`. - Multiples issues were appearing when invoicing a POS order containing settling lines. In this fix we put the quantity of the settling lines to 0 before sending it to the backend (as it's done in `master`), that way when invoicing the settling order it just act as a note and does not create a new debt. - When paying an order with customer account and generating an invoice from PoS, now we can pay (partially or not) the invoice from the backend, and it will be reflected in the PoS (as it's done in `master`). First issue to reproduce (settle order with invoicing): - Open PoS - Select a customer - Pay a product with customer account - Open customer popup and search for this customer (he should have a debt based on the previous amount) - Settle the due account - Click "Payment" - Enable "invoice" - Pay with card - => Open customer popup and look for this customer again, he still have a debt Second issue to reproduce (paying invoice from backend): - Open PoS - Select a customer - Pay a product with customer account - Open customer popup and search for this customer (he should have a debt based on the previous amount) - Close PoS session - Open the backend and go to the customer invoice - Open the invoice and pay it half of the amount - Go back to PoS and open the customer popup - Search for this customer and click settle due accounts - The amount due from the PoS order is not the same (the amount paid from the backend is not reflected in the PoS) task-id: 4751971 community PR: https://github.com/odoo/odoo/pull/207444 Forward-Port-Of: odoo/enterprise#84622 Forward-Port-Of: odoo/enterprise#84117
**Steps To Reproduce:** - Go to accounting -> reconcile. - Select 1 or 2 entries and try to reconcile. **Issue:** - By clicking on the reconcile button, a traceback occurs. **Cause:** - In the new bank reconciliation widget, the field "counterpart_type" is removed from the 'account.reconciliation.model' ([Ref](https://github.com/odoo/odoo/pull/203327/files#diff-c217a13a40a3cc27dc516b899793abecfac8cab9a42fed407d4776bcbc9de9a8L180 )), but it is not removed from one domain, w
Original PR description
**Steps To Reproduce:** - Go to accounting -> reconcile. - Select 1 or 2 entries and try to reconcile. **Issue:** - By clicking on the reconcile button, a traceback occurs. **Cause:** - In the new bank reconciliation widget, the field "counterpart_type" is removed from the 'account.reconciliation.model' ([Ref](https://github.com/odoo/odoo/pull/203327/files#diff-c217a13a40a3cc27dc516b899793abecfac8cab9a42fed407d4776bcbc9de9a8L180 )), but it is not removed from one domain, which causes the traceback. - **Solution:** - The fields which is removed from the 'account.reconciliation.model', is removed from the domain. Task-4784111 Forward-Port-Of: odoo/enterprise#85351
… for On a virgin DB Go to renting => product Enter studio The kanban of product.template triggers an onchange to get default values Before this commit there was a crash due to a bug in the ORM: the compute of the display_price field did not compute the currency_id id correctly. task to solve the ORM bug: 4264573 solving PR: https://github.com/odoo/odoo/pull/165930 runbot-error-161799 Forward-Port-Of: odoo/enterprise#85359
Original PR description
… for On a virgin DB Go to renting => product Enter studio The kanban of product.template triggers an onchange to get default values Before this commit there was a crash due to a bug in the ORM: the compute of the display_price field did not compute the currency_id id correctly. task to solve the ORM bug: 4264573 solving PR: https://github.com/odoo/odoo/pull/165930 runbot-error-161799 Forward-Port-Of: odoo/enterprise#85359
Steps: - install `web_studio` and `documents_spreadsheet` - open documents - open studio on the spreadsheet kanban view (the default one) - change sort by field to "created on" field - error This commit replaces encodeURIComponent with window.encodeURIComponent, because owl won't try to evaluate this variable via the context. And so the fix ```js get renderingContext() { const context = super.renderingContext; context.encodeURIComponent = encodeURIComponent;
Original PR description
Steps:
- install `web_studio` and `documents_spreadsheet`
- open documents
- open studio on the spreadsheet kanban view (the default one)
- change sort by field to "created on" field
- error
This commit replaces encodeURIComponent with window.encodeURIComponent,
because owl won't try to evaluate this variable via the context.
And so the fix
```js
get renderingContext() {
const context = super.renderingContext;
context.encodeURIComponent = encodeURIComponent;
...
}
```
In `DocumentsKanbanRecord` is no longer necessary.
The error occurred because `encodeURIComponent` was not found in the context object.
The reason this fix doesn't work with studio is the view is defined as
```xml
<kanban js_class="documents_kanban"/>
```
and studio does not load view js classes.
And since the fix is in `documents_kanban`, it's not taken into account. opw-4744886
Forward-Port-Of: odoo/enterprise#84411Add in missing modules to tx/config where their pots were auto-added by the pot export sync. Forward-Port-Of: odoo/enterprise#85480
Original PR description
Add in missing modules to tx/config where their pots were auto-added by the pot export sync. Forward-Port-Of: odoo/enterprise#85480
Steps to reproduce: - Activate foreign currency EUR (main company in USD) - Have a Bank journal in EUR - Create one Vendor "Send" payment of 100 EUR - Create a new Vendor batch payment and add the payment. - Open EUR Bank and register an outgoing transaction of 100 EUR - Match the transaction with the Batch payment Issue: Looking at the debit/credit columns it can be seen that the transaction amount is properly converted in company currency, but the batch amount is not converted (rate
Original PR description
Steps to reproduce: - Activate foreign currency EUR (main company in USD) - Have a Bank journal in EUR - Create one Vendor "Send" payment of 100 EUR - Create a new Vendor batch payment and add the payment. - Open EUR Bank and register an outgoing transaction of 100 EUR - Match the transaction with the Batch payment Issue: Looking at the debit/credit columns it can be seen that the transaction amount is properly converted in company currency, but the batch amount is not converted (rate 1.00) This occurs because when the payments in a batch don't have an associated move, the amount residual is converted from payment currency (EUR) to batch currency (still EUR) and not company currency (USD) opw-4656807 Forward-Port-Of: odoo/enterprise#85015 Forward-Port-Of: odoo/enterprise#83632
This PR updates and improves the AI / ChatGPT integration that already existed in odoo for messages and HTML fields. Now instead of a dedicated dialog, that covers the whole screen, the AI chat is integrated with discuss so users can talk with the AI bot as if they were talking with another user. Apart from the visual change, the functionality of the AI was also improved. Now, when the AI is prompted, a JSON with the record's information available to the current user is given to the AI con
Original PR description
This PR updates and improves the AI / ChatGPT integration that already existed in odoo for messages and HTML fields. Now instead of a dedicated dialog, that covers the whole screen, the AI chat is…
This PR updates and improves the AI / ChatGPT integration that already existed in odoo for messages and HTML fields. Now instead of a dedicated dialog, that covers the whole screen, the AI chat is integrated with discuss so users can talk with the AI bot as if they were talking with another user. Apart from the visual change, the functionality of the AI was also improved. Now, when the AI is prompted, a JSON with the record's information available to the current user is given to the AI context in order for the AI to generate more relevant text. If the context requires it (when composing messages/notes) we also input a list of all messages/notes from the chatter in the context, so the AI can take previous conversations about a record into account. When using the AI to improve a piece of text through text selection, no record information is shared. Also a new way to call the AI is added from the top of the chatter. From there, users can ask for a summary of the chatter conversation as well as generate messages and notes directly. A new app is added to change the ai pre-prompts configurations. A new module ai_apps was added to add all the above features. Also some bridge modules were created and some code was moved in order to loosen the dependencies between ai_apps and other modules, making the AI app fully deletable. Previous PR that targetted master: https://github.com/odoo/enterprise/pull/83428 task-4526290 Forward-Port-Of: odoo/enterprise#84868
The Issue: Prior to this commit, retrieving the amount currency from the transaction details caused a traceback. This occurred because the transaction details are stored as a jsonb object, and the code attempted to access a string within a dictionary, resulting in a TypeError mismatch. The Fix: The jsonb object is now converted to a string before processing. Additionally, an IndexError is caught to handle cases where the expected group is not found in the match. opw-4754518 Forward-Port
Original PR description
The Issue: Prior to this commit, retrieving the amount currency from the transaction details caused a traceback. This occurred because the transaction details are stored as a jsonb object, and the code attempted to access a string within a dictionary, resulting in a TypeError mismatch. The Fix: The jsonb object is now converted to a string before processing. Additionally, an IndexError is caught to handle cases where the expected group is not found in the match. opw-4754518 Forward-Port-Of: odoo/enterprise#84769
### Steps to reproduce: - Create an employee with flexible schedule with 8 hours per day - Navigate to Attendance app -> Gantt View - Check the progress bar for the flexible employee - Notice the progress bar will show X/11 ### Cause: This is happening as when calculating the maximum value for the employee's working hours we are adding a day to the date range https://github.com/odoo/enterprise/blob/2da6836520c4e7760e57062e3e97a22b744baacf/hr_attendance_gantt/models/hr_attendance.py#L
Original PR description
### Steps to reproduce: - Create an employee with flexible schedule with 8 hours per day - Navigate to Attendance app -> Gantt View - Check the progress bar for the flexible employee - Notice the progress bar will show X/11 ### Cause: This is happening as when calculating the maximum value for the employee's working hours we are adding a day to the date range https://github.com/odoo/enterprise/blob/2da6836520c4e7760e57062e3e97a22b744baacf/hr_attendance_gantt/models/hr_attendance.py#L47 ### Fix: We don't need to add this extra day as already the difference between the start and stop is relfecting the correct number of days opw-4680513 Forward-Port-Of: odoo/enterprise#84250
Steps to reproduce: 1. Go to documents 2. Try to mark your favourite document 3. It will ghost you. Technical Reason: Used record.load() as value was not updating instantly in the UI. 'this.props.record.data[this.props.name] = result' fetched correct value, but didn’t trigger re-render. After this commit: favorite icon state updates instantly. Task-4766725 Forward-Port-Of: odoo/enterprise#84666
Original PR description
Steps to reproduce: 1. Go to documents 2. Try to mark your favourite document 3. It will ghost you. Technical Reason: Used record.load() as value was not updating instantly in the UI. 'this.props.record.data[this.props.name] = result' fetched correct value, but didn’t trigger re-render. After this commit: favorite icon state updates instantly. Task-4766725 Forward-Port-Of: odoo/enterprise#84666