Daily updates from Odoo
Navigate
Branch
Monday, December 9, 2019
51 changes
Enhancements to existing features
Project task lists now stay focused on the selected project even if users remove the default filter, preventing cluttered kanban views. Task breadcrumbs also show the project name, making navigation clearer for users moving from project cards to tasks.
Original PR description
Pad:https://pad.odoo.com/p/r.1bd2e128f23118237b14e8c596093eb8 Task:https://www.odoo.com/web#id=2124377&action=327&model=project.task&view_type=form&menu_id=4720
Web actions can now save their own custom state in the page URL, making it easier to restore the same context after a browser refresh. This improves continuity for users in fullscreen actions and gives Odoo extensions more flexibility without changing core navigation behavior.
Original PR description
Sometimes, it might be useful for an action (e.g. a client action, although this may be used by standard views as well) to include custom values in its state. Since the state of a 'fullscreen' action is pushed in the URL, this means that it is possible for the action to resume its state properly upon refresh of the page (before this commit, only some standard information were pushed to the state - action_id, menu_id, etc. for window actions and action's name, active_id, active_ids for client actions). By implementing the `getState` method, an extension of the action mixin can thus push any state it wishes to the URL.
The website editor now refreshes page widgets automatically after editing options, making changes appear more reliably while content is being adjusted. It also improves how editor actions are handled behind the scenes and prevents certain edit-mode animations from restarting unnecessarily.
Check printing is now easier to adapt for different countries by allowing country-specific modules to define their own check layouts and related print actions. This makes it simpler for businesses operating in new regions to add compliant check formats without changing the core check printing feature.
Original PR description
Task: https://www.odoo.com/web#id=2030714&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.ddf719c3c5c3d5e68c1523369961d6b3
This update gives major configuration sections clear internal names across many Odoo apps. It makes future customizations and extensions safer and easier to maintain, without changing how users interact with the settings screens.
Original PR description
Description of the issue/feature this PR addresses: Since all containers within a configuration view have the same class 'row mt16 o_settings_container' it doesn't allow for very clean/easy xpath expressions. By setting a name on evey major container we can do cleaner and safer xpath expressions that don't need any index or sub-xpaths.
Follow-up of https://github.com/odoo/odoo/pull/39613
Current behavior before PR: If you'd like to xpath into the purchase configuration view and and insert after the last element you'd have to create ugly xpaths with indexes. Something like `<xpath expr="//div[hasclass('o_settings_container'][3]" position="after"></xpath>`
Desired behavior after PR is merged: After this change you can do a clean and safer xpath expression like `<xpath expr="//div[@name='purchase_setting_container']" position="after"></xpath>`
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update enables editing multiple list entries at once in project, timesheet, and expense screens. It helps users make bulk updates more quickly, reducing repetitive manual work in day-to-day operations.
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
The web charting library was updated so charts display date labels more reliably, including on smaller mobile screens. This helps users see time-based information more clearly in views such as Accounting Overview.
Original PR description
Update of Chart.js library to the latest version. Before this commit, we weren't able to see all x-axis dates labels like in Accounting Overview. Tick label rotation on mobile has been fixed in https://github.com/chartjs/Chart.js/pull/5961. 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
Calendar users can now apply changes to all future occurrences of a recurring event starting from a selected date. This makes it easier to adjust ongoing meetings or schedules without manually editing each occurrence, while preserving earlier event history.
Original PR description
The current behaviour with the calendar recurring events is: * You create one event in database * It generate virtual events with virtual ids * If you want to edit a virtual event, it creates a new…
The current behaviour with the calendar recurring events is: * You create one event in database * It generate virtual events with virtual ids * If you want to edit a virtual event, it creates a new real records from the virtual event. * It is not possible to updates multiple virtual events at the same time. What does this improvement does: * You can choose to edit all the future events from a selected date. How does it work: When you choose to update the future virtual events, this commit will: * Copy the original event. * Set the final date of the original event to the selected date. * return the new event Thus you will have two event object. One from the initial start date to the selected date Another from the selected date to the initial final date. 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
Users can now cancel scheduled activities from the chatter area, making it easier to keep communication and follow-up tasks accurate. This reduces clutter from outdated activities and helps teams maintain a clearer view of what still needs action.
Original PR description
Pad: https://pad.odoo.com/p/r.dab6c5a8fab1d0df86ca827b875e8e91 Task: https://www.odoo.com/web?debug=1#id=2006344&action=327&model=project.task&view_type=form&menu_id=4720
CSV files used by Odoo can now include comment rows that start with #, making large manually maintained files easier to organize and update. This is mainly an internal developer convenience and should not affect normal business workflows, except that real data rows should not begin with #.
Original PR description
Certain manually-maintained csv files contain lots of data, sometimes it's hard to keep track of this data in an organized fashion and thus updating these files can become quite tedious. To make it easier for developers, we now allow the usage of comments in CSV files, since comments are not defined in the CSV spec, we arbitrarily decide that any row starting with # is a comment and will therefore be discarded before the parsing of the csv data. Note that this means that any actual data should not begin with #, if this turns out to be a problem, the algorithm may be replaced by a more robust one. Task-ID: 2127354 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
This update modernizes pivot reporting views so they work better in mobile and in Odoo Studio. It also updates related tests to improve reliability and support the newer interface framework.
Companies can now choose any available check layout from Accounting Settings instead of being limited to country-specific options. This makes check printing setup more flexible for businesses operating with different formats or across regions.
Original PR description
Task: https://www.odoo.com/web#id=2030714&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.ddf719c3c5c3d5e68c1523369961d6b3 related community PR: https://github.com/odoo/odoo/pull/35438
Helpdesk teams now keep their own ticket view focused on the selected team, even if a user removes the default filter. Ticket navigation also shows the team name in the breadcrumb, making it clearer where users are working.
Original PR description
Pad:https://pad.odoo.com/p/r.1bd2e128f23118237b14e8c596093eb8 Task:https://www.odoo.com/web#id=2124377&action=327&model=project.task&view_type=form&menu_id=4720
This update makes list views editable in bulk across Helpdesk, Field Service, Planning, and Project Forecast. Teams can update several records at once, reducing repetitive data entry and speeding up day-to-day operations.
Planning shifts can now select any task before a project is chosen, and the project will automatically align with the selected task. This reduces confusing restrictions and prevents accidental changes to a task's project when mismatched planning details are selected.
Original PR description
* existing static domain was almost exactly what we wanted: the only
issue was that if no project was selected (yet) we'd only allow
selecting tasks not linked to a project, whereas the dynamic domain
would allow selecting any task period (with an other onchange
updating the project to match the task)
* also simplify the task onchange:
- always set the project to the task's project
- if we somehow manage to select a project and a task which don't
match, don't go and move the task from one project to the other,
that doesn't seem very sane
Task 2115472The IoT app now includes sample IoT Boxes and connected devices for demonstration and testing. This makes it easier for users and teams to explore IoT workflows without manually creating example hardware records.
Original PR description
Add demo data for IoT Boxes and devices TaskID: 2092615
Resolved issues and error corrections
Users without timesheet permissions can now open project task views normally. This removes an access-related blocker so project work remains visible to the right users even when they do not use timesheets.
Original PR description
Current behavior before PR: If you have not at least the timesheet user right, you can't open project task as a field in not present in the view. Desired behavior after PR is merged: You can open the task view TaskId: 2148606 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix keeps attendee answer choices limited to the relevant event, reducing the chance of selecting incorrect information. It also improves event administration screens by making an email settings field use the full available width and by applying clearer default sorting for registrations and event type cards.
Original PR description
Add a domain that limits to the answers belonging an event only on the attendee form. Make the width of the event_type_mail_ids 100% Sort event.registrations by id DESC and Kanban view by name task-2071337 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix cleans up remaining outdated FontAwesome 5 styling in the Documents app that should have been removed earlier. It helps keep the interface consistent and avoids visual glitches from obsolete icon code.
Original PR description
This commit removes some code that wasn't properly reverted in b152a16b9b236d5d0645fe2f823ebe92257e7d2e
This change fixes how salary package simulation links are generated by removing a fragile filter setup. It helps HR teams create links more consistently and reduces the chance of errors during contract salary simulations.
Original PR description
FIXME: task id
This fix changes how eligible accounting reversal records are selected in the Helpdesk accounting flow. It replaces a fragile automatic filtering method with a more stable rule, reducing the chance of incorrect or missing choices for users.
Original PR description
Task 2115472
The contact map view now supports translations for its labels and buttons when users switch languages. This helps non-English users see the map interface consistently in their selected language, with only third-party zoom labels remaining untranslated.
Original PR description
steps to reproduce: -install contacts -go to settings>translations>languages and activate a second language, for example Ukrainian as it has been fully translated in 13.0 -switch to the Ukrainian language, go to contacts and open the map view you can see the fields are not translated they do not appear in the web_map.pot either translation seem to not happen because the templates.xml file was not living in the static/src folder the fields "Name" and "Address" are part of the contacts_enterprise module (so they will appear in contacts_enterprise.pot, not web_map.pot) the pot file of the contacts_enterprise module was not named properly previous behavior: most fields inside the map view and the buttons are not translatable current behavior: all text inside the map view is translatable except for the "zoom in/out" labels (they are part of a third party library) opw-2144401
This fixes an issue in the Helpdesk Sales Timesheet area related to calculated information and how it appears in the helpdesk view. It helps ensure users see accurate timesheet-related details when working with helpdesk records.
Original PR description
TaskID: 2148606
This fixes a display issue where an icon was not shown correctly in the IoT scan range interface. The change improves visual clarity for users working with IoT device scanning, with no expected impact on business processes.
Original PR description
Icon not corretly displayed
This fixes the Helpdesk sales order selection so it behaves correctly when no customer is set. Users can still access available sales orders instead of seeing an empty or blocked list, reducing friction when linking helpdesk tickets to sales information.
Original PR description
The existing (and likely immediately replaced) static domain would be *almost* correct, but did not take in account the partner_id condition of the dynamic one. To check: I'm guessing the static domain "doesn't work" in the case partner_id is unset because the ORM then warns/complains about the `(a child_of False)` expression. However we can just coalesce False to [], which is what expression.py also does (after warning about it). If we truly actually care about partner_id being unset, we can use the conditional section hack. Task 2115472
This fix removes an outdated filtering behavior in the rental setup wizard so users can access the expected product choices. It helps avoid confusion during rental configuration and supports smoother sales operations.
Original PR description
Task 2115472
Features or functions removed from Odoo
This update removes a dynamic filtering behavior in the employee contract signing wizard. It helps keep the signing document selection process simpler and more consistent for users managing contract signatures.
Original PR description
Task 2115472
This change removes an older dynamic filtering behavior in the Helpdesk Sales Timesheet area. It simplifies how related options are handled, reducing complexity and helping keep ticket and timesheet workflows more predictable.
Original PR description
Task 2115472
Code cleanup and technical improvements
This update introduces a new user interface technology foundation and rebuilds the pivot reporting view on it. Business users should see more reliable interactive reporting behavior now, while the change also prepares Odoo for faster future interface improvements.
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
Miscellaneous changes
We add a condition to add printer. Printer, for protocol DNSSD and LPD, must have a "model" 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#41550
Original PR description
We add a condition to add printer. Printer, for protocol DNSSD and LPD, must have a "model" 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#41550
Update of Chart.js library to the latest version. Before this commit, we weren't able to see all x-axis dates labels like in Accounting Overview. Tick label rotation on mobile has been fixed in https://github.com/chartjs/Chart.js/pull/5961. 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#4
Original PR description
Update of Chart.js library to the latest version. Before this commit, we weren't able to see all x-axis dates labels like in Accounting Overview. Tick label rotation on mobile has been fixed in https://github.com/chartjs/Chart.js/pull/5961. 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#41568
When returning a delivery where the value was taken from different receipt, the last receipt's unit cost was wrongly used when returning the delivery. Now we use the `unit_cost` of the delivery when returning it. task-2150889 Forward-Port-Of: odoo/odoo#41422
Original PR description
When returning a delivery where the value was taken from different receipt, the last receipt's unit cost was wrongly used when returning the delivery. Now we use the `unit_cost` of the delivery when returning it. task-2150889 Forward-Port-Of: odoo/odoo#41422
Actual IoT Box not detect correctly Epson TM-T88v. Now we can detect printer even if name is 'Unknow' Taskid: 2153108 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#41530
Original PR description
Actual IoT Box not detect correctly Epson TM-T88v. Now we can detect printer even if name is 'Unknow' Taskid: 2153108 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#41530
### Issue - Install CRM & Website - Edit the website contact form - Add "Expected revenue" field Traceback ### Cause Monetary fields are not handled by the form builder ### Solution Add the monetary field in the form builder core **OPW-2150986** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41403
Original PR description
### Issue
- Install CRM & Website
- Edit the website contact form
- Add "Expected revenue" field
Traceback
### Cause
Monetary fields are not handled by the form builder
### Solution
Add the monetary field in the form builder core
**OPW-2150986**
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#41403Suppose you have a record rA of model A, and a record rB of model B which has a related B.v on field A.x, that is stored and translatable. Suppose also that user U can write on A, but not on B because of ACLs. Let U write on rA.x. Then it recomputes the value of rB.v. Since this directly calls the _write, we check the record rules but not the ACLs, so U wrote rA.x and rB.v successfully. Now let U be in another language L. This means that we go trough translations, which calls _set_ids
Original PR description
Suppose you have a record rA of model A, and a record rB of model B which has a related B.v on field A.x, that is stored and translatable. Suppose also that user U can write on A, but not on B…
Suppose you have a record rA of model A, and a record rB of model B which has a related B.v on field A.x, that is stored and translatable. Suppose also that user U can write on A, but not on B because of ACLs. Let U write on rA.x. Then it recomputes the value of rB.v. Since this directly calls the _write, we check the record rules but not the ACLs, so U wrote rA.x and rB.v successfully. Now let U be in another language L. This means that we go trough translations, which calls _set_ids. If the translation already exists, then the update is done in SQL so no access rights are checked. However if translations do not exist, the translations are created via the ORM and thus check both record rules and ACLs. Therefore the operation is forbidden, since by hypothesis U cannot write on B. We can skip the check in this case, since we come from either a create or a write, so the ACLs should already be checked on the original models as intended (in the case of B, not fully). Furthermore it removes the incoherency with the update case. opw 2145738 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#41509 Forward-Port-Of: odoo/odoo#41477
This reverts commit e5479fcfdb76bdbf9301fb140d873483bafdb9e4. This commit prevented an issue of losing messages on post in case of connectivity loss. The implementation consists of keeping the content in the composer until the server acknowledges handling the message. However, this solution introduces significant issues. For instance, sending messages in quick succession will likely loose or duplicate some content, based on how fast/slow the RPC `message_post` is resolved. Plus, ther
Original PR description
This reverts commit e5479fcfdb76bdbf9301fb140d873483bafdb9e4. This commit prevented an issue of losing messages on post in case of connectivity loss. The implementation consists of keeping the content in the composer until the server acknowledges handling the message. However, this solution introduces significant issues. For instance, sending messages in quick succession will likely loose or duplicate some content, based on how fast/slow the RPC `message_post` is resolved. Plus, there was an issue on mobile because the input focus was lost during the RPC. As a consequence, the virtual keyboard flickered. The intent was to fix a rare issue, and since the problems of this solution clearly outweigh the gain, we decided to revert. Forward-Port-Of: odoo/odoo#41484
This reverts commit ff1c35513aecef5fbc30f7c2f3834450e719714e. 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#41324
Original PR description
This reverts commit ff1c35513aecef5fbc30f7c2f3834450e719714e. 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#41324
Pad:https://pad.odoo.com/p/r.57bf8f062006c8c475a46867024e8317 Task:https://www.odoo.com/web#id=2145507&action=327&model=project.task&view_type=form&menu_id=4720 Forward-Port-Of: odoo/odoo#41223
Original PR description
Pad:https://pad.odoo.com/p/r.57bf8f062006c8c475a46867024e8317 Task:https://www.odoo.com/web#id=2145507&action=327&model=project.task&view_type=form&menu_id=4720 Forward-Port-Of: odoo/odoo#41223
Pad: https://pad.odoo.com/p/r.57bf8f062006c8c475a46867024e8317 Task:https://www.odoo.com/web#id=2145507&action=327&model=project.task&view_type=form&menu_id=4720 Forward-Port-Of: odoo/odoo#41005
Original PR description
Pad: https://pad.odoo.com/p/r.57bf8f062006c8c475a46867024e8317 Task:https://www.odoo.com/web#id=2145507&action=327&model=project.task&view_type=form&menu_id=4720 Forward-Port-Of: odoo/odoo#41005
### Description of the issue/feature this PR addresses: When creating vendor bills, it was considering this two numbers as different but actually are the same invoice number * 01234-00000001 * 1234-00000001 To avoid this we remove the zero to the left always if the pos number > 4. ### Current behavior before PR: 1. Create a vendor bill for Odoo Inc 2. Set Document number to 01234-00000001 3. Validate invoice. 4. Create a second vendor bill for same Odoo Inc partner. 5. Set Do
Original PR description
### Description of the issue/feature this PR addresses: When creating vendor bills, it was considering this two numbers as different but actually are the same invoice number * 01234-00000001 *…
### Description of the issue/feature this PR addresses: When creating vendor bills, it was considering this two numbers as different but actually are the same invoice number * 01234-00000001 * 1234-00000001 To avoid this we remove the zero to the left always if the pos number > 4. ### Current behavior before PR: 1. Create a vendor bill for Odoo Inc 2. Set Document number to 01234-00000001 3. Validate invoice. 4. Create a second vendor bill for same Odoo Inc partner. 5. Set Document number to 1234-00000001 6. Validate invoice. It validate both invoices but it should not, because the document number is the same and can not be used twice for the same vendor. ### Desired behavior after PR is merged: With the change we made now 01234-00000001 is saved as 1234-00000001, so now when try to validate an invoice with the same document number will raise the uniqueness error. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41196
If you reconcile for example a bank statement of 200,00€ with a customer invoice of 300,00€, you get a pen icon next to the 300,00€ and if you click on it you have an editing cell with: 200.00 But if you validate this, this will be parse in the current language number formatting so if you have . as thousands separator, this number will become 20000 which is not expected. With this changeset, we display the number in the current lang format. note: with this fix, number of decimals can be diff
Original PR description
If you reconcile for example a bank statement of 200,00€ with a customer invoice of 300,00€, you get a pen icon next to the 300,00€ and if you click on it you have an editing cell with: 200.00 But if you validate this, this will be parse in the current language number formatting so if you have . as thousands separator, this number will become 20000 which is not expected. With this changeset, we display the number in the current lang format. note: with this fix, number of decimals can be different than 2 note: forward-port of odoo/odoo#41410 saas-12.3 adapted for saas-13.1 opw-2150396 Forward-Port-Of: odoo/enterprise#7078
…arning from previous years" This reverts commit 7b1042644fabce1451f94b663b4e406ee05efe13. opw-2118381 Forward-Port-Of: odoo/enterprise#7114 Forward-Port-Of: odoo/enterprise#7053
Original PR description
…arning from previous years" This reverts commit 7b1042644fabce1451f94b663b4e406ee05efe13. opw-2118381 Forward-Port-Of: odoo/enterprise#7114 Forward-Port-Of: odoo/enterprise#7053
This reverts commit b0f6d645ff4fe5f5cf5f865434360981a58100fb. Forward-Port-Of: odoo/enterprise#7034
Original PR description
This reverts commit b0f6d645ff4fe5f5cf5f865434360981a58100fb. Forward-Port-Of: odoo/enterprise#7034
Before that, v13 tax model was totally ignored, leading to erratic behavior (and no tags at all on lines). Forward port of https://github.com/odoo/odoo/pull/40687 (as the reconciliation widget got moved to enterprise) Forward-Port-Of: odoo/enterprise#6963
Original PR description
Before that, v13 tax model was totally ignored, leading to erratic behavior (and no tags at all on lines). Forward port of https://github.com/odoo/odoo/pull/40687 (as the reconciliation widget got moved to enterprise) Forward-Port-Of: odoo/enterprise#6963
Taskid: 2146226 X-original-commit: b2db442c6492c2d9dbca03e3dcf0ac81655e31a3 Forward-Port-Of: odoo/enterprise#7133
Original PR description
Taskid: 2146226 X-original-commit: b2db442c6492c2d9dbca03e3dcf0ac81655e31a3 Forward-Port-Of: odoo/enterprise#7133
In the version of auditfiles.nl XSD validation file, there has been country codes added in the version of september 2017. With this changeset, the XSD file is updated and missing country code (such as RS) will not cause a validation error. opw-2150268 Forward-Port-Of: odoo/enterprise#7077
Original PR description
In the version of auditfiles.nl XSD validation file, there has been country codes added in the version of september 2017. With this changeset, the XSD file is updated and missing country code (such as RS) will not cause a validation error. opw-2150268 Forward-Port-Of: odoo/enterprise#7077
TaskID: 2146226 Forward-Port-Of: odoo/enterprise#6969
Original PR description
TaskID: 2146226 Forward-Port-Of: odoo/enterprise#6969
Usecase to reproduce: - Create a delivery order with easypost UPS as carrier - Use multiple packages - Validate the picking It raise a Usererror returned from easypost response. However the buy order is created on easypost.com It happens because other carrier from easypost during an order return the rate for the order in the first shipment and following shipments have their rate empty. UPS do the same process but it adds a message in shipments with empty rate explaining that the rate
Original PR description
Usecase to reproduce: - Create a delivery order with easypost UPS as carrier - Use multiple packages - Validate the picking It raise a Usererror returned from easypost response. However the buy order is created on easypost.com It happens because other carrier from easypost during an order return the rate for the order in the first shipment and following shipments have their rate empty. UPS do the same process but it adds a message in shipments with empty rate explaining that the rate is in the first shipment. However when easypost request catch a response with a messages inside, it consider it has an error message and return it to the customer. In this case the error message is not a real error and there is no flag in the response that allow us to know if it's a real error or not thus for this case we remove it from the response and log it as a message_post on the picking. opw-2081066 Forward-Port-Of: odoo/enterprise#6761
Add some move to 778000. Go to Reporting>Pérdidas y Ganancias. The report doesn't add to the total the 12th line as it should, given the formula. opw-2149538 Forward-Port-Of: odoo/enterprise#7030
Original PR description
Add some move to 778000. Go to Reporting>Pérdidas y Ganancias. The report doesn't add to the total the 12th line as it should, given the formula. opw-2149538 Forward-Port-Of: odoo/enterprise#7030
The method ``_run_fifo()`` now is in the product, not in the move like in the last version. And extra, now is not send the ``move`` as parameter, to know which is the move where must be assigned the fifo candidate. Now, to get the move origin was moved to ``_create_out_svl``, to assign the entry correctly. The tests were improved. Forward-Port-Of: odoo/enterprise#7015
Original PR description
The method ``_run_fifo()`` now is in the product, not in the move like in the last version. And extra, now is not send the ``move`` as parameter, to know which is the move where must be assigned the fifo candidate. Now, to get the move origin was moved to ``_create_out_svl``, to assign the entry correctly. The tests were improved. Forward-Port-Of: odoo/enterprise#7015
When an address contains the `/` character, the call to OSM fails. We can simply remove it since it shouldn't be necessary to locate the address. opw-2150692 Forward-Port-Of: odoo/enterprise#7105 Forward-Port-Of: odoo/enterprise#7092
Original PR description
When an address contains the `/` character, the call to OSM fails. We can simply remove it since it shouldn't be necessary to locate the address. opw-2150692 Forward-Port-Of: odoo/enterprise#7105 Forward-Port-Of: odoo/enterprise#7092