Wednesday, January 25, 2023
17 changes
Enhancements to existing features
The Amazon sales integration was simplified by removing redundant internal links to sales teams and warehouse locations. This reduces maintenance complexity while preserving the same business behavior by using existing information directly.
Original PR description
There is no need to inherit from crm.teams and stock.location, as the only use of the added fields can easily be retrieved from the original models. task-2883455 See also: - https://github.com/odoo/upgrade/pull/3991
Several app settings screens now use a newer layout that groups options more clearly. This makes configuration areas in project, helpdesk, field service, forecasting, documents, and website helpdesk easier for users and administrators to scan without changing business behavior.
Original PR description
* : documents_project, helpdesk, industry_fsm, industry_fsm_report,
industry_fsm_sale, project_forecast, website_helpdesk
Comunity PR : https://github.com/odoo/odoo/pull/110432Code cleanup and technical improvements
Odoo Studio’s app creation and action editing screens have been modernized behind the scenes. This helps keep Studio easier to maintain and prepares it for smoother future improvements, with limited direct change for day-to-day users.
Miscellaneous changes
- Create an invoice of 2000 - Create another invoice of 2000 - Create a refund of -1000 - Create a statement line of 3000 The statement line's amount matches exactly all 3 invoices. If we add first the 2 customer invoices on the bank reco widget, a partial of 1000 is suggested for the second invoice. When adding the refund, the previous partial is not reset and then, the bank reco widget adds a new auto_balance line to balance debit/credit. Also, make sure the exchange difference lines
Original PR description
- Create an invoice of 2000 - Create another invoice of 2000 - Create a refund of -1000 - Create a statement line of 3000 The statement line's amount matches exactly all 3 invoices. If we add first the 2 customer invoices on the bank reco widget, a partial of 1000 is suggested for the second invoice. When adding the refund, the previous partial is not reset and then, the bank reco widget adds a new auto_balance line to balance debit/credit. Also, make sure the exchange difference lines (exchange_diff) are put right after their corresponding lines (new_aml). task: 3138627 Forward-Port-Of: odoo/enterprise#36091
- Create a reco model that doesn't match anything with auto_validate - Create 21 statement lines - Wait the CRON to process => No cron trigger created to auto-reconcile the 21th line task: 3143478 Forward-Port-Of: odoo/enterprise#36268 Forward-Port-Of: odoo/enterprise#36257
Original PR description
- Create a reco model that doesn't match anything with auto_validate - Create 21 statement lines - Wait the CRON to process => No cron trigger created to auto-reconcile the 21th line task: 3143478 Forward-Port-Of: odoo/enterprise#36268 Forward-Port-Of: odoo/enterprise#36257
Before this commit, if there were accounts with no account group, there were instances where this 'No Group' group would be repeated several times. This was because `render_lines()` can sometimes be called recursively, and each time it was called while 'No Group' was present in the hierarchy, this group would get rendered again. There was also an issue with the `parent_line_id` for those accounts. It should have been `None`, but was instead using some leftover value from a previous iterati
Original PR description
Before this commit, if there were accounts with no account group, there were instances where this 'No Group' group would be repeated several times. This was because `render_lines()` can sometimes be called recursively, and each time it was called while 'No Group' was present in the hierarchy, this group would get rendered again. There was also an issue with the `parent_line_id` for those accounts. It should have been `None`, but was instead using some leftover value from a previous iteration. The test in `account_asset` is also adapted to cover these use cases. opw-3126168 opw-3128706 Forward-Port-Of: odoo/enterprise#35970
stock_move_line create method is currently decorated by `@api.model` in the quality_control module. This means that when creating a batch of smls, the records will be created one by one instead of in batch. Changing `api.model` to `api.model_create_multi` makes the record creation work in batch. #### speedup In a testing DB with one product tracked by Serial Number, confirming a purchase order of 20.000 products goes from 4min40s to 40s. Forward-Port-Of: odoo/enterprise#36214 Forw
Original PR description
stock_move_line create method is currently decorated by `@api.model` in the quality_control module. This means that when creating a batch of smls, the records will be created one by one instead of in batch. Changing `api.model` to `api.model_create_multi` makes the record creation work in batch. #### speedup In a testing DB with one product tracked by Serial Number, confirming a purchase order of 20.000 products goes from 4min40s to 40s. Forward-Port-Of: odoo/enterprise#36214 Forward-Port-Of: odoo/enterprise#24170
Before this commit, while creating a new record, the chatter was disabled and no interaction on chatter was possible until the record was fully created by saving it. This was a problem because it's unclear that chatter requires the record to be fully created. In earlier versions of Odoo, we had to click on "Edit" and "Save" buttons of Form view, but now that edit/read-only mode is no longer explictly managed by the users, they'd expect to be able to interact with chatter, even while in the pr
Original PR description
Before this commit, while creating a new record, the chatter was disabled and no interaction on chatter was possible until the record was fully created by saving it. This was a problem because it's unclear that chatter requires the record to be fully created. In earlier versions of Odoo, we had to click on "Edit" and "Save" buttons of Form view, but now that edit/read-only mode is no longer explictly managed by the users, they'd expect to be able to interact with chatter, even while in the process of creating a new record. With this commit, when clicking on most actions in chatter, the record is created. In case the record cannot be created, usual validation errors are applied. Task-3132931 Community: https://github.com/odoo/odoo/pull/109911 Forward-Port-Of: odoo/enterprise#36130 Forward-Port-Of: odoo/enterprise#36027
Before, when a report contained multiple expressions on a line using a groupby, if multiple figure types were used on these expressions, only the figure type of the last of these expression was used as a default value for grouped lines (this default value is needed for example when grouping by partner, if partner A is obtained from expression 1, but not in the result of expression 2 => expression 2 displays the default value). For example, if expression 1 had figure_type 'none' and expression
Original PR description
Before, when a report contained multiple expressions on a line using a groupby, if multiple figure types were used on these expressions, only the figure type of the last of these expression was used as a default value for grouped lines (this default value is needed for example when grouping by partner, if partner A is obtained from expression 1, but not in the result of expression 2 => expression 2 displays the default value). For example, if expression 1 had figure_type 'none' and expression 2 had 'monetary', expression 1's default value would be '0 $' instead of ''. This was due to bad grouping in the processing of groupby lines expansion. It is now fixed. Forward-Port-Of: odoo/enterprise#36111
Open the kanban view by default when clicking on the journal name. task: 3141127 Forward-Port-Of: odoo/enterprise#36094
Original PR description
Open the kanban view by default when clicking on the journal name. task: 3141127 Forward-Port-Of: odoo/enterprise#36094
Add formula for the total of liabilities in the finnish balance sheet. opw- 2702912 Forward-Port-Of: odoo/enterprise#36248 Forward-Port-Of: odoo/enterprise#35809
Original PR description
Add formula for the total of liabilities in the finnish balance sheet. opw- 2702912 Forward-Port-Of: odoo/enterprise#36248 Forward-Port-Of: odoo/enterprise#35809
https://github.com/odoo/enterprise/commit/8efe4b2932f9b43127b214882125bd98804b1c67 got mistakenly cancelled by https://github.com/odoo/enterprise/commit/95d8a49162da9a7608180d1748996a68d85c9894 in 15.0. This resulted in the Partner VAT Listing files being refused by the government if there was an accounting firm set on the company. We restore the proper node order here, and in the meantime add some basing tests to ensure that. Forward-Port-Of: odoo/enterprise#36103 Forward-Port-Of: odoo/enterpr
Original PR description
https://github.com/odoo/enterprise/commit/8efe4b2932f9b43127b214882125bd98804b1c67 got mistakenly cancelled by https://github.com/odoo/enterprise/commit/95d8a49162da9a7608180d1748996a68d85c9894 in 15.0. This resulted in the Partner VAT Listing files being refused by the government if there was an accounting firm set on the company. We restore the proper node order here, and in the meantime add some basing tests to ensure that. Forward-Port-Of: odoo/enterprise#36103 Forward-Port-Of: odoo/enterprise#35975
before this commit, in asset form view, while clearing the acquisition date it was showing Traceback error from the compute function of prorata date after this commit, there is no traceback on clearing the acquisition date  Forward-Port-Of: odoo/enterprise#36247
Original PR description
before this commit, in asset form view, while clearing the acquisition date it was showing Traceback error from the compute function of prorata date after this commit, there is no traceback on clearing the acquisition date  Forward-Port-Of: odoo/enterprise#36247
Currently, when sending a follow-up email, the email itself is not actually sent. On top of that, in the chatter, it appears like the email was sent by the customer instead of to the customer. To fix this, we just need to remove the `email_from` parameter, as it was set to the customer's email. Forward-Port-Of: odoo/enterprise#36230
Original PR description
Currently, when sending a follow-up email, the email itself is not actually sent. On top of that, in the chatter, it appears like the email was sent by the customer instead of to the customer. To fix this, we just need to remove the `email_from` parameter, as it was set to the customer's email. Forward-Port-Of: odoo/enterprise#36230
Forward-Port-Of: odoo/enterprise#35945 Forward-Port-Of: odoo/enterprise#35801
Original PR description
Forward-Port-Of: odoo/enterprise#35945 Forward-Port-Of: odoo/enterprise#35801
…et}: reintroduce lost translations from 15.0/Transifex Some translations were lost when we changed to 16.0 since there is no l10n_* project for 16.0 on Transifex. Reintroduced lost translations for Arabic, German, French, Italian, Dutch and Chinese. Task: 3127707 Forward-Port-Of: odoo/enterprise#35623
Original PR description
…et}: reintroduce lost translations from 15.0/Transifex Some translations were lost when we changed to 16.0 since there is no l10n_* project for 16.0 on Transifex. Reintroduced lost translations for Arabic, German, French, Italian, Dutch and Chinese. Task: 3127707 Forward-Port-Of: odoo/enterprise#35623
This commit removes all props declaration warning when using documents. TaskId-3060562 Forward-Port-Of: odoo/enterprise#36217
Original PR description
This commit removes all props declaration warning when using documents. TaskId-3060562 Forward-Port-Of: odoo/enterprise#36217