Daily updates from Odoo
Navigate
Branch
Tuesday, February 4, 2020
46 changes
New functionality added to Odoo
Studio now includes a guided model configurator that helps users create new apps and menu items with common business features already set up. It can automatically add useful fields, views, menus, and access settings so new applications are faster to build and more immediately usable.
Original PR description
Studio usability and user experience improvement with an emphasis on the creation of new applications and menu items. The main improvement provided by this task is the introduction of a 'Model…
Studio usability and user experience improvement with an emphasis
on the creation of new applications and menu items.
The main improvement provided by this task is the introduction of a
'Model Configurator', as new dialog that can be accessed when creating
new models in Studio, either through the App Creator or through the
edition of a menu.
This model configurator allows user to select pre-determined behaviours
on their newly-created models. The possible behaviours include:
- m2o to a `res.partner` record ('Customer') which will enable
the map view on the model
- m2o to a `res.users` record ('Responsible')
- date fields ('Date', 'Date Start', 'Date Stop') which will enable
the calendar and gantt views on the model respectively
- monetary field ('Value'), which will enable the pivot view on the model
- stage field, which will create a model for this purpose and which will
enable the kanban view
- image field
- tags field which will create a model for this purpose
- text field ('Notes')
- m2o to a `res.company` field ('Company') - this option is enabled
by default and is only visible in a multi-company environment; it will
also create a record rule for the created model to restrict access
based on the company field.
Along with these, several behaviours are enabled by default and
can only be disabled when in debug mode:
- archiving behaviour
- sequencing of record through a `sequence` field
- inheritance of `mail.thread` and `mail.activity.mixin`
The selected behaviours will be used to automatically generate
views and menu entries (for tags and stages models) in the app.
The enabled view types will depend on the selected behaviours
and will include all relevant fields according in a 'best practice' way
(e.g. images are included in the kanban card, etc.).
Other changes in this task:
- default access rules are more lax than before (CRUD for internal
users by default)
- small UX improvement in the Studio tabs at the top right
Task 2091654
Community PR: odoo/odoo#42055Enhancements to existing features
Delivery operations now better keep package and shipment weights aligned, including packages that use a carrier’s default packaging. The update also adds clearer estimated pricing and unit-of-measure display improvements, helping teams quote and manage shipping more accurately.
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 blog latest posts block has been redesigned to work better across devices and offer clearer display choices. Website editors now get standardized layout and hover options, plus the ability to show either recent or most viewed posts, making blog sections more polished and useful.
Original PR description
*: website This reviews the latest posts snippet and its options. Theme options (available in graphene and avantgarde themes) have been made standard, the hover effects on the images have been rewritten as they were broken since the snippet's DOM had been altered in bb0cdec4594f and the css rules no longer applied. The number of posts option has been removed in favor of a fixed number that depends on the screen size so that the layout looks good on all devices (3x1, 2x2 1x3). The list, big picture and horizontal layouts of this snippet have been fused, and the layout is now an option on the snippet. A new option has also been added to choose which posts are displayed: most recent or most viewed. Lastly, a new 'cards' layout similar to the one on odoo.com has been added. See sub-commits for details. task-2152188 Linked to https://github.com/odoo/design-themes/pull/198
Event organizers get clearer event reporting, easier invitation tools, and better registration handling. The update also improves ticket sale visibility, attendee payment status, and speaker proposal formatting, making event operations smoother across sales, marketing, and website workflows.
Original PR description
PURPOSE Improve global event usability by adding a graph view as well as various changes on the ticket sale flow. We also improved the track proposal layout, added a handy button to invite partners to your event and prepared some data for the event_barcode module. SPECIFICATIONS - Add a "Invite" button on the event, that allows sending invitations though the mass_mailing / mass_sms features - Add a graph view for the event.event model - Allow styling the description and the biography when sending a track proposal with basic plaintext2html usage - Improve event and sale views integration in the event_sale module (stat buttons and next activity generation) - General improvements to the "auto confirm" flow of registrations - Prepare data for the event_barcode module, to make it "event agnostic" More details in underlying commits LINKS Task ID : 2093336 Enterprise PR: odoo/enterprise#7760
Expense receipts and other attachments are now shown in the purchase journal document preview. This makes it easier for accounting teams to review supporting documents directly from journal entries without opening the original expense separately.
Original PR description
Adding preview of expenses attachment to journal view. When creating an expense, files can be attached (e.g. scanned receipts). Those attachment files where not displayed in "Accounting > Accounting > Journals > Purchases" move_line list. They now appear in the document preview. Task = 2176443
Creating a new blog post is now less visually distracting and guides users more directly to set up the cover area. Blog and event cover sections can now have their background color adjusted instead of being locked to a default style, making content setup smoother and more flexible.
Original PR description
The creation of a new blog post is noisy. The user is disturbed with colors (purple box, blue borders, etc). task-2144335
Custom model records now duplicate with their name included by default, making copied records clearer for users. Kanban cards with images also render more reliably for custom models, improving the Studio-created app experience.
Original PR description
Improvements for custom models and some default behaviours linked to the Studio model configurator (Enterprise task). In a nutshell: - mark the default `x_name` field of a custom model as 'to be copied' - improvement for kanban views that makes it easier to user with custom models The interesting part is in the Enterprise `web_studio` module. Task 2091654 Enterprise PR: odoo/enterprise#7326
This update makes blog creation and editing smoother by simplifying cover options, reducing visual clutter in edit mode, and making key actions like publishing clearer. It also improves default blog navigation and restores quote styling so published content looks more polished.
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
Shipping carrier integrations now use the estimated weight from the related picking when preparing shipment requests. This should make carrier quotes and labels more accurate across supported delivery services, reducing manual corrections and pricing mismatches.
Event organizers can now view events on a map, making it easier to understand locations at a glance. Barcode check-in has also been improved so staff can scan attendees across ongoing events from one desk, reducing repeated scans and check-in friction.
Original PR description
PURPOSE Improve the event module usability by adding a map view as well as an improved usability flow when scanning event barcodes SPECIFICATIONS - The "event_enterprise" module now adds a handy map view on event.event - The barcode interface on events is now "event agnostic". Meaning you can scan tickets from any events, making it easier to have multiple events at once in a single location. More details in underlying commit messages. LINKS Task ID : 2093336
Expense attachments, such as scanned receipts, now appear in the purchase journal document preview. This helps accounting teams review supporting documents directly from the journal view without opening the expense separately.
Original PR description
Adding preview of expenses attachment to journal view. When creating an expense, files can be attached (e.g. scanned receipts). Those attachment files where not displayed in "Accounting > Accounting > Journals > Purchases" move_line list. They now appear in the document preview. Task = 2176443
Resolved issues and error corrections
This fixes an issue where partners linked to a company could not be selected or opened unless the user had that company active. It also improves inter-company rules by separating accounting from sales and purchasing, so businesses can use the relevant automation without installing unnecessary apps.
Original PR description
The fact that there is a company id set means that you cannot select the partner in a M2o if you didn't select the company in the selector, and that you cannot open a document where that partner is set if you are not in the correct company. This is an issue for inter_company_rules, as you should be able to select the company to make a so, po or invoice to a company of the same database. 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 fix aligns account selection rules across accounting and purchasing so users see the appropriate accounts for products and categories. It also restores missing company-specific filtering, reducing the risk of choosing accounts from the wrong company in multi-company setups.
Original PR description
This started from noticing that purchase somewhat oddly *removes* a filter (internal_type='other') from a domain which is fairly rare. Looking at the file histories didn't yield anything of interest ("v9 accounting") but finally looking at the model revealed an additional multi-company filter missing from both views.
After consulting with @qdp-odoo, @sle-odoo and @lap-odoo, no good reason was found for the discrepancies:
* internal_type filter should probably always be there, unclear why it would get removed in purchase
* whoever added the multicompany filter *probably* missed that it would never be used because there was not one but two views overriding it (differently)
* sibling "income" field, as well as the corresponding fields on the product category, should match (though they were less incoherent).This fixes a purchasing issue where increasing a purchase order quantity could calculate the added stock incorrectly when returned items were linked to the order. The change helps ensure purchase updates create the right incoming stock movements and avoids confusion caused by returns.
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
This update cleans up outdated internal code patterns that were causing deprecation warnings during development and testing. It helps keep Odoo easier to maintain and better prepared for future dependency and platform updates, with little expected impact on day-to-day users.
Original PR description
@Julien00859 already made a pass on this at some point but there's a bunch of warnings either dynamic or from not the stdlib left over. Some of them can't really be fixed in-code and have been explicitly ignored instead: * `setuptools` uses the deprecated `imp` module until v41.6.0 * `zeep` uses defusedxml.lxml which was never intended to be a public / production API, not sure what to do there (cf mvantellingen/python-zeep#956) * there are a ton of invalid escapes in non-raw string literals, they're unlikely to ever be relevant so ignore them
Invoices that are marked as in payment will now show the outstanding credit widget. This helps accounting users apply available credits at the right stage, reducing confusion and avoiding missed credit allocations.
Original PR description
… in_payment -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a duplicate test module name in the stock app that could prevent one set of tests from running. It helps keep automated checks reliable, reducing the risk of unnoticed issues reaching users.
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
System notifications now show sender names with normal punctuation instead of visible web-safe codes. This makes message alerts easier to read, for example showing Bob's friend rather than Bob's friend, while preserving existing security handling for web content.
Original PR description
The title of notification is the author name escaped (for security reasons). https://github.com/odoo/odoo/blob/e3fa264d1053e0f0a5181da56f205cc05cc06316/addons/mail/static/src/js/services/mail_manager.js#L987-L989 When forwarded to the system notification, it does not need to be escaped though, as the system notification is not HTML based. Without this patch, a user named `Bob's friend` sending a message was creating a notification with the title `Bob's friend` Fixes odoo/odoo#24846 PS: PR targeting master as low issue and not worth to potentially break user's notifications for a corner case.
The project forecast Gantt view now organizes shifts by employee instead of user account. This prevents shifts for employees without linked user accounts from appearing as "Undefined User" and makes open and assigned shifts easier to understand.
Original PR description
PURPOSE 'Open Shifts' should be displayed and Once the shift is assigned, it should appear under the corresponding employee. SPECIFICATIONS In project current group by on Gantt view is on 'user_id' not by the employee_id so, when you change the employee and that employee is not linked with the user then it will display the 'Undefined User'. So, we change the group by on 'employee_id' so, in the Gantt view display the 'open shift' as well as display the corresponding 'employee' under the open shift. LINKS PR #8057 Task 2172834
This change removes deprecated internal calls and updates an outdated test method so the affected apps remain compatible with newer supporting libraries. It helps reduce future maintenance risk without changing day-to-day user workflows.
Original PR description
cf odoo/odoo#44164
The reconciliation screen now properly exits amount editing when users click away or press Enter, even if they did not change the value. This prevents the editing field from getting stuck and makes bank reconciliation smoother for accounting users.
Original PR description
…on widget Commit: https://github.com/odoo/enterprise/commit/a1f6cf1367d254a6515546599ac624a823916890 changed the event on input from keyup,blur to change which was wrong. Change event only trigger when an input value has changed, or in our case when we edit the amount of a line, we want the input to disappear when we click elsewhere or when we press enter and no change were made to the value. This commit fixes this by reintroducing the keyup and blur event.
The Gantt view now avoids a crash when users group records by date. This keeps the page usable in affected cases, although date-based grouping behavior remains limited and may need a fuller follow-up fix.
Original PR description
Date grouping is broken: wrong calls to read_group, _getFieldFormattedValue crashes because thee field_date:day field is not passed to _parseServerData and moreover the following logic in…
Date grouping is broken: wrong calls to read_group, _getFieldFormattedValue
crashes because thee field_date:day field is not passed to
_parseServerData and moreover the following logic in _generateRows
"return _.isEqual(record[groupedByField], subGroups[0][groupedByField]);"
won't ever work with the field_date:day (because 6th august 2019 won't
be equal to a datetime).
Note that it didn't work in v12 anyway, it didn't crash but the groups
did not make sens (all records were grouped in an "undefined" group).
Apparently the new gantt view uses read_group ONLY to handle the group_expand
option, to get empty groups. Maybe what we could do here is use a wrapper
of read_group (web_read_group already exists) and drop entirely the call to
search_read, or make web_read_group returns the ids of the grouped
records and match them with the parent group in generate rows and drop
the _.isEqual.
This commit simply ignore the field in groupBy containing a ':', which
is wrong and incomplete but at least doesn't traceback.
task-2036914Code cleanup and technical improvements
The inter-company rules functionality has been split so businesses can use it with Accounting without also installing Sales and Purchase. Companies that need sales and purchase automation still have a separate add-on that builds on the accounting-only module.
Original PR description
Task [2080625](https://www.odoo.com/web?debug#id=2080625&action=333&active_id=967&model=project.task&view_type=form&menu_id=4720) Before, the module was dependent on sale and purchase and it was not possible to use only with account. There are now 2 modules: * account_inter_company_rules which depends only on account * sale_purchase_inter_company_rules which depends on the first one and on sale and purchase
Miscellaneous changes
Simple `this` instead of `self` mistake which prevents the widgets to trigger up events. Forward-Port-Of: odoo/odoo#44411
Original PR description
Simple `this` instead of `self` mistake which prevents the widgets to trigger up events. Forward-Port-Of: odoo/odoo#44411
When an order is synchronized to the server, there is a timeout of 7.5 seconds that is left before considering that the order has not been synchronized, and should be re-syncronised. Since syncronization of order in pos_restaurant have been made, there are more operations than before that are performed, and the synchronization of an order can take more than that. The validation of a picking can also take a lot of time, almost when products are kits and compose of multiple products.
Original PR description
When an order is synchronized to the server, there is a timeout of 7.5 seconds that is left before considering that the order has not been synchronized, and should be re-syncronised. Since…
When an order is synchronized to the server, there is a timeout of 7.5 seconds that is left before considering that the order has not been synchronized, and should be re-syncronised. Since syncronization of order in pos_restaurant have been made, there are more operations than before that are performed, and the synchronization of an order can take more than that. The validation of a picking can also take a lot of time, almost when products are kits and compose of multiple products. The problem, is that if it takes more than 7.5, the same order will be pushed again to the server, even if the previous sychro still running, which will lead to wait the previous request that has the lok on the same records, all this blocked request can lead to block all workers of the server because all requests are trying to modify same objects. So we've increased the timout for flushed orders. 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#44600
Purpose ======= Before this commit, the method _mail_find_partner_from_emails could return a list mixing partner ids and partner recordset, that could lead to issue when trying to read the different elements. With this commit, we ensure that we return a list of records only. 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/s
Original PR description
Purpose ======= Before this commit, the method _mail_find_partner_from_emails could return a list mixing partner ids and partner recordset, that could lead to issue when trying to read the different elements. With this commit, we ensure that we return a list of records only. 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#44588
With the commit some time ago #d382288, I removed to take the first, but you can have multiple transfer accounts in one company. The best way is to just do a limit=1, 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#44592
Original PR description
With the commit some time ago #d382288, I removed to take the first, but you can have multiple transfer accounts in one company. The best way is to just do a limit=1, 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#44592
It very rarely happens that the test is failing due to the following error: `Tour shop_list_view_b2c failed at step .oe_product_cart .oe_currency_value:contains("825.00")` The value found in that case is 750 instead of 825, which indicates that the b2c setting was not correctly activated. To exclude the RPC themselves from the equation, it is decided here to move the setting change directly in the Python. Forward-Port-Of: odoo/odoo#44581 Forward-Port-Of: odoo/odoo#44492
Original PR description
It very rarely happens that the test is failing due to the following error:
`Tour shop_list_view_b2c failed at step
.oe_product_cart .oe_currency_value:contains("825.00")`
The value found in that case is 750 instead of 825, which indicates that the b2c
setting was not correctly activated.
To exclude the RPC themselves from the equation, it is decided here to move the
setting change directly in the Python.
Forward-Port-Of: odoo/odoo#44581
Forward-Port-Of: odoo/odoo#44492Forward-Port-Of: odoo/odoo#44558
Original PR description
Forward-Port-Of: odoo/odoo#44558
During the port to 13.0 and the new Settings dashboard, the "Load demo data" button visibility condition was reversed. Also rewrote the `&&` operator to `and` for XML readability. Cfr #34290 or https://github.com/odoo/odoo/pull/34290/files#diff-e5df7b873d03867c9527da957b762802L131 Forward-Port-Of: odoo/odoo#44526
Original PR description
During the port to 13.0 and the new Settings dashboard, the "Load demo data" button visibility condition was reversed. Also rewrote the `&&` operator to `and` for XML readability. Cfr #34290 or https://github.com/odoo/odoo/pull/34290/files#diff-e5df7b873d03867c9527da957b762802L131 Forward-Port-Of: odoo/odoo#44526
#### Description of the issue/feature this PR addresses: We found this error because in l10n_ar module we have 3 chart of accounts that actually have same transfer_account_code_prefix. #### Current behavior before PR: When installing chart of accounts of l10n_ar module it is setting a bad transfer account in the company because the account does not belongs to the current company.  If you active superuser you will see that the "(AR) Responsable Inscripto" company has set a transfer_account_id that does not belongs to "(AR) Exento" company  #### Desired behavior after PR is merged: Properly set the transfer account in the company taking account the accounts defined in the current company -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44506
[FIX] im_livechat: add missing dependency to livechat widget Bug === A dependecy is missing "lazyloader.js" Task #2118959 Forward-Port-Of: odoo/odoo#39763
Original PR description
[FIX] im_livechat: add missing dependency to livechat widget Bug === A dependecy is missing "lazyloader.js" Task #2118959 Forward-Port-Of: odoo/odoo#39763
Description of the issue/feature this PR addresses: Followup on https://github.com/odoo/odoo/commit/3ef3aeb640c90e2817878eaa11701aedbf6b6ecb , PR https://github.com/odoo/odoo/pull/29812 Current behavior before PR: Before this commit, Creating New Template from "Send Invoice" wizard doesn't update template_id on the Wizard.  Desired behavior after PR is merged: In this co
Original PR description
Description of the issue/feature this PR addresses: Followup on https://github.com/odoo/odoo/commit/3ef3aeb640c90e2817878eaa11701aedbf6b6ecb , PR https://github.com/odoo/odoo/pull/29812 Current behavior before PR: Before this commit, Creating New Template from "Send Invoice" wizard doesn't update template_id on the Wizard.  Desired behavior after PR is merged: In this commit, We write newly created template_id on the wizard.  Cc @qdp-odoo based on https://github.com/odoo/odoo/pull/29812#issuecomment-459262514 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42655
Description of the issue/feature this PR addresses: Fixes #43705 Current behavior before PR: Before this commit, There will be tracback on converting currecy if there is not date on tax line. Desired behavior after PR is merged: Now we use current date to as fallback to convert currency. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44421
Original PR description
Description of the issue/feature this PR addresses: Fixes #43705 Current behavior before PR: Before this commit, There will be tracback on converting currecy if there is not date on tax line. Desired behavior after PR is merged: Now we use current date to as fallback to convert currency. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44421
- Create a product A MTO, Buy Add a supplier S1 and set a specific reference - Create a product B MTO, Buy Add a supplier S2 and set a specific reference - Create a SO with A & B, confirm - 2 RFQ are created The first RFQ is created with the correct reference, but not the second one. This is because `display_name` depends on context keys: it is computed once for both products with `partner_id` set as `S1`, while it should be recomputed for product B with `partner_id` set
Original PR description
- Create a product A MTO, Buy Add a supplier S1 and set a specific reference - Create a product B MTO, Buy Add a supplier S2 and set a specific reference - Create a SO with A & B, confirm - 2 RFQ are created The first RFQ is created with the correct reference, but not the second one. This is because `display_name` depends on context keys: it is computed once for both products with `partner_id` set as `S1`, while it should be recomputed for product B with `partner_id` set as `S2`. In order to avoid this, we explicitly call `name_get`. opw-2176638 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#44533 Forward-Port-Of: odoo/odoo#44487
The web_diagram module was removed in saas-13.1, along with the diagram view support but some translation files were brought back by forwardports. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44507
Original PR description
The web_diagram module was removed in saas-13.1, along with the diagram view support but some translation files were brought back by forwardports. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44507
- Create an invoice for 1000 - Make a partial payment (e.g. cash) for 250 - Print the ISR The ISR contains an amount of 1000 (total amount), while it should be 750 (amount left to pay). opw-2180538 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#44518 Forward-Port-Of: odoo/odoo#44276
Original PR description
- Create an invoice for 1000 - Make a partial payment (e.g. cash) for 250 - Print the ISR The ISR contains an amount of 1000 (total amount), while it should be 750 (amount left to pay). opw-2180538 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#44518 Forward-Port-Of: odoo/odoo#44276
### Issue - Install eLearning - Edit the header > change image - Save Image not changed ### Cause We do not take new style/class attrib in account in replace_arch_section. ### Solution Take them in account **OPW-2122947 OPW-2182109** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44389
Original PR description
### Issue
- Install eLearning
- Edit the header > change image
- Save
Image not changed
### Cause
We do not take new style/class attrib in account in
replace_arch_section.
### Solution
Take them in account
**OPW-2122947
OPW-2182109**
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#44389The parameter `lot_id` must be a recordset, not an `int`. opw-2188752 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#44512
Original PR description
The parameter `lot_id` must be a recordset, not an `int`. opw-2188752 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#44512
The computation was incorrect, the answer was 10, not 110 with the previous formula Courtesy of Frederico Freire Boaventura Forward-Port-Of: odoo/odoo#44503
Original PR description
The computation was incorrect, the answer was 10, not 110 with the previous formula Courtesy of Frederico Freire Boaventura Forward-Port-Of: odoo/odoo#44503
Steps to reproduce: - install sales - create a new quotation Previous behavior: the avatar next to the author's name is empty in the mailthread Current behavior: avatar is displayed as expected opw-2187231 Forward-Port-Of: odoo/odoo#44379
Original PR description
Steps to reproduce: - install sales - create a new quotation Previous behavior: the avatar next to the author's name is empty in the mailthread Current behavior: avatar is displayed as expected opw-2187231 Forward-Port-Of: odoo/odoo#44379
The default journal depends on the company define in the context or the company in the environment In case of online signature/payment of a SO in a different company then the public user The company will be wrong and the journal_id as well It lead to a fail of the payment since the payment could not be reconciled with the invoices This is happening because the force_company is not taken into account for the default journal This commit take the force_company into account, it take the pre
Original PR description
The default journal depends on the company define in the context or the company in the environment In case of online signature/payment of a SO in a different company then the public user The company will be wrong and the journal_id as well It lead to a fail of the payment since the payment could not be reconciled with the invoices This is happening because the force_company is not taken into account for the default journal This commit take the force_company into account, it take the precedences on the default_company Forward-Port-Of: odoo/odoo#44231
Previously doing so was causing an error but the problem has been fixed by ponto, therefore in order to have the correct account balance in Odoo, we also trigger the refresh of the account when doing the refresh for transactions. Forward-Port-Of: odoo/enterprise#8142
Original PR description
Previously doing so was causing an error but the problem has been fixed by ponto, therefore in order to have the correct account balance in Odoo, we also trigger the refresh of the account when doing the refresh for transactions. Forward-Port-Of: odoo/enterprise#8142
When several packages are delivered in a delivery order, if we cancel the delivery we have to cancel each package one by one because UPS only has API to cancel only one shipment. This was not done so we would get an error. With this changeset, we will cancel 5 packages if there is 5 package on the current delivery order. opw-2180729 Forward-Port-Of: odoo/enterprise#8016
Original PR description
When several packages are delivered in a delivery order, if we cancel the delivery we have to cancel each package one by one because UPS only has API to cancel only one shipment. This was not done so we would get an error. With this changeset, we will cancel 5 packages if there is 5 package on the current delivery order. opw-2180729 Forward-Port-Of: odoo/enterprise#8016
The precision of the `quantity` field should be consistent with the precision of the AML: https://github.com/odoo/odoo/blob/67178f0191cf9a76ff1f7f55a1959aa63b6f7f66/addons/account/models/account_invoice.py#L1732 Closes #7580 opw-2168582 Forward-Port-Of: odoo/enterprise#8124 Forward-Port-Of: odoo/enterprise#8122
Original PR description
The precision of the `quantity` field should be consistent with the precision of the AML: https://github.com/odoo/odoo/blob/67178f0191cf9a76ff1f7f55a1959aa63b6f7f66/addons/account/models/account_invoice.py#L1732 Closes #7580 opw-2168582 Forward-Port-Of: odoo/enterprise#8124 Forward-Port-Of: odoo/enterprise#8122
Belgium localization shadows function from parent resulting in export XML wizard from Belgium localization showing up for other localizations. Forward-Port-Of: odoo/enterprise#8111 Forward-Port-Of: odoo/enterprise#8048
Original PR description
Belgium localization shadows function from parent resulting in export XML wizard from Belgium localization showing up for other localizations. Forward-Port-Of: odoo/enterprise#8111 Forward-Port-Of: odoo/enterprise#8048