Daily updates from Odoo
Navigate
Branch
Saturday, December 7, 2024
13 changes
6 changes
Miscellaneous changes
- Created a new module `l10n_mt_pos` to provide a compliance letter required by Maltese businesses for requesting an EXO number. - Automatically installs for Malta by default. - Added a menu item under "Reporting" > "Compliance Letter" to allow users to download the document. Task ID: 4373339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189868 Forward-Port-Of: odoo/odoo#189640
Original PR description
- Created a new module `l10n_mt_pos` to provide a compliance letter required by Maltese businesses for requesting an EXO number. - Automatically installs for Malta by default. - Added a menu item under "Reporting" > "Compliance Letter" to allow users to download the document. Task ID: 4373339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189868 Forward-Port-Of: odoo/odoo#189640
This commit adds the E-invoicing app for Jordan. The E-invoicing is mandatory for businesses in Jordan as the end of May 2024. It is a backport of this PR: https://github.com/odoo/odoo/pull/182983 task-3895493 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#176625
Original PR description
This commit adds the E-invoicing app for Jordan. The E-invoicing is mandatory for businesses in Jordan as the end of May 2024. It is a backport of this PR: https://github.com/odoo/odoo/pull/182983 task-3895493 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#176625
Description of the issue/feature this PR addresses: When there is more than one mail.activity.schedule records created in a process, the function `_compute_plan_available_ids()` will face the error Expected singleton. Current behavior before PR: This issue will not happen when launching the activity plan on WUI because users open one launch plan wizard at a time. When activity plans need to launch simultaneously, we need to create a separate wizard for each plan, this process will caus
Original PR description
Description of the issue/feature this PR addresses: When there is more than one mail.activity.schedule records created in a process, the function `_compute_plan_available_ids()` will face the error Expected singleton. Current behavior before PR: This issue will not happen when launching the activity plan on WUI because users open one launch plan wizard at a time. When activity plans need to launch simultaneously, we need to create a separate wizard for each plan, this process will cause the issue. Desired behavior after PR is merged: The function `_compute_plan_available_ids()` will work properly. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189843
Before this commit, since the addition of the dual stream feature in v17, starting the screen sharing while the blur was active or swapping from blur to unblur and back would cause a black camera screen. This commit fixes this issue by: 1) Not closing streams when removing them from a RTC session when those streams originate from the device (and not a remote session). 2) Removing the condition on the state, which was always false when attempting to recover an old stream. Forward-Port-Of
Original PR description
Before this commit, since the addition of the dual stream feature in v17, starting the screen sharing while the blur was active or swapping from blur to unblur and back would cause a black camera screen. This commit fixes this issue by: 1) Not closing streams when removing them from a RTC session when those streams originate from the device (and not a remote session). 2) Removing the condition on the state, which was always false when attempting to recover an old stream. Forward-Port-Of: odoo/odoo#189799
The `OpenMoveWidget` was usually called from an `account.move.line`, since https://github.com/odoo/enterprise/commit/6ec55979a79a959b0a7a784ceaa5cdc0b7854182 it is called from `account.move`. With this commit, by using `this.props.record.resModel`, we allow the model to be either `account.move` or `account.move.line`, any other models would raise an error as there is no `action_open_business_doc` defined in other models. Steps: - Install 'Accounting` - Create an asset with passed depreciation
Original PR description
The `OpenMoveWidget` was usually called from an `account.move.line`, since https://github.com/odoo/enterprise/commit/6ec55979a79a959b0a7a784ceaa5cdc0b7854182 it is called from `account.move`. With this commit, by using `this.props.record.resModel`, we allow the model to be either `account.move` or `account.move.line`, any other models would raise an error as there is no `action_open_business_doc` defined in other models. Steps: - Install 'Accounting` - Create an asset with passed depreciation entries and confirm it - Go to 'Depreciation Board' tab - Click on a posted entry name -> We land on an other move (in fact, move that have the line with the same id as the depreciation move) or an error (non existing record) opw-4357468 Forward-Port-Of: odoo/odoo#189861
…anges In previous commit [1], we made changes to handle better the invoicing address partner and the commercial partner. This broke facturx constraints. [1]: https://github.com/odoo/odoo/commit/053c6de8e48ff3fea469531cf32352d88111469e task-no Forward-Port-Of: odoo/odoo#189907
Original PR description
…anges In previous commit [1], we made changes to handle better the invoicing address partner and the commercial partner. This broke facturx constraints. [1]: https://github.com/odoo/odoo/commit/053c6de8e48ff3fea469531cf32352d88111469e task-no Forward-Port-Of: odoo/odoo#189907
2 changes
Miscellaneous changes
Normally, when using document versioning, the attachments linked to a record are re-attached to the document when changing the version. This is not compatible with the requirement for audit trail in Germany (GoBD) as we want to be sure that the document won't be deleted. This is ensure by making sure all the attachments stay attached, and can't be deleted. To reproduce: * Install Accounting and Documents, as well as l10n_de * Select/configure a German company * Create new document folder s
Original PR description
Normally, when using document versioning, the attachments linked to a record are re-attached to the document when changing the version. This is not compatible with the requirement for audit trail in Germany (GoBD) as we want to be sure that the document won't be deleted. This is ensure by making sure all the attachments stay attached, and can't be deleted. To reproduce: * Install Accounting and Documents, as well as l10n_de * Select/configure a German company * Create new document folder settings for Customer Invoices * Create a new invoice * Send & Print * Delete it from the attachments (it should "detach it") * On the document, change the main history version, or on the invoice, navigate through the attachments [opw-4095549](https://www.odoo.com/odoo/project.task/4095549) Forward-Port-Of: odoo/enterprise#74945 Forward-Port-Of: odoo/enterprise#68235
When having Accounting installed with a company without chart template, we can not create a partner as bot `property_account_payable_id` and `property_account_receivable_id` are required. With ff54822738925d5b5b952520bbfbd4a76c876809 we add a non stored computed field to handle the `required` attribute on partner view. We use this field to make the `Accounting Entries` group invisble when it is not needed. opw-4323694 Forward-Port-Of: odoo/enterprise#75153 Forward-Port-Of: odoo/enterprise#749
Original PR description
When having Accounting installed with a company without chart template, we can not create a partner as bot `property_account_payable_id` and `property_account_receivable_id` are required. With ff54822738925d5b5b952520bbfbd4a76c876809 we add a non stored computed field to handle the `required` attribute on partner view. We use this field to make the `Accounting Entries` group invisble when it is not needed. opw-4323694 Forward-Port-Of: odoo/enterprise#75153 Forward-Port-Of: odoo/enterprise#74994
4 changes
Miscellaneous changes
The `OpenMoveWidget` was usually called from an `account.move.line`, since https://github.com/odoo/enterprise/commit/6ec55979a79a959b0a7a784ceaa5cdc0b7854182 it is called from `account.move`. With this commit, by using `this.props.record.resModel`, we allow the model to be either `account.move` or `account.move.line`, any other models would raise an error as there is no `action_open_business_doc` defined in other models. Steps: - Install 'Accounting` - Create an asset with passed depreciation
Original PR description
The `OpenMoveWidget` was usually called from an `account.move.line`, since https://github.com/odoo/enterprise/commit/6ec55979a79a959b0a7a784ceaa5cdc0b7854182 it is called from `account.move`. With this commit, by using `this.props.record.resModel`, we allow the model to be either `account.move` or `account.move.line`, any other models would raise an error as there is no `action_open_business_doc` defined in other models. Steps: - Install 'Accounting` - Create an asset with passed depreciation entries and confirm it - Go to 'Depreciation Board' tab - Click on a posted entry name -> We land on an other move (in fact, move that have the line with the same id as the depreciation move) or an error (non existing record) opw-4357468 Forward-Port-Of: odoo/odoo#189861
Description of the issue/feature this PR addresses: When there is more than one mail.activity.schedule records created in a process, the function `_compute_plan_available_ids()` will face the error Expected singleton. Current behavior before PR: This issue will not happen when launching the activity plan on WUI because users open one launch plan wizard at a time. When activity plans need to launch simultaneously, we need to create a separate wizard for each plan, this process will caus
Original PR description
Description of the issue/feature this PR addresses: When there is more than one mail.activity.schedule records created in a process, the function `_compute_plan_available_ids()` will face the error Expected singleton. Current behavior before PR: This issue will not happen when launching the activity plan on WUI because users open one launch plan wizard at a time. When activity plans need to launch simultaneously, we need to create a separate wizard for each plan, this process will cause the issue. Desired behavior after PR is merged: The function `_compute_plan_available_ids()` will work properly. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189843
- Created a new module `l10n_mt_pos` to provide a compliance letter required by Maltese businesses for requesting an EXO number. - Automatically installs for Malta by default. - Added a menu item under "Reporting" > "Compliance Letter" to allow users to download the document. Task ID: 4373339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189868 Forward-Port-Of: odoo/odoo#189640
Original PR description
- Created a new module `l10n_mt_pos` to provide a compliance letter required by Maltese businesses for requesting an EXO number. - Automatically installs for Malta by default. - Added a menu item under "Reporting" > "Compliance Letter" to allow users to download the document. Task ID: 4373339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189868 Forward-Port-Of: odoo/odoo#189640
Versions -------- - 16.0+ Steps ----- 1. Create a rental order; 2. cancel said rental order; 3. go to Schedule; 4. change search to show all rental orders; 5. hover over cancelled rental order. Issue ----- It's still showing its status as 'reserved'. Cause ----- The `report_line_status` field assumes any line that isn't picked up or returned is reserved. Solution -------- If the order's state is `cancel`, display the report line as "Cancelled". opw-4342420 Forward-P
Original PR description
Versions -------- - 16.0+ Steps ----- 1. Create a rental order; 2. cancel said rental order; 3. go to Schedule; 4. change search to show all rental orders; 5. hover over cancelled rental order. Issue ----- It's still showing its status as 'reserved'. Cause ----- The `report_line_status` field assumes any line that isn't picked up or returned is reserved. Solution -------- If the order's state is `cancel`, display the report line as "Cancelled". opw-4342420 Forward-Port-Of: odoo/enterprise#75245 Forward-Port-Of: odoo/enterprise#75066
1 change
Resolved issues and error corrections
This update corrects a minor issue in the Odoo tour that guides users through the approval process. The previous method of identifying the correct status button relied on an outdated attribute, which is now replaced with a more reliable method using the 'aria-checked' attribute. This ensures the tour functions correctly and provides a seamless user experience.
Original PR description
This is just to test solving of conflicts on https://github.com/odoo/enterprise/pull/72263