Wednesday, October 7, 2020
43 changes · master
Enhancements to existing features
New eCommerce sales orders are no longer assigned to Odoobot by default. Instead, a human salesperson is assigned when an online quotation is sent, helping ensure the right team is notified and customers see a real contact person.
Original PR description
Pad:https://pad.odoo.com/p/r.b315258e687a63bdb1e6f4a2f0b6016b Task:https://www.odoo.com/web#id=2059492&action=327&model=project.task&view_type=form&menu_id=4720
Point of Sale now warns cashiers when they enter an incorrect lot or serial number, or when there is not enough stock for a product. Managers can still allow the sale, and closing a session now highlights draft transfers that need attention so inventory issues are easier to resolve.
Original PR description
**Task**: https://www.odoo.com/web#id=1906359&model=project.task&menu_id=4720 **Pad**: https://pad.odoo.com/p/r.4743e005b9bcb7d415399d5f1c055be6 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When a logged-in user registers for an event, the first attendee line is automatically filled with their available name, email, and phone number. This reduces manual entry and makes event signup faster, especially when users are registering themselves or someone they manage.
Original PR description
# Purpose To ease the process of the registration to an event, we prefill the first row which holds the info of the attendee (name, email, phone), if they are available. In most cases, the attendee: - Take a ticket for himself - Take a ticket for someone he's responsible of - Take a ticket for someone else who doesn't want to be troubled by that (ex: an assistant of a CEO) # Specifications When the user is logged and clicked on the button "Register", the first row will be fill by its personal information. task-2346145
The installation documentation now lists missing system libraries needed by common image and database components on fresh Linux Mint setups. This helps users complete setup more smoothly without searching separate third-party documentation.
Original PR description
On a fresh Linux Mint installation, the libraries used by Pillow and psycopg2 are not installed. This update the list of dependencies so users don't have to dig through Pillow/psycopg2 documentations in order to find and install the missing dependencies.
Resolved issues and error corrections
Refund payments in Point of Sale now follow the same cash rounding rules as regular payments. This prevents staff from accepting non-rounded cash amounts when cash rounding is enabled, improving payment consistency and reducing checkout errors.
Original PR description
When using the cash rounding in the point of sale, when we wanted to pay a refunded order, we didn't apply the cash rounding rules. Now we prevent the user to pay with non rounded values if the cash rounding is enabled. task-id: 2148530 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59048
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59048
This fix restores the visibility of muted text in full-screen course slides after a color system change made it hard to see. Learners using course content in full-screen mode will now see supporting text and labels more clearly.
Original PR description
PURPOSE since a refactoring of the handling of the color system and the way the text muted is handled, the text-muted isn't visible on the full-screen mode of a course SPECIFICATION make text muted visible on full-screen mode LINKS Task: https://www.odoo.com/web#id=2346013&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website editor now only shows dynamic snippet filters that belong to the website being edited. This prevents users managing multiple websites from accidentally selecting filters intended for another site.
Original PR description
[FIX] website: filter_opt of dynamic snippet is filtered by website_id Add a filtering by the contextual website_id when looking up available website_snippet_filters task-2312878 Description of the issue/feature this PR addresses: The filter option in the dynamic snippet gives access to an unrestrained list of website snippet filters Current behavior before PR: All defined website snippet filters are available for selection on all websites Desired behavior after PR is merged: Only website snippet filters assigned to the current website are available for selection -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
PURPOSE when try to see time off analysis from employee, and click on "Action" button it shows blank dropdown option. SPECIFICATION it was checking for the registry action data on the click on action button, so sometime it was showing blank dropdown. But now it will check the registry action if it have data or not before adding it to the action dropdown LINKS Task: https://www.odoo.com/web#id=2325587&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720 -- I c
Original PR description
PURPOSE when try to see time off analysis from employee, and click on "Action" button it shows blank dropdown option. SPECIFICATION it was checking for the registry action data on the click on action button, so sometime it was showing blank dropdown. But now it will check the registry action if it have data or not before adding it to the action dropdown LINKS Task: https://www.odoo.com/web#id=2325587&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#57745
PURPOSE When manually updating the time on a daterange widget, the value sent to the server is not converted to UTC and is sent as it appears on the input. SPECIFICATIONS currently set value takes the string and while parsing the date it takes it as the UTC input and while displaying the date to user it changes the timezone and display the date. so, it shows the wrong date. Instead, change the string date to moment object with current user timezone. so, UTC time will be the same
Original PR description
PURPOSE When manually updating the time on a daterange widget, the value sent to the server is not converted to UTC and is sent as it appears on the input. SPECIFICATIONS currently set value takes the string and while parsing the date it takes it as the UTC input and while displaying the date to user it changes the timezone and display the date. so, it shows the wrong date. Instead, change the string date to moment object with current user timezone. so, UTC time will be the same for all the user. LINKS PR https://github.com/odoo/odoo/pull/50132 Task 2240378 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59208 Forward-Port-Of: odoo/odoo#50132
Before this commit, the pager component would only quit the edit mode if its value changed when hitting Enter. Now, when pressing Enter while the pager value did not change, its edit mode will change regardless. Task [2318738](https://www.odoo.com/web#id=2314864&model=project.task&view_type=form&cids=1&menu_id=) Forward-Port-Of: odoo/odoo#55798
Original PR description
Before this commit, the pager component would only quit the edit mode if its value changed when hitting Enter. Now, when pressing Enter while the pager value did not change, its edit mode will change regardless. Task [2318738](https://www.odoo.com/web#id=2314864&model=project.task&view_type=form&cids=1&menu_id=) Forward-Port-Of: odoo/odoo#55798
Handle salesmen allows to assign responsible to leads using a round robin like algorithm. Currently a write on each lead is done to update its team and responsible, even if number of leads is far greater than number of available users to assign. Current implementation can be simplified by doing one write per sales person to assign on its batch of leads, or a single write if no salesmen has to be assigned. Forward-Port-Of: odoo/odoo#59100
Original PR description
Handle salesmen allows to assign responsible to leads using a round robin like algorithm. Currently a write on each lead is done to update its team and responsible, even if number of leads is far greater than number of available users to assign. Current implementation can be simplified by doing one write per sales person to assign on its batch of leads, or a single write if no salesmen has to be assigned. Forward-Port-Of: odoo/odoo#59100
Before this this commit there would be `ZeroDivisionError` if product is archived. Steps to Reproduce Issue: - Create product with AVCO and Automated Valuation - Create PO and Received all Quantities - Archive Product - Create Bill and Post There will be Traceback ``` File "/data/build/odoo/addons/purchase_stock/models/account_invoice.py", line 84, in _stock_account_prepare_anglo_saxon_in_lines_vals valuation_price_unit = valuation_price_unit_total / valua
Original PR description
Before this this commit there would be `ZeroDivisionError` if product is archived.
Steps to Reproduce Issue:
- Create product with AVCO and Automated Valuation
- Create PO and Received all Quantities
- Archive Product
- Create Bill and Post
There will be Traceback
```
File "/data/build/odoo/addons/purchase_stock/models/account_invoice.py", line 84, in _stock_account_prepare_anglo_saxon_in_lines_vals
valuation_price_unit = valuation_price_unit_total / valuation_total_qty
ZeroDivisionError: division by zero
```
Now we consider Archived `stock_valuation_layer_ids` as well
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#54610- Go to Invoicing > Configuration > Taxes - Create a Tax and enable "Included in Price" in Advanced Options tab - Go to Sales and create a Quotation: * Add an Order Line with the created Tax - Save & Confirm - Edit the Quotation to set a delivery quantity, then save - Go to Sales > Reporting > Sales: * Display row by "Order #" * In Measures, add "Untaxed Amount to Invoice" - Check the values for the create SO The amount for "Untaxed Amount to Invoice" is the amount with taxes inc
Original PR description
- Go to Invoicing > Configuration > Taxes - Create a Tax and enable "Included in Price" in Advanced Options tab - Go to Sales and create a Quotation: * Add an Order Line with the created Tax - Save &…
- Go to Invoicing > Configuration > Taxes - Create a Tax and enable "Included in Price" in Advanced Options tab - Go to Sales and create a Quotation: * Add an Order Line with the created Tax - Save & Confirm - Edit the Quotation to set a delivery quantity, then save - Go to Sales > Reporting > Sales: * Display row by "Order #" * In Measures, add "Untaxed Amount to Invoice" - Check the values for the create SO The amount for "Untaxed Amount to Invoice" is the amount with taxes included. It is due to the fact that untaxed_amount_to_invoice field of sale.order.line is computed from price_reduce field. As price_reduce is computed from price_unit, if there is a tax that is included in the price, price_reduce will also contain the tax in its value. opw-2347571 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#58974
task-2348620 Forward-Port-Of: odoo/odoo#58980
Original PR description
task-2348620 Forward-Port-Of: odoo/odoo#58980
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59129
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59129
When media dialog launched for the first time (with no selected media attachment), "FileWidget.selectedAttachments" contains a default object {url:... , alt:...} (default attachment already on the target), and the click on "Add" button will cause a backtrace since the code on "_save" method tries to access "image_src" attribute on all selectedAttachments elements including default one. The simplest solution would be to check if the object already has an "image_src" attribute. task-23
Original PR description
When media dialog launched for the first time (with no selected
media attachment), "FileWidget.selectedAttachments" contains a default
object {url:... , alt:...} (default attachment already on the target),
and the click on "Add" button will cause a backtrace since the code on
"_save" method tries to access "image_src" attribute on all selectedAttachments
elements including default one.
The simplest solution would be to check if the object already has
an "image_src" attribute.
task-2312878
Forward-Port-Of: odoo/odoo#58143Before this commit, Label *Unit Cost* was displayed in the footer for *BoM Structure* report which is not displaying any cost Information. With this commit we hide *Unit Cost* on *BoM Structure* report. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59320
Original PR description
Before this commit, Label *Unit Cost* was displayed in the footer for *BoM Structure* report which is not displaying any cost Information. With this commit we hide *Unit Cost* on *BoM Structure* report. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59320
Do not round the unit price when calculating the company currency price used to calculate the tax. This avoids rounding errors when the company currency amount has been calculated based on a converted (and rounded) unit price. Corrects a regression bug introduced in 13.0. The behavior has been corrected in 14.0 by a more extensive rework of the accounting module (commit id 419d4bb among others). This fix seeks to correct the bug with minimal impact. In version 12.0, the tax amount
Original PR description
Do not round the unit price when calculating the company currency price used to calculate the tax. This avoids rounding errors when the company currency amount has been calculated based on a…
Do not round the unit price when calculating the company currency price used to calculate the tax. This avoids rounding errors when the company currency amount has been calculated based on a converted (and rounded) unit price. Corrects a regression bug introduced in 13.0. The behavior has been corrected in 14.0 by a more extensive rework of the accounting module (commit id 419d4bb among others). This fix seeks to correct the bug with minimal impact. In version 12.0, the tax amount was calculated strictly based on the total amount, which avoided compounding the rounding issue but had some other problems (see #35358). Current behavior before PR: For example: 20000 @ 2.82 with a rate of 1.1726 gives a tax amount in foreign currency of 11844, which is 10100 in company currency. But if the company currency amount is calculated based on a unit price of 2.4 (rounded converted amount of 2.82), the calculated tax amount will only be 10080 in company currency. Desired behavior after PR is merged: Tax amount is calculated based on the total amount in the foreign currency, not the amount based on the rounded unit price. opw-2340933 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59207 Forward-Port-Of: odoo/odoo#58881
Purpose ======= There's one special case for the participant count update. When we leave a room, if we are the last participant, we directly update the participant count without waiting for the cool down (because the participant might change the page and so the JS might not be loaded anymore). But, Jitsi made a change and now, when we hanging up the room, when the event "videoConferenceLeft" is called, we are the only participant in the list even if they're still other people in th
Original PR description
Purpose ======= There's one special case for the participant count update. When we leave a room, if we are the last participant, we directly update the participant count without waiting for the cool down (because the participant might change the page and so the JS might not be loaded anymore). But, Jitsi made a change and now, when we hanging up the room, when the event "videoConferenceLeft" is called, we are the only participant in the list even if they're still other people in the room. So every time someone hanging up the room, he will send the "zero participant" update. As we can not properly fix it (and be sure it will be "future proof"), we dropped this update. So now, some empty rooms might be marked as having one participant, but no room will be marked as having zero participant if they are not empty (and we prefer this behavior than the opposite). Task-2350117 Forward-Port-Of: odoo/odoo#58985
Previously, when no on-time delivery data, we should 100%. Now we show "No data" to make it more clear. Task 2346121 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#58653
Original PR description
Previously, when no on-time delivery data, we should 100%. Now we show "No data" to make it more clear. Task 2346121 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#58653
"Print Return Label" button on a Transfer is showed when `is_return_picking` field is True. But `is_return_picking` is True for any picking that is a return of another picking, making the button visible for the return of a return, when it should not as it is an outgoing picking. opw-2312425 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at ww
Original PR description
"Print Return Label" button on a Transfer is showed when `is_return_picking` field is True. But `is_return_picking` is True for any picking that is a return of another picking, making the button visible for the return of a return, when it should not as it is an outgoing picking. opw-2312425 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59287
from docs https://docs.python.org/3/library/unittest.html#unittest-skipping: > Skipped classes will not have setUpClass() or tearDownClass() run. This may lead to running out of available sql connections. It mostly happens in odoo.sh, which has max connections set to 16, while default value is 64 Fixes #56636 opw-2345762 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the
Original PR description
from docs https://docs.python.org/3/library/unittest.html#unittest-skipping: > Skipped classes will not have setUpClass() or tearDownClass() run. This may lead to running out of available sql connections. It mostly happens in odoo.sh, which has max connections set to 16, while default value is 64 Fixes #56636 opw-2345762 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59205 Forward-Port-Of: odoo/odoo#59112
Current behavior before PR: When accessing activities from the systray, any existing breadcrumb-item should be clearer. Desired behavior after PR is merged: Clear breadcrumb-item when access activities from the systray. LINKS PR https://github.com/odoo/odoo/pull/58221 Task-2342246 Forward-Port-Of: odoo/odoo#58221
Original PR description
Current behavior before PR: When accessing activities from the systray, any existing breadcrumb-item should be clearer. Desired behavior after PR is merged: Clear breadcrumb-item when access activities from the systray. LINKS PR https://github.com/odoo/odoo/pull/58221 Task-2342246 Forward-Port-Of: odoo/odoo#58221
A few changes, fixes or improvements for `mrp`, `purchase_stock` and `stock`. See commit's message for more information. task-2328830 Forward-Port-Of: odoo/odoo#57254
Original PR description
A few changes, fixes or improvements for `mrp`, `purchase_stock` and `stock`. See commit's message for more information. task-2328830 Forward-Port-Of: odoo/odoo#57254
Disable the link on the vendor delay report graph view, as it leads us to a undesired list view. Task 2346121 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59358
Original PR description
Disable the link on the vendor delay report graph view, as it leads us to a undesired list view. Task 2346121 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59358
This will prevent various flicker when using previous/next. task-2243518 Forward-Port-Of: odoo/odoo#59375 Forward-Port-Of: odoo/odoo#58967
Original PR description
This will prevent various flicker when using previous/next. task-2243518 Forward-Port-Of: odoo/odoo#59375 Forward-Port-Of: odoo/odoo#58967
Before this commit the clickable zone of a checkbox in the editor was all the width of the panel. After this commit, the clickable zone is only the label width + the checkbox width. Also, the active and hover states of the label have been removed to not confuse the user. task-2312878 Forward-Port-Of: odoo/odoo#59240
Original PR description
Before this commit the clickable zone of a checkbox in the editor was all the width of the panel. After this commit, the clickable zone is only the label width + the checkbox width. Also, the active and hover states of the label have been removed to not confuse the user. task-2312878 Forward-Port-Of: odoo/odoo#59240
This commit fixes a number of shapes, usually the problems were with imperfect joints between connecting shapes, shapes being cut not close enough to the edge, or shapes using embedded PNGs for shadows instead of using SVG filters. Forward-Port-Of: odoo/odoo#58333
Original PR description
This commit fixes a number of shapes, usually the problems were with imperfect joints between connecting shapes, shapes being cut not close enough to the edge, or shapes using embedded PNGs for shadows instead of using SVG filters. Forward-Port-Of: odoo/odoo#58333
Calling write in a compute won't works (and shouldn't) if there is any automated action on the model. fix this issue in the compute of `_compute_qty_received`. task-2351175 Forward-Port-Of: odoo/odoo#59224
Original PR description
Calling write in a compute won't works (and shouldn't) if there is any automated action on the model. fix this issue in the compute of `_compute_qty_received`. task-2351175 Forward-Port-Of: odoo/odoo#59224
Commit 59eee6ba5fed0ba74221f44a296ec6efedbc2527 introduced a cleanup mechanism for external data modules being uninstalled from a database, this meant deleting the ir.module.module entry created when first installing the aforementioned external module. However, the above patch has one small oversight: the access of the `imported` field introduced by the `base_import_module` module is done after the `super().module_uninstall()` call which, in the case of the uninstall of the `base_import
Original PR description
Commit 59eee6ba5fed0ba74221f44a296ec6efedbc2527 introduced a cleanup mechanism for external data modules being uninstalled from a database, this meant deleting the ir.module.module entry created when first installing the aforementioned external module. However, the above patch has one small oversight: the access of the `imported` field introduced by the `base_import_module` module is done after the `super().module_uninstall()` call which, in the case of the uninstall of the `base_import_module` module, will delete the `imported` column and the following call to filtered will fail because the column has already been deleted and the registry hasn't been reloaded yet. The solution to this, as explained in the code comment, is to simply compute the `modules_to_delete` before the call to `module_uninstall()`. Forward-Port-Of: odoo/odoo#59393
This commit makes sure we do not try to update the quantity on a finished stock move (during record production or confirming the produce wizard) if there is no finished move available. Closes #57227 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59306 Forward-Port-Of: odoo/odoo#57237
Original PR description
This commit makes sure we do not try to update the quantity on a finished stock move (during record production or confirming the produce wizard) if there is no finished move available. Closes #57227 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59306 Forward-Port-Of: odoo/odoo#57237
We sometimes encountered IoT Boxes crashing because the remount failed. As this isn't a big issue, we won't check the return value of the call to `mount`. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59416
Original PR description
We sometimes encountered IoT Boxes crashing because the remount failed. As this isn't a big issue, we won't check the return value of the call to `mount`. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59416
`http.py` had been modified so the file could be patched correctly with the previous version of the `http.py.iotpatch` file Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#59419
Original PR description
`http.py` had been modified so the file could be patched correctly with
the previous version of the `http.py.iotpatch` file
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#59419Since [1] the feature was broken because of a traceback which occured while trying parse a background image URL of an element which is not in the DOM. [1]: https://github.com/odoo/odoo/commit/7558dcce791f707e3f3470835133f91ec7ff074f Forward-Port-Of: odoo/odoo#59425
Original PR description
Since [1] the feature was broken because of a traceback which occured while trying parse a background image URL of an element which is not in the DOM. [1]: https://github.com/odoo/odoo/commit/7558dcce791f707e3f3470835133f91ec7ff074f Forward-Port-Of: odoo/odoo#59425
Issue - Install "Inventory" module - Go to settings - Activate "Easypost" & "FedEx" connector feature - Create a new 'Shipping Method' - Set "Easypost" as "Provider" - Set "Delivery Product" to "[Delivery_006] Fedex US" - Set "Test" and "Production" api credidentials. - Click on "Load your Easypost carrier accounts" - Choose "FedEx" and click on "select" - Repeat last 2 steps - On "Default Service Level" field value, select "Search More..." option Services are dup
Original PR description
Issue - Install "Inventory" module - Go to settings - Activate "Easypost" & "FedEx" connector feature - Create a new 'Shipping Method' - Set "Easypost" as "Provider" - Set "Delivery Product" to "[Delivery_006] Fedex US" - Set "Test" and "Production" api credidentials. - Click on "Load your Easypost carrier accounts" - Choose "FedEx" and click on "select" - Repeat last 2 steps - On "Default Service Level" field value, select "Search More..." option Services are duplicated. Cause When search_read already existing service, it is done on 'product.packaging' model. Solution Replace model to "search_read" on "easypost.service" instead. opw-2350575 Forward-Port-Of: odoo/enterprise#13869
This will prevent various flicker when using previous/next. task-2243518 Forward-Port-Of: odoo/enterprise#13868 Forward-Port-Of: odoo/enterprise#13762
Original PR description
This will prevent various flicker when using previous/next. task-2243518 Forward-Port-Of: odoo/enterprise#13868 Forward-Port-Of: odoo/enterprise#13762
See commit's message for more information. task-2328830 Forward-Port-Of: odoo/enterprise#13047
Original PR description
See commit's message for more information. task-2328830 Forward-Port-Of: odoo/enterprise#13047
before this commit: - the date was set correctly by the "update status" button in the invoice form view but not with the cron that updates all pending invoices. after this commit: - now the date is set correctly by the cron Forward-Port-Of: odoo/enterprise#13851 Forward-Port-Of: odoo/enterprise#13798
Original PR description
before this commit: - the date was set correctly by the "update status" button in the invoice form view but not with the cron that updates all pending invoices. after this commit: - now the date is set correctly by the cron Forward-Port-Of: odoo/enterprise#13851 Forward-Port-Of: odoo/enterprise#13798
Small fixup of https://github.com/odoo/odoo/commit/2de4417ccd6db13eb2c44419543badf4dfddf2c0 Field length was renamed to packaging_length. opw-2350987 Forward-Port-Of: odoo/enterprise#13845
Original PR description
Small fixup of https://github.com/odoo/odoo/commit/2de4417ccd6db13eb2c44419543badf4dfddf2c0 Field length was renamed to packaging_length. opw-2350987 Forward-Port-Of: odoo/enterprise#13845
- Install delivery_easypost - Go to Sales > Configuration > Shipping Methods and create a shipping method: * Name: Easypost Fedex * Provider: Easypost * Carrier Type: FedEx * Default Package Type: FedExBox * Default Service Level: FEDEX_2_DAY * (Test Environment) - Go to Sales > Products and create a storable product with a weight of 0.1 (i.e. Product X) - Update the quantity (i.e. 100) - Go to Sales > Orders > Customers and create a customer: * Customer X * Company A
Original PR description
- Install delivery_easypost - Go to Sales > Configuration > Shipping Methods and create a shipping method: * Name: Easypost Fedex * Provider: Easypost * Carrier Type: FedEx * Default Package Type:…
- Install delivery_easypost
- Go to Sales > Configuration > Shipping Methods and create a shipping method:
* Name: Easypost Fedex
* Provider: Easypost
* Carrier Type: FedEx
* Default Package Type: FedExBox
* Default Service Level: FEDEX_2_DAY
* (Test Environment)
- Go to Sales > Products and create a storable product with a weight of 0.1 (i.e. Product X)
- Update the quantity (i.e. 100)
- Go to Sales > Orders > Customers and create a customer:
* Customer X
* Company Address:
425 Recker HwyAuburndale
Florida (US)
33823
United States
* Phone: 00337123456
- Create a Quotation:
* Customer: Customer X
* Order Lines: Product X (quantity: 10)
* Add Shipping: Easypost Fedex and get rate
- Confirm Quotation
- Open delivery via Delivery smart button
- Check and set (if not already set) Carrier to "Easypost Fedex" in Additional Info tab
- Validate
- Create a return (via return button), set Carrier (Easypost Fedex) and validate
- Create a return of the previous return (via return button), set Carrier (Easypost Fedex) and validate
An error is raised: "Easypost returned an error: Validation failed: Weight must be greater than 0"
The weight is computed from `qty_done` of the `stock.move.line` for a normal delivery (outgoing) and
from `product_qty` for a return delivery (incoming).
The computed field `is_return_picking` defines if a picking is a return or not.
The issue comes from the fact that `is_return_picking` is True if it is a return of another picking and
and flags the return of a return as a return, when it should not as it is an outgoing picking.
Therefore weight is computed from `product_qty` (which is 0) instead of `qty_done`.
Instead of basing the weight computation on `is_return_picking` field, it should be done on the picking type.
opw-2312425
Forward-Port-Of: odoo/enterprise#13847Task ID: 2350513 Forward-Port-Of: odoo/enterprise#13819
Original PR description
Task ID: 2350513 Forward-Port-Of: odoo/enterprise#13819
BUG === Some Social LinkedIn tests make real HTTP requests during the account creation. This happens when computing the social account statistics. LINKS === Task 2351507 Forward-Port-Of: odoo/enterprise#13828
Original PR description
BUG === Some Social LinkedIn tests make real HTTP requests during the account creation. This happens when computing the social account statistics. LINKS === Task 2351507 Forward-Port-Of: odoo/enterprise#13828