Tuesday, February 16, 2021
41 changes · master
Enhancements to existing features
When a point of sale session cannot close because its accounting entries are not balanced, users are now prompted to choose the account used for the balancing amount. This gives businesses clearer control over how closing adjustments are recorded instead of automatically using the default receivable account.
Original PR description
When closing pos.session and it turned out that during the creation of journal entry the move lines are not balanced, pos automatically balances the lines by crediting the amount to balance and recording it to the default pos receivable account. In this commit, we are changing the behavior by allowing the user to choose which account the imbalance amount be recorded. So the workflow becomes: 1. Close pos session fails. 2. Wizard shows the amount to balance and asks which account to record it. 3. Confirm the wizard to successfully close the session. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When users enable decorative background shapes in the website editor, the shape selection menu now opens automatically instead of staying closed. The editor also reuses colors from existing page shapes, making it quicker to keep website designs visually consistent.
Original PR description
Before this commit when toggling shapes on a snippet background, the shape selection dropdown was shown as closed. After this commit when toggling shapes on on a snippet background, the shape selection dropdown is automatically opened. Also, the palette of the shape is based on the previous shape's palette. task-2431445 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
Employees can now delete their own future time off requests as long as they have not yet been validated. This reduces administrative effort by letting employees correct planned absences themselves before approval, with tests added to confirm the access rules.
Original PR description
Add some tests Task - 2428789
This update improves how checkbox-related fields appear on mobile screens across Event, Purchase, and Survey forms. It makes dependent fields easier to show or hide consistently and fixes alignment issues that could make forms harder to read on small devices.
Original PR description
This PR adds a class to be able to show/hide other fields depending on a checkbox status. This class is needed to have this behavior on desktop but also on mobile. We can now fix some alignment issues encountered on mobile. Related task-ID: 1929043
Product category filters now show only the category name instead of the full hierarchy. This makes the search panel easier to read because parent categories are already displayed separately.
Original PR description
Purpose of the commit is to prevent the hierarchical name of category in search panel. So in this commit, Override the the name_get to prevent the category hierarchy on search panel and we already displaying parent category separately in search panel. TaskID: 2417252 Related PR: https://github.com/odoo/enterprise/pull/15550
Website editors now see realistic sample content when a fully configured dynamic snippet has no live data yet, instead of an empty section. This makes page building easier by showing how product or website content blocks will look once real records become available.
Original PR description
Before this commit when a dynamic snippet was fully configured but returned no data, the rendered section remained empty in edit mode. After this commit when a dynamic snippet is fully configured but has no data to display, some sample data is generated in edit mode to give a feel of how the page will look like when data will be available. This commit of merge refactor also the way to get the data to render. We split function to handle data and convert / escape it. The default structure is now simplified and an helper to_generic exists to allow generic template to be used with indexed list. An other PR is coming to change the data getter, and have more generic function to merge 'Recently Viewed' in the "Dynamic products' snippet. task-2446024 PR: https://github.com/odoo/odoo/pull/65176
Demo field service tasks planned for today or future dates now appear only in the new stage instead of being marked as done. This makes sample data reflect realistic upcoming work and avoids confusion when reviewing field service tasks.
Original PR description
Initially, the tasks were stored in both the done stage and the new stage whether it is planned for today or for future, but now these tasks are only stored in new stage but not in done stage. TaskID : 2445906
Field service users can now browse products by category when adding items to a task, making it faster to find the right product in large catalogs. The mobile search panel also shows selected category paths in the correct order, improving navigation clarity.
Original PR description
Purpose of the task is, It is not easy to find the right product when they are hundreds of them so a search panel on product category would help the user quickly access the products. So in this commit, Added a search panel on product category when going to add the product on fsm task. TaskID: 2417252 Related PR: odoo/odoo#65442
The subscription list view now shows fewer columns by default, making it easier for users to focus on the most relevant information. Additional fields can be optionally displayed when needed, improving day-to-day usability without removing access to details.
Original PR description
Before this commit, many columns were visible by default and were not optional. taskid: 2443251
Resolved issues and error corrections
This fix makes Odoo's JavaScript processing more reliable when files have special characters in their names and when module markers use common spacing formats. It reduces the risk of valid JavaScript assets being missed or processed incorrectly during builds.
Original PR description
Change two regex:
Handles now special chars in file url
Fix problem in the regex for the @odoo-module detection
Add tests:
Creation of a new file for regex white box tests
Add tests for both modified regexMiscellaneous changes
In some location, a long unbreakable word would cause following columns to be hidden (depending on size of unbreakable word, font, font size, ...). For example, this happened in the cart summary on payment page. With this changeset, if not possible otherwise, line break happen inside the word. opw-2451496 Forward-Port-Of: odoo/odoo#66191 Forward-Port-Of: odoo/odoo#66176
Original PR description
In some location, a long unbreakable word would cause following columns to be hidden (depending on size of unbreakable word, font, font size, ...). For example, this happened in the cart summary on payment page. With this changeset, if not possible otherwise, line break happen inside the word. opw-2451496 Forward-Port-Of: odoo/odoo#66191 Forward-Port-Of: odoo/odoo#66176
Checkbox fields that reveal optional follow-up fields now display correctly on mobile screens. This improves form readability and alignment in Payroll, Planning, Accounting Assets, and related fleet contract workflows.
Original PR description
This PR adapts a class to be able to show/hide other fields depending on a checkbox status. This class is needed to have this behavior on desktop but also on mobile. We can now fix some alignment issues encountered on mobile. Related task-ID: 1929043
In a4d170ad9 there were some improvment to not show event totally empty on the day calendar view because of different style (font + padding). The lower part of the text was still a little cut, this commit try to improve this for week and day view mode by removing 5 additional pixels. opw-2422700 Forward-Port-Of: odoo/odoo#66091 Forward-Port-Of: odoo/odoo#66078
Original PR description
In a4d170ad9 there were some improvment to not show event totally empty on the day calendar view because of different style (font + padding). The lower part of the text was still a little cut, this commit try to improve this for week and day view mode by removing 5 additional pixels. opw-2422700 Forward-Port-Of: odoo/odoo#66091 Forward-Port-Of: odoo/odoo#66078
- Install event_sale; - On the Sale's settings check 'Sale Warning'; - Create a blocking message for a product; - Create a SO; - Add the product with the blocking message. Before this commit, a traceback was raised before the blocking message is shown. Now, only the blocking message is shown. opw-2458568 Forward-Port-Of: odoo/odoo#66159
Original PR description
- Install event_sale; - On the Sale's settings check 'Sale Warning'; - Create a blocking message for a product; - Create a SO; - Add the product with the blocking message. Before this commit, a traceback was raised before the blocking message is shown. Now, only the blocking message is shown. opw-2458568 Forward-Port-Of: odoo/odoo#66159
PURPOSE When there is a horizontal scroll and user scrolls horizontally and go to other view(form view by clicking any record) and comeback to previous view then horizontal scroll is not preserved SPEC Scrolling horizontally and then go to form view and come back to previous view should preserve scroll position. Also consider case for kanban view where there are too many columns and user click on 'Add Column' user should be scrolled to new column element. TASK 2418275 -- I confi
Original PR description
PURPOSE When there is a horizontal scroll and user scrolls horizontally and go to other view(form view by clicking any record) and comeback to previous view then horizontal scroll is not preserved SPEC Scrolling horizontally and then go to form view and come back to previous view should preserve scroll position. Also consider case for kanban view where there are too many columns and user click on 'Add Column' user should be scrolled to new column element. TASK 2418275 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#66143 Forward-Port-Of: odoo/odoo#63933
PURPOSE When searchbar has autocomplete and user press Tab key then focus goes out of searchbar input while it should keep focus on searchbar so that user can do search on other term. SPEC When searching on searchbar and pressing Tab key should keep focus on searchbar input so that user can search again. TASK 2393772 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 an
Original PR description
PURPOSE When searchbar has autocomplete and user press Tab key then focus goes out of searchbar input while it should keep focus on searchbar so that user can do search on other term. SPEC When searching on searchbar and pressing Tab key should keep focus on searchbar input so that user can search again. TASK 2393772 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#64471
Before this commit the loader did not always get displayed when switching to the options tab. After this commit the loader always gets displayed ASAP when switching to the options tab until the tab is ready and displayed. task-2439295 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#65223
Original PR description
Before this commit the loader did not always get displayed when switching to the options tab. After this commit the loader always gets displayed ASAP when switching to the options tab until the tab is ready and displayed. task-2439295 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#65223
Before this commit, only whitelisted fields would be updated on cow views during a module update. A field would be whitelisted if he had the same value than the original view, see it as a heuristic to not write on modified fields. But `inherit_id` is not that simple, even if the cow view has a different value than its original view, it doesn't mean it was modified by the user, it is just because of the cow mechanism that assigned a copied view as inherit_id, which is just a copy ofthe o
Original PR description
Before this commit, only whitelisted fields would be updated on cow views during a module update. A field would be whitelisted if he had the same value than the original view, see it as a heuristic…
Before this commit, only whitelisted fields would be updated on cow views
during a module update.
A field would be whitelisted if he had the same value than the original view,
see it as a heuristic to not write on modified fields.
But `inherit_id` is not that simple, even if the cow view has a different value
than its original view, it doesn't mean it was modified by the user, it is just
because of the cow mechanism that assigned a copied view as inherit_id, which
is just a copy ofthe original one.
We can thus consider `inherit_id` as unchanged and whitelist it if the `key` is
the same.
In practice, it means that cow'd views did not receive the `inherit_id` updates
as in commit c857756#diff-823e5db841dca1798ff1300e243059a4e1c93343598d2be5a1d1dcd1d2d0c273R537
where `portal.my_account_link` had its `inherit_id` changed from
`portal.frontend_layout` to `portal.user_dropdow`, see odoo/upgrade#2059:
Considering a module update changing `inherit_id` of D from A to B, the
following use cases are expected. Without this fix, D' never move:
```
CASE 1
A A' B A A' B
| | => / \
D D' D D'
CASE 2
A A' B B' A A' B B'
| | => | |
D D' D D'
CASE 3
A B A B
/ \ => / \
D D' D D'
CASE 4
A B B' A B B'
/ \ => | |
D D' D D'
```
Forward-Port-Of: odoo/odoo#65979
Forward-Port-Of: odoo/odoo#64446In some location, a long unbreakable word would cause following columns to be hidden (depending on size of unbreakable word, font, font size, ...). For example, this happened in the cart summary on payment page. With this changeset, if not possible otherwise, line break happen inside the word. opw-2451496 Forward-Port-Of: odoo/odoo#66176
Original PR description
In some location, a long unbreakable word would cause following columns to be hidden (depending on size of unbreakable word, font, font size, ...). For example, this happened in the cart summary on payment page. With this changeset, if not possible otherwise, line break happen inside the word. opw-2451496 Forward-Port-Of: odoo/odoo#66176
The company is used to compute currency of: - discount_fixed_amount - discount_max_amount - rule_minimum_amount If currently we don't set a company, we have an error when using the company. opw-2458950 Forward-Port-Of: odoo/odoo#66210
Original PR description
The company is used to compute currency of: - discount_fixed_amount - discount_max_amount - rule_minimum_amount If currently we don't set a company, we have an error when using the company. opw-2458950 Forward-Port-Of: odoo/odoo#66210
Create a product with variants attributes that NEVER create variants. Configure Variants to add some extra-prices (1$) to some variants. In POS settings activate "Product Configurator" and "Advanced Pricelists", add the public pricelist and one that applies 50% to the product. Open a session and select the product created (say price = 1$) Select the attributes, the extra-price is added to the product (say the total price now is 2$). Change pricelist from public to 50% and the order li
Original PR description
Create a product with variants attributes that NEVER create variants. Configure Variants to add some extra-prices (1$) to some variants. In POS settings activate "Product Configurator" and "Advanced Pricelists", add the public pricelist and one that applies 50% to the product. Open a session and select the product created (say price = 1$) Select the attributes, the extra-price is added to the product (say the total price now is 2$). Change pricelist from public to 50% and the order line will show our product = 1@50% + 1 = 1.50, not applying the pricelist to the extra-price opw-2439445 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#66198 Forward-Port-Of: odoo/odoo#65711
Fixes #65706 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#65774 Forward-Port-Of: odoo/odoo#65742
Original PR description
Fixes #65706 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#65774 Forward-Port-Of: odoo/odoo#65742
Forward-Port-Of: odoo/odoo#66171
Original PR description
Forward-Port-Of: odoo/odoo#66171
task-2172312 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#65055
Original PR description
task-2172312 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#65055
In "Inventory Valuation", when click "Inventory at Date" then "confirm". Record for consumable products will be shown in the report. Previously fix in #62622 which disabled svl for consumable products, then rolled back in #63386 due to mrp need to create svl for consumables to analyse cost. In this commit, we add a domian filter to not show consumables in "Inventory Valuation" Task 2449211 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/subm
Original PR description
In "Inventory Valuation", when click "Inventory at Date" then "confirm". Record for consumable products will be shown in the report. Previously fix in #62622 which disabled svl for consumable products, then rolled back in #63386 due to mrp need to create svl for consumables to analyse cost. In this commit, we add a domian filter to not show consumables in "Inventory Valuation" Task 2449211 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#66062 Forward-Port-Of: odoo/odoo#65726
Before this commit, the preview of the dragged snippet didn't work when moving a dragged snippet from a drop zone to an other drop zone when there was no space between those drop zones. It is because, in this case, the over event of the second drop zone is triggered before the out event of the first drop zone. task-2312878 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
Before this commit, the preview of the dragged snippet didn't work when moving a dragged snippet from a drop zone to an other drop zone when there was no space between those drop zones. It is because, in this case, the over event of the second drop zone is triggered before the out event of the first drop zone. task-2312878 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#66165 Forward-Port-Of: odoo/odoo#66148
Use a custom Cartesian product implementation to generate variant combinations in order to be able to skip incompatible attribute values without having to generate the full variant. It's necessary because some customers have products with MANY attributes and filtering through invalid combinations takes ages. This meant that the variant configurator would time out. opw-2335936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo
Original PR description
Use a custom Cartesian product implementation to generate variant combinations in order to be able to skip incompatible attribute values without having to generate the full variant. It's necessary because some customers have products with MANY attributes and filtering through invalid combinations takes ages. This meant that the variant configurator would time out. opw-2335936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#65723 Forward-Port-Of: odoo/odoo#65089
In a4d170ad9 there were some improvment to not show event totally empty on the day calendar view because of different style (font + padding). The lower part of the text was still a little cut, this commit try to improve this for week and day view mode by removing 5 additional pixels. opw-2422700 Forward-Port-Of: odoo/odoo#66078
Original PR description
In a4d170ad9 there were some improvment to not show event totally empty on the day calendar view because of different style (font + padding). The lower part of the text was still a little cut, this commit try to improve this for week and day view mode by removing 5 additional pixels. opw-2422700 Forward-Port-Of: odoo/odoo#66078
Use a custom Cartesian product implementation to generate variant combinations in order to be able to skip incompatible attribute values without having to generate the full variant. It's necessary because some customers have products with MANY attributes and filtering through invalid combinations takes ages. This meant that the variant configurator would time out. opw-2335936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo
Original PR description
Use a custom Cartesian product implementation to generate variant combinations in order to be able to skip incompatible attribute values without having to generate the full variant. It's necessary because some customers have products with MANY attributes and filtering through invalid combinations takes ages. This meant that the variant configurator would time out. opw-2335936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#65798 Forward-Port-Of: odoo/odoo#65089
Use a custom Cartesian product implementation to generate variant combinations in order to be able to skip incompatible attribute values without having to generate the full variant. It's necessary because some customers have products with MANY attributes and filtering through invalid combinations takes ages. This meant that the variant configurator would time out. opw-2335936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo
Original PR description
Use a custom Cartesian product implementation to generate variant combinations in order to be able to skip incompatible attribute values without having to generate the full variant. It's necessary because some customers have products with MANY attributes and filtering through invalid combinations takes ages. This meant that the variant configurator would time out. opw-2335936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#65802 Forward-Port-Of: odoo/odoo#65089
**Current behavior before PR:** If a next activity is "triggered", the discard button is not visible. **Desired behavior after PR is merged:** Even if a next activity is "triggered", the discard button will visible. **LINKS:** PR #66164 Task-2459645 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#66164
Original PR description
**Current behavior before PR:** If a next activity is "triggered", the discard button is not visible. **Desired behavior after PR is merged:** Even if a next activity is "triggered", the discard button will visible. **LINKS:** PR #66164 Task-2459645 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#66164
**Current behavior before PR:** When chat window is focused odoo shortcuts (with alt) did not work because of there is stop propagation in _onKeydown method. **Desired behavior after PR is merged:** Remove stop propagation. Now odoo shortcuts (with alt) work properly. **LINKS:** PR #65478 Task-2388829 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#65478
Original PR description
**Current behavior before PR:** When chat window is focused odoo shortcuts (with alt) did not work because of there is stop propagation in _onKeydown method. **Desired behavior after PR is merged:** Remove stop propagation. Now odoo shortcuts (with alt) work properly. **LINKS:** PR #65478 Task-2388829 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#65478
Issue - Install 'Calendar' module - Create new event from Calendar view - Edit event - Set True to 'Recurrent' in options tab - Repeat every 2 weeks - Until : Number of repetitions 2 - Save and go back to calendar view - Events are shifted (+ 1 week) Cause The rrule.rrule (who create the generator with the recurrence ranges dates) use by default `calendar.firstweekday()` as first week day ('wkst'). Solution If recurrence frequency is 'weekly', get first week d
Original PR description
Issue
- Install 'Calendar' module
- Create new event from Calendar view
- Edit event
- Set True to 'Recurrent' in options tab
- Repeat every 2 weeks
- Until : Number of repetitions 2
- Save and go back to calendar view
- Events are shifted (+ 1 week)
Cause
The rrule.rrule (who create the generator with the recurrence ranges dates) use
by default `calendar.firstweekday()` as first week day ('wkst').
Solution
If recurrence frequency is 'weekly', get first week day based on user language,
and add it as param ('wkst') to the rrule.rrule.
https://dateutil.readthedocs.io/en/stable/rrule.html#classes
opw-2448325
Co-authored-by: LucasLefevre (lul) <lul@odoo.com>
Forward-Port-Of: odoo/odoo#66265In some location, a long unbreakable word would cause following columns to be hidden (depending on size of unbreakable word, font, font size, ...). For example, this happened in the cart summary on payment page. With this changeset, if not possible otherwise, line break happen inside the word. opw-2451496 Forward-Port-Of: odoo/odoo#66204 Forward-Port-Of: odoo/odoo#66176
Original PR description
In some location, a long unbreakable word would cause following columns to be hidden (depending on size of unbreakable word, font, font size, ...). For example, this happened in the cart summary on payment page. With this changeset, if not possible otherwise, line break happen inside the word. opw-2451496 Forward-Port-Of: odoo/odoo#66204 Forward-Port-Of: odoo/odoo#66176
In some location, a long unbreakable word would cause following columns to be hidden (depending on size of unbreakable word, font, font size, ...). For example, this happened in the cart summary on payment page. With this changeset, if not possible otherwise, line break happen inside the word. opw-2451496 Forward-Port-Of: odoo/odoo#66194 Forward-Port-Of: odoo/odoo#66176
Original PR description
In some location, a long unbreakable word would cause following columns to be hidden (depending on size of unbreakable word, font, font size, ...). For example, this happened in the cart summary on payment page. With this changeset, if not possible otherwise, line break happen inside the word. opw-2451496 Forward-Port-Of: odoo/odoo#66194 Forward-Port-Of: odoo/odoo#66176
Steps: - Make sure your company is in the United States - Install eCommerce. - Set up TaxCloud credentials Follow this doc to be sure: https://www.odoo.com/documentation/user/14.0/accounting/fiscality/taxes/taxcloud.html - Go to Invoicing > Configuration > Fiscal Positions - Edit Fiscal Position for United States: - Detect Automatically: checked - Go to Customers > Products - Edit a Product (1): - TaxCloud category: Select one - Log out - Go on the website shop - Add (1) to
Original PR description
Steps: - Make sure your company is in the United States - Install eCommerce. - Set up TaxCloud credentials Follow this doc to be sure:…
Steps: - Make sure your company is in the United States - Install eCommerce. - Set up TaxCloud credentials Follow this doc to be sure: https://www.odoo.com/documentation/user/14.0/accounting/fiscality/taxes/taxcloud.html - Go to Invoicing > Configuration > Fiscal Positions - Edit Fiscal Position for United States: - Detect Automatically: checked - Go to Customers > Products - Edit a Product (1): - TaxCloud category: Select one - Log out - Go on the website shop - Add (1) to the cart - Checkout the cart - Enter an address: - Zip: 49105 - State: Massachusetts - Try to process the payment Bug: Error 500 here: https://github.com/odoo/enterprise/blob/90204abeb4b2af312101320cbcb6973a69908c21/sale_account_taxcloud/models/sale_order.py#L44 Explanation: The error is not caught. This commit prevents the user from entering an invalid address when buying a TaxCloud product. Since the actual error is not intended to be displayed to a public user, a more abstract message is displayed instead. opw:2347980 Forward-Port-Of: odoo/enterprise#16376 Forward-Port-Of: odoo/enterprise#16301
Before this commit, if the delivery address was on Mexico, an error was raised when signing the CFDI document. Now, the document is signed correctly. opw-2427677 Forward-Port-Of: odoo/enterprise#16374 Forward-Port-Of: odoo/enterprise#16293
Original PR description
Before this commit, if the delivery address was on Mexico, an error was raised when signing the CFDI document. Now, the document is signed correctly. opw-2427677 Forward-Port-Of: odoo/enterprise#16374 Forward-Port-Of: odoo/enterprise#16293
The mws lib is missing in the packages because __init__.py file does not exists and therefore not recognized as a Python module. Forward-Port-Of: odoo/enterprise#16371 Forward-Port-Of: odoo/enterprise#16357
Original PR description
The mws lib is missing in the packages because __init__.py file does not exists and therefore not recognized as a Python module. Forward-Port-Of: odoo/enterprise#16371 Forward-Port-Of: odoo/enterprise#16357
Accounting -> Configuration -> Follow up levels -> open "First reminder email" and check "Join open Invoices" Go to Accounting -> Customers -> Follow-up Reports -> open the only one "Deco Addict" -> check "Excluded" for INV/2021/0004 Click on "Print Letter" and open PDF -> the first page is correctly excluding the invoice, but it is still attached in the next pages while it should not. opw-2339917 Forward-Port-Of: odoo/enterprise#16324 Forward-Port-Of: odoo/enterprise#16213
Original PR description
Accounting -> Configuration -> Follow up levels -> open "First reminder email" and check "Join open Invoices" Go to Accounting -> Customers -> Follow-up Reports -> open the only one "Deco Addict" -> check "Excluded" for INV/2021/0004 Click on "Print Letter" and open PDF -> the first page is correctly excluding the invoice, but it is still attached in the next pages while it should not. opw-2339917 Forward-Port-Of: odoo/enterprise#16324 Forward-Port-Of: odoo/enterprise#16213
Before this commit, when there too many lines on the reconciliation widget, the 'load more' button wasn't shown. On b2dd65b9a9c054570d5796a81f2c390c4d8cb6c4 recs_count was removed, but it's used on https://github.com/odoo/enterprise/blob/f119f117dde1c8901b73575cd725501aad57c86f/account_accountant/static/src/js/reconciliation/reconciliation_renderer.js#L364 to show or hide the 'load more' button, and to complete the text. Now, the load more button is correctly shown. opw-2447384 Forw
Original PR description
Before this commit, when there too many lines on the reconciliation widget, the 'load more' button wasn't shown. On b2dd65b9a9c054570d5796a81f2c390c4d8cb6c4 recs_count was removed, but it's used on https://github.com/odoo/enterprise/blob/f119f117dde1c8901b73575cd725501aad57c86f/account_accountant/static/src/js/reconciliation/reconciliation_renderer.js#L364 to show or hide the 'load more' button, and to complete the text. Now, the load more button is correctly shown. opw-2447384 Forward-Port-Of: odoo/enterprise#16267
PURPOSE View switcher icon for Activity view is not the same as an icon displayed in studio mode, both icons should be the same in non-studio mode as well as studio mode. SPEC Use fa-clock-o as activity view icon. TASK 2376354 Forward-Port-Of: odoo/enterprise#16313 Forward-Port-Of: odoo/enterprise#15092
Original PR description
PURPOSE View switcher icon for Activity view is not the same as an icon displayed in studio mode, both icons should be the same in non-studio mode as well as studio mode. SPEC Use fa-clock-o as activity view icon. TASK 2376354 Forward-Port-Of: odoo/enterprise#16313 Forward-Port-Of: odoo/enterprise#15092