Wednesday, September 18, 2024
84 changes · master
Enhancements to existing features
This update makes a minor usability improvement in the Sales area, helping users work with sales orders more smoothly. It is a low-risk change intended to reduce friction in day-to-day sales operations without changing core business logic.
Original PR description
task-3750550
The restaurant floor plan no longer shows or increases the black order-count badge on tables when multiple orders are created from different POS screens. This reduces confusion for restaurant staff by avoiding misleading table indicators.
Original PR description
Before this commit: =================== Initially, If I place the order from the frontend then it will show the black badge on the floor plan for the specific table, similarly, if I place another order for the same table from the ticket screen then it will increment the current black badge count on the floor plan After this commit: ==================== As of now, If we do the order from the frontend and also do the order from the ticket screen, it will create multiple orders and increment the black badge that we don't want. To prevent this behavior we are removing the black badge task - 4138483
Message reactions are now shown from oldest to newest when loaded from the server. This makes conversation activity easier to follow and ensures users see reactions in a consistent, predictable order.
Original PR description
This commit ensures that message reactions are displayed in chronological order, from the earliest to the most recent when getting the data from the server. https://github.com/odoo/enterprise/pull/70042 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Accounting records can now more easily expose their currency code, such as identifying Euro transactions. This supports current and future payment-related improvements, including SEPA Direct Debit handling, with minimal direct impact on users.
Original PR description
During SEPA Direct Debit refactoring, the need to check a move or payment currency to be in Euros arose. We add the related field to the base account module, as it may be required by other child modules later task-id: 3722517 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes an unused internal mail component that is no longer needed. It helps keep the codebase cleaner and easier to maintain without changing how users experience the system.
Original PR description
`message.now` isn't used anywhere any more.
This update adds an internal identifier to the sales team commission section, making it easier for future customizations or extensions to target that part of the screen reliably. There is no expected change for day-to-day users, but it improves maintainability for sales-related configurations.
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
When a cashier creates a new customer in Point of Sale, the system now selects that customer automatically. This removes an extra manual step, making checkout and customer assignment faster and less error-prone.
Original PR description
Before this commit, after creating a new partner, the user had to manually select it from the list of partners. This commit makes the system automatically select the newly created partner.
Test cases that intentionally trigger retry behavior now keep those expected retry messages out of build logs. This reduces noise on build pages and makes it easier for teams to spot real issues during test runs.
Original PR description
Some tests are written to assert the retry mechanism behaviors , but the retry caused by those test will be emit in level 25 and appears on the build page. Patching the logging runbot method to silent the retry in this case.
The passkey-related user cards have been simplified to use newer interface building blocks and cleaner layout conventions. This makes the views easier to maintain while preserving the same user experience for managing passkeys.
Original PR description
In this commit we have simplified the kanban arch for the auth_passkey. The goal is to simplify them, make them easier to read, and use bootstrap utility classnames. - Previously, we used `kanban-box`, but now we are using `kanban-card` instead. - Deprecated `oe_kanban_global_click` and `oe_kanban_global_click_edit`. - More use of `<field/>` tags - Removed the `oe_kanban_colorpicker` class and replaced it with the `kanban_color_picker` widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - `kanban_image` from rendering context, is deprecated so we use `<field name=... widget=image/>` instead Task-3992107
Scheduled background tasks that only need to process a fixed set of records can now mark themselves as finished and deactivate automatically. This helps avoid unnecessary repeated runs once there is no more work to do, improving operational efficiency and reducing background noise.
Original PR description
Some crons needs to process a finite number of records. When finished, we need a way to deactivate the cron.
The Incoterms menu in Accounting is now hidden during normal use and only appears when debug mode is enabled. This keeps everyday accounting menus simpler while preserving access for advanced configuration or troubleshooting.
Original PR description
This Pr will put the menu item of incoterm in debug mode only Task: 4192465 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Administrators now have a dedicated menu to configure embedded actions alongside other technical action settings. This makes the option easier to find and manage, improving configuration workflows without changing everyday user behavior.
Original PR description
This commit adds a menu for the configuration of embedded actions next to the other technical action settings. task-4184488
The Point of Sale interface no longer shows an expand button on form dialogs because that action is not supported there. This avoids presenting users with a control that cannot work, making the POS experience clearer and less confusing.
Original PR description
Before the expand button was displayed on form view when opening it from PoS, but this fonctionnality is not handled in POS, so it's better to remove it.
The message composer in dark mode now uses a slightly darker background, reducing visual distraction while users read messages. This makes the messaging area feel more balanced and comfortable without changing the light theme.
Original PR description
There was too much contrast between message list and composer, making composer too distracting when reading messages. This commit fixes issue by slightly darkening composer background in dark theme. White theme is unchanged and is still white. Before <img width="511" alt="Screenshot 2024-09-18 at 17 10 53" src="https://github.com/user-attachments/assets/ebfd4dfd-bf96-470d-804a-6716ca83eeac"> After <img width="509" alt="Screenshot 2024-09-18 at 17 10 48" src="https://github.com/user-attachments/assets/7566f806-203d-4596-8a4b-a64d5457ad8d">
This update modernizes automated testing for the mobile calendar view. It helps Odoo maintain the calendar experience more reliably without changing day-to-day user workflows.
Original PR description
task-4028335 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 project module’s automated tests were updated to use a newer testing framework and no longer rely on older mail testing helpers. This is an internal quality improvement that helps keep testing infrastructure current without changing user-facing project features.
Original PR description
Purpose of this PR: To convert QUnit tests which depends on mail/test_utils to hoot. part of: 3818666
Advanced configuration menu items for tax units, horizontal report groups, and 1099 boxes are now shown only in debug mode. This keeps everyday menus simpler while still allowing administrators and support teams to access specialized setup options when needed.
Original PR description
This Pr will put different menu item in debug mode: - Tax unit - Horizontal group - 1099 boxes Task: 4192465
Appointment and website appointment dashboard cards were simplified to use newer Odoo interface building blocks. This makes the screens easier to maintain and keeps the appointment experience aligned with current platform standards, with minimal change for end users.
Original PR description
In this commit we have simplified the kanban arch for the appointment and it's related module dashboard. The goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of <field/> tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use <field name="..." widget="image"/> instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color="color_field_name" on root node Task-3992107
The Quality Control dashboard layout was cleaned up to use newer Odoo interface patterns. This makes the dashboard easier to maintain and helps keep the user experience consistent with current Odoo standards.
Original PR description
In this commit we have simplified the kanban arch for the quality_control module dashboard. the goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of `<field/>` tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use `<field name=... widget=image/>` instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color=color_field_name on root node Task-3992107
The POS preparation and order tracking dashboard layouts were cleaned up to use newer interface building blocks. This makes the screens easier to maintain and keeps them aligned with current Odoo standards, with little expected change for everyday users.
Original PR description
In this commit we have simplified the kanban arch for the pos_preparation_display module dashboard. the goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of `<field/>` tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use `<field name=... widget=image/>` instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color=color_field_name on root node Task-3992107
Message reactions are now shown from oldest to newest when loaded from the server. This makes conversation history easier to follow and keeps reaction displays consistent for users.
Original PR description
This commit ensures that message reactions are displayed in chronological order, from the earliest to the most recent when getting the data from the server. https://github.com/odoo/odoo/pull/180198
Resolved issues and error corrections
This fixes Odoo's test setup so web-based tests can run correctly when the system is asked to choose an available port automatically. It improves reliability for developers and QA teams running automated tests, without changing business features or end-user behavior.
Original PR description
While it's possible to run Odoo with `-p 0`, previously the test suite would then generate URLs with a port of 0, means the http tests were unable to get the server's port and connect to it. By retrieving the actual port the server is bound to, we can run http tests / tours with `-p 0` and things will work correctly, even tour watching / debugging should work correctly.
Code cleanup and technical improvements
This update improves the internal structure of the HTML editor by adding type information to its static resources. It helps developers maintain the editor more safely and reduces the chance of future errors, without changing the user-facing editing experience.
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Currently, an exception was generated when the user added a dynamic filter like 'Recently Sold Products', 'Accessories for Product', or 'Products Recently Sold With Product' to the product website view and tried to preview archived products from website. Steps to produce: 1. Create a product with Alternative Products from the sales tab. 2. Archive this product 3. Click on Go to Website Icon >> error occurs Error: `TypeError: int() argument must be a string, a bytes-like object or a
Original PR description
Currently, an exception was generated when the user added a dynamic filter like 'Recently Sold Products', 'Accessories for Product', or 'Products Recently Sold With Product' to the product website…
Currently, an exception was generated when the user added a dynamic filter like 'Recently Sold Products', 'Accessories for Product', or 'Products Recently Sold With Product' to the product website view and tried to preview archived products from website. Steps to produce: 1. Create a product with Alternative Products from the sales tab. 2. Archive this product 3. Click on Go to Website Icon >> error occurs Error: `TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'` This is because we receive 'product_template_id' as None, and when [1] tries to convert it onto Integer, it will generate an exception. With the recently merged https://github.com/odoo/odoo/commit/d526b6c70bcf21bf84be83615daefee5ad972d14, added this code but not handled case with product_template_id as None. This commit will resolve the above issue by setting 'current_template' as false when `current_template` is None. [1] - https://github.com/odoo/odoo/blob/2aa4ee0d66af8079694a42b84d341fe118f12c0b/addons/website_sale/models/website_snippet_filter.py#L216 sentry-5704306029 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179845
This fix makes several automated tests run with predictable pricing settings, avoiding failures caused by optional pricelist and multi-currency configurations. It helps keep validation stable across sales, timesheet, events, loyalty, and delivery scenarios without changing customer-facing behavior.
Original PR description
Because runbot always runs post_install tests with multi-currency pricelists enabled (because it installs `l10n_be` which activates the EUR currency, which enables multi-currency, which through `product` enables pricelists) some tests don't cope well with pricelists / multi-currency not being enabled, enable the pricelists feature for those which require it. Furthermore, because it's possible for pricelists to exist even though the feature is not enabled some tests will correctly handle either there being no pricelists or there being a default pricelist, but not the intermediate state where pricelists are disabled *but* `pos_pricer` has been installed and has created a weirdo universally applicable pricelist with a 20% discount, which causes lookups for specific prices to fail (as the final price is 20% lower than looked for). Fix those tests by deleting all pricelists before they run.
This change standardizes how spaces are treated in selected automated tests for dates and monetary values. It helps prevent test failures caused by differences in supporting software versions, improving development reliability without changing user-facing behavior.
Original PR description
Date and monetary formatting can lead to "interesting" whitespace depending on dependencies and all, and their versions. Normalise whitespace to alias NBSP and SP in a few tests which otherwise may fail depending on the babel version.
The Point of Sale app now only switches to offline mode when the connection is actually lost. This prevents regular server errors from being misinterpreted as connectivity problems, reducing confusion for cashiers and staff.
Original PR description
When catching an error in the execute method, `setOffline` is called no matter the error. But in case of an RPCError, it doesn't make sense. The fix here, is to call `setOffline` only when we have a `ConnectionLostError`.
This fix improves how early payment discount messages appear in customer portal invoices, making them easier to translate and clearer for customers. It also corrects the payment reference when a customer pays the full invoice amount and standardizes the wording of “Left to Pay.”
Original PR description
In the previous commit https://github.com/odoo/odoo/commit/67e2270d56a81d385db3ca27d29fa3945501fca8, when using early payment discounts, a discount message is now displayed on the portal view.…
In the previous commit https://github.com/odoo/odoo/commit/67e2270d56a81d385db3ca27d29fa3945501fca8, when using early payment discounts, a discount message is now displayed on the portal view. However, the translation of this message is not optimal, and this commit aims to fix it. For example, in Dutch Korting van € 100 indien vandaag betaald Korting van € 100 indien betaald binnen 10 dagen In the first case, "betaald" is after "today" while in the second case, it is before the "within 10 days" Also, for consistency, turns this string "Left to pay" into title-case "Left to Pay" Also, fixes the "Reference" in the portal payment wizard when paying the full amount. It was displayed the same reference as when paying only the installment, but with the full amount, the invoice name should be used as the reference. task-4193178 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 fixes a timing issue where website editing or translation options could appear before the page was fully ready, causing automated checks to fail. The menu now waits until the website is prepared, making the editing experience more reliable without changing normal user workflows.
Original PR description
With enough modules installed, the edit / translate menu can appear before the `websiteRootInstance` is loaded, which suppresses the switch to translation mode (tours are pretty prototypical "clicks too fast" users), which fails step "Check has error dialog" as there is no error since we didn't even attempt to switch to edition mode. - Update the tour to only click the edit button if it's a dropdown. - Update the `translatable` flag to check if the website root instance is ready, this way `Edit > Translate` is only accessible if the public root is loaded. - Remove the suppression condition, which should now be unnecessary. - Simplify the tail code a bit.
Tour sharing links are now generated from the tour name instead of depending on a page URL. This prevents missing share links when a tour has no URL, making tour sharing more reliable for users.
Original PR description
Before this commit, the sharing_url was compute on url and was not set if there was no url. But the sharing url doesn't depend on the url, but the name. Now, the sharing_url depends on name. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A test tour for merging accounts has been moved to the Accountant app, where the needed Chart of Accounts view is available. This helps keep automated checks reliable and prevents false failures in accounting workflows.
Original PR description
The tour needs access to the Chart of Accounts list view to function, which is enabled only in `accountant`, so we move it there. Enterprise PR: https://github.com/odoo/enterprise/pull/70237 runbot-98348
This fix adds a broader validation for batch size handling in manufacturing procurement. It helps prevent invalid production planning values from being used in multiple places, reducing the risk of manufacturing process errors.
Original PR description
We want to use batch_size in multiple places, so it's better to have a check at a more global level in addition to local checks. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change corrects an internal test that was not actually verifying the intended access-rights behavior because cached data was not refreshed. It makes the test more reliable by using a dedicated template and test group, helping prevent future regressions in permission-related behavior.
Original PR description
The test check nothing. It's just the debug mode, the field group are not tested because the cache is never invalidate. Update the test to use a new template, and a test_group instead of the debug mode and an existing group from data.
The Discuss sidebar now aligns notification badges more neatly with the category action buttons. This small visual fix makes the messaging interface look cleaner and easier to scan without changing functionality.
Original PR description
Before / After <img width="298" alt="Screenshot 2024-09-18 at 15 12 57" src="https://github.com/user-attachments/assets/7876591b-1320-49ea-b485-b69cb6a3ad4e"> <img width="301" alt="Screenshot 2024-09-18 at 15 10 32" src="https://github.com/user-attachments/assets/9f1ea6c0-7791-4be6-b61a-733f2510100d">
Links shown inside Point of Sale web dialogs now open in a new dialog instead of silently closing or doing nothing. This helps users navigate related records, such as sessions from POS orders, without losing their workflow.
Original PR description
The action service wants to open the majority of links in the main container, not in new dialog. The problem is that in pos we don't have the main container, so the links are simply not opened. This is a workaround to always open links in new dialogs. Example: Click on the `session` link in the `pos.order` form view and observe the fact that the dialog simply closes.  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Restores the missing Print & Send action in the refund list view after it was accidentally omitted during a previous button relocation. This lets users print and send refund documents directly from the list again, reducing workflow disruption.
Original PR description
With previous changes we moved the button "Print & Send" of place and forgot to re-add in in the refund list view. See https://github.com/odoo/odoo/commit/73c9fb48c5890f956a1bef1c271f3e954e5b5386 task-no
The chat window action buttons now show a clearer hover effect in dark theme. This makes the interface easier to read and use, aligning the chat experience with other parts of Odoo.
Original PR description
Dark theme actions hover effect was barely noticeable. This commit improves effect to match with other parts of UI such as composer actions. Before <img width="456" alt="Screenshot 2024-09-18 at 17 28 10" src="https://github.com/user-attachments/assets/41f06484-ed5e-41a6-b4c6-189fd69fd960"> After <img width="451" alt="Screenshot 2024-09-18 at 17 27 45" src="https://github.com/user-attachments/assets/8029bfff-653e-4bdb-8a9b-866ea41b9229">
Spreadsheet list side panels now wait for required list field information before rendering. This prevents missing or incomplete list details after updates, keeping spreadsheet views reliable for users.
Original PR description
This commit is the Enterprise counter-part of a community commit. Let me explain what's going on: Before the community commit, as soon as a list update was dispatched, it would trigger a new evaluation which would load the new (unloaded) datasource. The meta data (fields) being cached by the ServerData, fetching the fields was actually synchronous. Hence, at the next rendering, right after the command dispatch, the fields were already available. Now, with the community commit, there's a micro-tick delay before loading the new data source. The next rendering, being first in the event queue, renders the component before the cache was even queried. Task: 4134859
Manufacturing planning no longer blocks certain batch size settings during setup. If the batch size option is disabled or not set to a positive value, it is simply ignored when replenishment is run, reducing unnecessary configuration errors.
Original PR description
We do not impose restrictions on how batch_size is configured. It will simply be ignored if it's not enabled or is not something above zero.
The point of sale preparation display now loads the required sound resources for its notifications. This ensures staff can hear the expected alerts when orders or updates need attention.
Original PR description
In commit 45f568f8f8252913ed7cba00fe3da6f48edb7b26 we replaced the pos sound service with the mail sound service. In this commit we ensure that the correct assets are loaded in `pos_preparation_display`. The assets that handled the specific notifications used in pos were not loaded.
The EU OSS Reports module now avoids loading its test components during normal use. This prevents unnecessary internal test code from being imported in production, reducing the risk of avoidable startup or installation issues.
Original PR description
Test import was prevented by odoo/odoo#177671. Importing tests is only done when tests are enabled. This one was missed because it was merged concurrently.
The automated check for the account merge wizard has been moved into the Accountant app, where it can access the Chart of Accounts screen it needs. This helps ensure the test runs reliably and reduces false failures without changing day-to-day user behavior.
Original PR description
The tour needs access to the Chart of Accounts list view to function, which is available only in `accountant`, so we move it there from `account`. Community PR: https://github.com/odoo/odoo/pull/180614 runbot-98348
The Documents Kanban view has been corrected after a prior change caused visual layout issues. Users should now see better aligned footers, properly shortened text, correctly placed fields, and more consistent spacing when managing documents and accounting documents.
Original PR description
This commit fixes the broken Kanban view of documents, which occurred due to merging of this pr https://github.com/odoo/enterprise/pull/69250 . The following problems were addressed: - Misalignment of the footer - Text not being properly truncated - Incorrect positioning of a field using x-path - Inadequate padding Task-3992107
Several app onboarding walkthroughs were not starting because they were missing from setup files or absent entirely. This fix restores those tours so users can receive the intended guided introduction when using affected apps.
Original PR description
Some of the onboarding tour was missing in the manifest and some were not existing. They have been added. TASK-ID: 4184140
A typo was corrected in the Loans screen. This improves clarity for users and helps keep the interface polished without changing any business process or functionality.
Financial reports now avoid showing the word “False” where an account code is unavailable for the active company. This keeps report labels clearer and more professional by showing only the account name in those cases.
Original PR description
Since sharing accounts between companies in https://github.com/odoo/odoo/pull/171079, an account's code may be False from the perspective of the active company. In that case, we want only the account name to appear in reports. A fix was already done for `account.display_name` in https://github.com/odoo/odoo/pull/177943. This commit does a similar fix for reports which use code + name rather than display_name. taskid: none
pos*: point_of_sale, pos_hr, pos_loyalty, pos_restaurant, pos_self_order In this commit, we adapt the community code to the belgian restaurant certification. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179856
Original PR description
pos*: point_of_sale, pos_hr, pos_loyalty, pos_restaurant, pos_self_order In this commit, we adapt the community code to the belgian restaurant certification. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179856
This commit will set the deferred accounts for spain template. task: 4181499 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180004
Original PR description
This commit will set the deferred accounts for spain template. task: 4181499 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180004
The custom stock.move.line's x2many field computes a domain automatically for the SML that can be selected from the stock.move records (e.g. when trying to find a specific lot, etc. to fulfill a demand). This commit makes it possible to include the domain defined on the field in the final constructed domain, making it possible to somewhat customize this behaviour without the need for a js override. Task-4116000 ----------- Example of customization made possible with this: Have a com
Original PR description
The custom stock.move.line's x2many field computes a domain automatically for the SML that can be selected from the stock.move records (e.g. when trying to find a specific lot, etc. to fulfill a demand).
This commit makes it possible to include the domain defined on the field in the final constructed domain, making it possible to somewhat customize this behaviour without the need for a js override.
Task-4116000
-----------
Example of customization made possible with this:
Have a computed field `x_allowed_lot_ids` on the stock.move and restrict the selection of the lots to this domain by modifying the view `stock.view_stock_move_operations`:
```xml
<field name="move_line_ids" domain="[('lot_id', 'in', x_allowed_lot_ids)]" [...] widget="sml_x2_many"/>
```
without this commit, the `domain` attribute set on the field is simply ignored and it would require a more complex js custo (we could live with it)
Forward-Port-Of: odoo/odoo#180421On accounts from 14... to 19..., there are current liabilities while they should be non-current libialities. Manual forward-port of #178373 opw-4134510 Forward-Port-Of: odoo/odoo#180446
Original PR description
On accounts from 14... to 19..., there are current liabilities while they should be non-current libialities. Manual forward-port of #178373 opw-4134510 Forward-Port-Of: odoo/odoo#180446
This commit simplifies the labels on invoices in the Indian accounting localization package. task-4035245 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180374 Forward-Port-Of: odoo/odoo#172469
Original PR description
This commit simplifies the labels on invoices in the Indian accounting localization package. task-4035245 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180374 Forward-Port-Of: odoo/odoo#172469
Before this commit, when importing multiple leaves for different employee, the last employee in the list will be set as a follower on all the created leaves. This commit fixes this behavior by checking for the employee assigned to each leave and using its ID when adding the follower. opw-4023073 Forward-Port-Of: odoo/odoo#179872 Forward-Port-Of: odoo/odoo#178994
Original PR description
Before this commit, when importing multiple leaves for different employee, the last employee in the list will be set as a follower on all the created leaves. This commit fixes this behavior by checking for the employee assigned to each leave and using its ID when adding the follower. opw-4023073 Forward-Port-Of: odoo/odoo#179872 Forward-Port-Of: odoo/odoo#178994
Purpose of this PR: When a canned response have a long shortcut text, the text overflow the navigablelist. Before:  After:  Forward-Port-Of: odoo/odoo#180438
Original PR description
Purpose of this PR: When a canned response have a long shortcut text, the text overflow the navigablelist. Before:  After:  Forward-Port-Of: odoo/odoo#180438
Before this commit, when adding a product variant with an attribute that does not trigger variant creation (create_variant !== "always"), the system failed to include the extra price of this attribute if another attribute with variant creation mode was present. Additionally, for variants of an attribute that triggers variant creation and is added by a barcode, the it would computed the extra price twice. opw-4151754 --- I confirm I have signed the CLA and read the PR guidelines at www.odo
Original PR description
Before this commit, when adding a product variant with an attribute that does not trigger variant creation (create_variant !== "always"), the system failed to include the extra price of this attribute if another attribute with variant creation mode was present. Additionally, for variants of an attribute that triggers variant creation and is added by a barcode, the it would computed the extra price twice. opw-4151754 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179399
Since [1], a display of the number of records was added in a kanban view when grouped. This commit removes this display when the Kanban view does not have any records and the sample data is used. [1]: https://github.com/odoo/odoo/commit/f486bca505cb6ef9bf477e5d02d06c420b27de56 Forward-Port-Of: odoo/odoo#180311
Original PR description
Since [1], a display of the number of records was added in a kanban view when grouped. This commit removes this display when the Kanban view does not have any records and the sample data is used. [1]: https://github.com/odoo/odoo/commit/f486bca505cb6ef9bf477e5d02d06c420b27de56 Forward-Port-Of: odoo/odoo#180311
When returning a purchase/sale order, we can not create accrued entry for the returned order Steps: - Create a purchase order - Receive product - Create and confirm bill - Set received quantity to 0 - From the action menu, select "Accrued Expense Entry" -> There is no line, it should be a line for the vendor credit not This is because we filter the order lines to get only the lines that have a positive quantity to invoice, in that case the quantity to invoice is negative and should be taken i
Original PR description
When returning a purchase/sale order, we can not create accrued entry for the returned order Steps: - Create a purchase order - Receive product - Create and confirm bill - Set received quantity to 0 - From the action menu, select "Accrued Expense Entry" -> There is no line, it should be a line for the vendor credit not This is because we filter the order lines to get only the lines that have a positive quantity to invoice, in that case the quantity to invoice is negative and should be taken into account opw-4176706 Forward-Port-Of: odoo/odoo#180299
Add `account_edi_ubl_cii_tax_extension` module to transifex. Pot file already added in original PR that adds in new module into stable. Orig PR: https://github.com/odoo/odoo/pull/176221 opw-4061329 Forward-Port-Of: odoo/odoo#180491 Forward-Port-Of: odoo/odoo#180277
Original PR description
Add `account_edi_ubl_cii_tax_extension` module to transifex. Pot file already added in original PR that adds in new module into stable. Orig PR: https://github.com/odoo/odoo/pull/176221 opw-4061329 Forward-Port-Of: odoo/odoo#180491 Forward-Port-Of: odoo/odoo#180277
Versions -------- - saas-17.4+ Steps ----- 1. Set document layout to DIN5008; 2. create an invoice; 3. print invoice. Issue ----- Dates are formatted as YYYY-MM-DD, regardless of date formatting preferences. Cause ----- Commit 6d36b380315 moved DIN5008 formatting logic from Python to XML. In doing so, dates were no longer getting formatted. Solution -------- Add the `date` widget to the XML fields to format them accordingly. opw-4172138 Enterprise PR: https://github
Original PR description
Versions -------- - saas-17.4+ Steps ----- 1. Set document layout to DIN5008; 2. create an invoice; 3. print invoice. Issue ----- Dates are formatted as YYYY-MM-DD, regardless of date formatting preferences. Cause ----- Commit 6d36b380315 moved DIN5008 formatting logic from Python to XML. In doing so, dates were no longer getting formatted. Solution -------- Add the `date` widget to the XML fields to format them accordingly. opw-4172138 Enterprise PR: https://github.com/odoo/enterprise/pull/70142 Forward-Port-Of: odoo/odoo#180415
Do not use the purchase description in dropshipping pickings Example use case: - Create a dropshipping product and set a purchase description - Create a sales order with the product and confirm - Purchase order will have the purchase description - Confirm the purchase order - Go to dropshipping picking - Print Delivery slip Current behavior: - Product name and purchase description is displayed Expected behavior: - Purchase description should not be displayed @Tecnativa TT5067
Original PR description
Do not use the purchase description in dropshipping pickings Example use case: - Create a dropshipping product and set a purchase description - Create a sales order with the product and confirm - Purchase order will have the purchase description - Confirm the purchase order - Go to dropshipping picking - Print Delivery slip Current behavior: - Product name and purchase description is displayed Expected behavior: - Purchase description should not be displayed @Tecnativa TT50677 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180111 Forward-Port-Of: odoo/odoo#179104
This commit will remove the readonly constraint on the journal when an account move has been posted. task: 4028973 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180357 Forward-Port-Of: odoo/odoo#171710
Original PR description
This commit will remove the readonly constraint on the journal when an account move has been posted. task: 4028973 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180357 Forward-Port-Of: odoo/odoo#171710
When uploading a bill via xml, if the file does not contain the node 'Name` in accounting parties informations, we don't set the partner at all on the bill. With this commit, if the node `Name` is missing, we fallback to the node `RegistrationName`. opw-4154071 Forward-Port-Of: odoo/odoo#180505 Forward-Port-Of: odoo/odoo#180056
Original PR description
When uploading a bill via xml, if the file does not contain the node 'Name` in accounting parties informations, we don't set the partner at all on the bill. With this commit, if the node `Name` is missing, we fallback to the node `RegistrationName`. opw-4154071 Forward-Port-Of: odoo/odoo#180505 Forward-Port-Of: odoo/odoo#180056
Steps to reproduce: Create 2 products with a product tag (ex. '3+1') Create Buy X Get Y reward. In the conditional rules choose: - in the 'among' section the product tag '3+1', - in the 'grant' 1 point per unit paid In the rewards choose: - reward type as 'Free product' - in exchage of 3 points - in the 'among' section the product tag '3+1' Go to /shop page and add 3 products with the tag '3+1' Try to click on the button 'Free product'
Original PR description
Steps to reproduce:
Create 2 products with a product tag (ex. '3+1')
Create Buy X Get Y reward.
In the conditional rules choose:
- in the 'among' section the product tag '3+1',
- in the 'grant' 1 point per unit paid
In the rewards choose:
- reward type as 'Free product'
- in exchage of 3 points
- in the 'among' section the product tag '3+1'
Go to /shop page and add 3 products with the tag '3+1'
Try to click on the button 'Free product'
The reward is not applied
Reason:
In the claim_reward function a reward is not applied if it is a multi_product one.
Fix:
added a dropdown on template that will allow user to select product. the selected product will be sent to backend and processed in claim_reward function
Task : 3774033
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#180477
Forward-Port-Of: odoo/odoo#164868Epson badge printers have recently been added to the Event app, but they use new reports and so can't currently be used via pos_event. This PR adds support for printing the correct reports based on the event's badge format, which will allow printing on the badge printer assuming the report has been linked. Related enterprise PR: https://github.com/odoo/enterprise/pull/69953 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/o
Original PR description
Epson badge printers have recently been added to the Event app, but they use new reports and so can't currently be used via pos_event. This PR adds support for printing the correct reports based on the event's badge format, which will allow printing on the badge printer assuming the report has been linked. Related enterprise PR: https://github.com/odoo/enterprise/pull/69953 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180063
This commit fixes a test that even though would pass with the current implementation of the position hook, was behaving in a completely different way from before the conversion. Forward-Port-Of: odoo/odoo#180559
Original PR description
This commit fixes a test that even though would pass with the current implementation of the position hook, was behaving in a completely different way from before the conversion. Forward-Port-Of: odoo/odoo#180559
Commit 1: When you are launching a POS, you are loading all events of your companies, even if you don't sale any of the related products of those event. To avoid unnecessary load time, we only take the events we can sell Commit 2: We are preventing the deletion of the pos category events, which is a data. We don't need to do so, as the only place where we are using it we correctly manage the fact that the category exists or not by checking if the record is still there before using i
Original PR description
Commit 1: When you are launching a POS, you are loading all events of your companies, even if you don't sale any of the related products of those event. To avoid unnecessary load time, we only take the events we can sell Commit 2: We are preventing the deletion of the pos category events, which is a data. We don't need to do so, as the only place where we are using it we correctly manage the fact that the category exists or not by checking if the record is still there before using it. Forward-Port-Of: odoo/odoo#180470
With this commit we extend the account_tax model to add tax category code and tax exemption reason, that will be used when generating peppol xml. Without that we can only do some incomplete computation leading to missing informations in peppol xml. opw-4061329 Forward-Port-Of: odoo/odoo#180499 Forward-Port-Of: odoo/odoo#176221
Original PR description
With this commit we extend the account_tax model to add tax category code and tax exemption reason, that will be used when generating peppol xml. Without that we can only do some incomplete computation leading to missing informations in peppol xml. opw-4061329 Forward-Port-Of: odoo/odoo#180499 Forward-Port-Of: odoo/odoo#176221
If SMS or Whatsapp are not enabled, diplaying the email toggle button to set the mode to email is redundant, as email would be the only available option by default. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179895
Original PR description
If SMS or Whatsapp are not enabled, diplaying the email toggle button to set the mode to email is redundant, as email would be the only available option by default. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179895
**Steps to reproduce this issue:** - Go to views (Settings -> Technical -> User Interface -> Views). - Edit something and click the Save/Discard button. - Notice that the Save and Discard buttons remain visible. **Current behavior before PR:** The state `fieldIsDirty` remains true after clicking the Save/Discard button because the `FIELD_IS_DIRTY` event defined in the `useBus` hook is not triggered in `commitChanges`. **Desired behavior after PR is merged:** The Save and Discard
Original PR description
**Steps to reproduce this issue:** - Go to views (Settings -> Technical -> User Interface -> Views). - Edit something and click the Save/Discard button. - Notice that the Save and Discard buttons remain visible. **Current behavior before PR:** The state `fieldIsDirty` remains true after clicking the Save/Discard button because the `FIELD_IS_DIRTY` event defined in the `useBus` hook is not triggered in `commitChanges`. **Desired behavior after PR is merged:** The Save and Discard buttons hide successfully when not needed. task-3948043 Forward-Port-Of: odoo/odoo#180414 Forward-Port-Of: odoo/odoo#174187
In #165778, cross-dock was given a specific picking type as other old Internal Transfers. It was set as using the input / output locations as its source / destination. However, at warehouse creation, if it was not set as multi step reception and/or delivery, then respectively the input and/or the output location will the warehouse `lot_stock_id`. This is incorrect for Cross-Dock, as we always want to have Input -> Output. --- I confirm I have signed the CLA and read the PR guidelines at
Original PR description
In #165778, cross-dock was given a specific picking type as other old Internal Transfers. It was set as using the input / output locations as its source / destination. However, at warehouse creation, if it was not set as multi step reception and/or delivery, then respectively the input and/or the output location will the warehouse `lot_stock_id`. This is incorrect for Cross-Dock, as we always want to have Input -> Output. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180223
This reverts commit 76f06383d405e129a00bd4fffa3943d68dccec46. When serializing an object from the PoS computed fields are ignored, and this caused issues because `price_subtotal_incl` is needed in `_merge_order_lines`. This also fix the issue of the reverted commit in another and add a test for it. opw-4171641 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180354
Original PR description
This reverts commit 76f06383d405e129a00bd4fffa3943d68dccec46. When serializing an object from the PoS computed fields are ignored, and this caused issues because `price_subtotal_incl` is needed in `_merge_order_lines`. This also fix the issue of the reverted commit in another and add a test for it. opw-4171641 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180354
**Steps to reproduce:** 1- Install POS and POS restaurant 2- Activate self ordering 3- Create a self order from the mobile menu 4- Create another order from the Shop POS **Current behavior before PR:** There is a conflict happening in order numbers between Self order and other orders where at some point we might have two orders with the same number. This is happening because when adding the order from Shop we get the sequence number from the JS side in Order class https://github.com
Original PR description
**Steps to reproduce:** 1- Install POS and POS restaurant 2- Activate self ordering 3- Create a self order from the mobile menu 4- Create another order from the Shop POS **Current behavior before…
**Steps to reproduce:** 1- Install POS and POS restaurant 2- Activate self ordering 3- Create a self order from the mobile menu 4- Create another order from the Shop POS **Current behavior before PR:** There is a conflict happening in order numbers between Self order and other orders where at some point we might have two orders with the same number. This is happening because when adding the order from Shop we get the sequence number from the JS side in Order class https://github.com/odoo/odoo/blob/d82ffde0b316c52f726c247bf6f3d38e2e73e405/addons/point_of_sale/static/src/app/store/models.js#L1383 but in case of self order. We get it from ir_sequence https://github.com/odoo/odoo/blob/d82ffde0b316c52f726c247bf6f3d38e2e73e405/addons/pos_self_order/controllers/orders.py#L19 So we don't have a shared sequence between them. **Desired behavior after PR is merged:** We are now creating another sequence for self-order and as agreed with the PO we will have 'S' before the order number if the order is self-order opw-3809595 Forward-Port-Of: odoo/odoo#179810 Forward-Port-Of: odoo/odoo#162119
Problem: When viewing the replenishment information for a product, the last purchase date is set to the date from the oldest purchase order. The last_purchase_date field is set using the purchase order with the oldest date_order field. The last_purchase_date field should be set using the purchase order with the most recent date_order field. Purpose: By ordering the purchase orders by date_order desc we will get the purchase order with the most recent date_order field. This will cause the supp
Original PR description
Problem: When viewing the replenishment information for a product, the last purchase date is set to the date from the oldest purchase order. The last_purchase_date field is set using the purchase…
Problem: When viewing the replenishment information for a product, the last purchase date is set to the date from the oldest purchase order. The last_purchase_date field is set using the purchase order with the oldest date_order field. The last_purchase_date field should be set using the purchase order with the most recent date_order field. Purpose: By ordering the purchase orders by date_order desc we will get the purchase order with the most recent date_order field. This will cause the supplier’s last purchase date to be the most recent one instead of the oldest one. Steps to Reproduce on Runbot: 1. Create a storable product and create a reordering rule for this product 2. Create a purchase order for this product and set the Order Deadline to a date in the past and then confirm it 3. Create a purchase order for this product and set the Order Deadline to the current date and the confirm it 4. Navigate to this product’s replenishment information 5. Observe that the Last Purchase date is the earlier of the two dates from the purchase orders opw-4113810 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180527 Forward-Port-Of: odoo/odoo#177306
Problem was we try to get partner from `order.partner` instead of `order.partner_id` Steps to reproduce: - Install l10n_cl - Select the CL Company - Go to POS - Select products - Change the client to Blanco Martin & Asociados EIRL (has all the information for l10n_cl) - Click on "payment" - Select any payment method - Select the option "Invoice" - Validate - Console error opw-4180894 Forward-Port-Of: odoo/enterprise#70239
Original PR description
Problem was we try to get partner from `order.partner` instead of `order.partner_id` Steps to reproduce: - Install l10n_cl - Select the CL Company - Go to POS - Select products - Change the client to Blanco Martin & Asociados EIRL (has all the information for l10n_cl) - Click on "payment" - Select any payment method - Select the option "Invoice" - Validate - Console error opw-4180894 Forward-Port-Of: odoo/enterprise#70239
### Issue: The word 'Review' being used in 2 different frontend locations (it's also used in portal_rating) and the frontend can only use the last translation that it loads. Thus, the 'Review' is translated as 'Avis', which is wrong. ### After this PR: Renamed 'Review' label to 'Review Booking'. Task-4164125 Forward-Port-Of: odoo/enterprise#69404
Original PR description
### Issue: The word 'Review' being used in 2 different frontend locations (it's also used in portal_rating) and the frontend can only use the last translation that it loads. Thus, the 'Review' is translated as 'Avis', which is wrong. ### After this PR: Renamed 'Review' label to 'Review Booking'. Task-4164125 Forward-Port-Of: odoo/enterprise#69404
Steps to reproduce ================== - In the accounting app, go to 'Journal Entries'. - Create a new entry. - Set the 'reference' field to 'Receipt'. - Add 2 accounts in Journal Items. - For the 1st account, select 'Account Receivable' (e.g., 121000 Account Receivable). - Set the Partner field to "0h3n-abcdefg@yahoo.example.com" and the label field to "Online transfer reced agst INV-00171, Dt:01.08.2024". - For the 2nd account, set it to any other type, such as "101401 Bank". - Add
Original PR description
Steps to reproduce ================== - In the accounting app, go to 'Journal Entries'. - Create a new entry. - Set the 'reference' field to 'Receipt'. - Add 2 accounts in Journal Items. - For the…
Steps to reproduce ================== - In the accounting app, go to 'Journal Entries'. - Create a new entry. - Set the 'reference' field to 'Receipt'. - Add 2 accounts in Journal Items. - For the 1st account, select 'Account Receivable' (e.g., 121000 Account Receivable). - Set the Partner field to "0h3n-abcdefg@yahoo.example.com" and the label field to "Online transfer reced agst INV-00171, Dt:01.08.2024". - For the 2nd account, set it to any other type, such as "101401 Bank". - Add a credit amount in the 'Account Receivable' and the same amount in the 2nd account. - Save and post the transaction. - Navigate to the general ledger. - Ensure you expand the list of this newly created account move under the 121000 Account Receivable to observe overlapping text. - Click on 'PDF' and print the report. - Notice the overlapping text.  Cause of the issue ================== The o_overflow_value class is only applied when the cell value length is longer than 65 chars Solution =======  Here are the differences, only the following lines are pushed down  opw-4130917 Forward-Port-Of: odoo/enterprise#70141
Before this PR, trying to print an IoT linked report from PoS would result in an error, as the JS file for websockets was not loaded. This PR fixes the issue by including the file. Related community PR: https://github.com/odoo/odoo/pull/180063 Forward-Port-Of: odoo/enterprise#69953
Original PR description
Before this PR, trying to print an IoT linked report from PoS would result in an error, as the JS file for websockets was not loaded. This PR fixes the issue by including the file. Related community PR: https://github.com/odoo/odoo/pull/180063 Forward-Port-Of: odoo/enterprise#69953
Steps to reproduce (on IOS): ------------------- With Safari browser: - Install `Meeting Rooms` app - Go to Meeting Rooms -> Rooms and open any room - Copy the `Room Booking URL` and open it in a new tab - Click on the menu, then on `Add to Home Screen` - Open the room booking from the home screen Issue: ------ The URL and browser buttons are visible at the top of the screen. Solution: --------- Add the meta tags `mobile-web-app-capable` and `apple-mobile-web-app-capable`
Original PR description
Steps to reproduce (on IOS): ------------------- With Safari browser: - Install `Meeting Rooms` app - Go to Meeting Rooms -> Rooms and open any room - Copy the `Room Booking URL` and open it in a new tab - Click on the menu, then on `Add to Home Screen` - Open the room booking from the home screen Issue: ------ The URL and browser buttons are visible at the top of the screen. Solution: --------- Add the meta tags `mobile-web-app-capable` and `apple-mobile-web-app-capable` to the room template. opw-3639196 Forward-Port-Of: odoo/enterprise#67944
**Steps to reproduce:** - Make studio view of account journal entry form view (account.journal.form). - Find the node that exists on xpath "//field[@name='partner_id'][@widget='res_partner_many2one']" and remove the invisible attribute from it. - Upgrade database to saas-17.4 **Traceback:** ``` File "/home/odoo/src/enterprise/saas-17.4/account_invoice_extract/models/account_invoice.py", line 900, in _get_view node.set('invisible', f"{placeholder_condition} or ({node.attrib.pop(
Original PR description
**Steps to reproduce:**
- Make studio view of account journal entry form view (account.journal.form).
- Find the node that exists on xpath "//field[@name='partner_id'][@widget='res_partner_many2one']"
and remove the invisible attribute from it.
- Upgrade database to saas-17.4
**Traceback:**
```
File "/home/odoo/src/enterprise/saas-17.4/account_invoice_extract/models/account_invoice.py", line 900, in _get_view
node.set('invisible', f"{placeholder_condition} or ({node.attrib.pop('invisible')})")
File "src/lxml/etree.pyx," line 2464, in lxml.etree._Attrib.pop
KeyError: 'invisible'
```
**Solution:**
- This occurs because when checking the invisible attribute of a node, we are not checking if an invisible attribute exists or not, so added a condition for checking.
Forward-Port-Of: odoo/enterprise#69891Versions -------- - saas-17.4+ Steps ----- 1. Set document layout to DIN5008; 2. create an invoice; 3. print invoice. Issue ----- Dates are formatted as YYYY-MM-DD, regardless of date formatting preferences. Cause ----- Commit 7f63dab38a6 moved DIN5008 formatting logic from Python to XML. In doing so, dates were no longer getting formatted. Solution -------- Add the `date` widget to the XML fields to format them accordingly. opw-4172138 Community PR: https://github.
Original PR description
Versions -------- - saas-17.4+ Steps ----- 1. Set document layout to DIN5008; 2. create an invoice; 3. print invoice. Issue ----- Dates are formatted as YYYY-MM-DD, regardless of date formatting preferences. Cause ----- Commit 7f63dab38a6 moved DIN5008 formatting logic from Python to XML. In doing so, dates were no longer getting formatted. Solution -------- Add the `date` widget to the XML fields to format them accordingly. opw-4172138 Community PR: https://github.com/odoo/odoo/pull/180415 Forward-Port-Of: odoo/enterprise#70142
Sequences of optional employer insurance payments should come before gross Forward-Port-Of: odoo/enterprise#70081 Forward-Port-Of: odoo/enterprise#70070
Original PR description
Sequences of optional employer insurance payments should come before gross Forward-Port-Of: odoo/enterprise#70081 Forward-Port-Of: odoo/enterprise#70070
Since the fiscal position is added in data with the xml, the others companies than the current ones don't have it. So this commit will allow: - When installing the Avatax modules, create the fiscal position in all US companies at the same time - When creating a new US company with the Avatax module installed, setup the fiscal position in the new company at the same time task: 4100725 Forward-Port-Of: odoo/enterprise#69204
Original PR description
Since the fiscal position is added in data with the xml, the others companies than the current ones don't have it. So this commit will allow: - When installing the Avatax modules, create the fiscal position in all US companies at the same time - When creating a new US company with the Avatax module installed, setup the fiscal position in the new company at the same time task: 4100725 Forward-Port-Of: odoo/enterprise#69204
In this PR, we adapt the code of the belgian blackbox module to be compliant with the law. A summary of the changes can be found below: Added the global discount option in certified pos Added fields to the log of orders Correct loging of orders Remove the option to download the receipt Automatic work in/out for the employees Remove the possibility to refund work in/out Precision made to the sales report Added some restriction on the settings of a pos_config Remove the possibility o
Original PR description
In this PR, we adapt the code of the belgian blackbox module to be compliant with the law. A summary of the changes can be found below: Added the global discount option in certified pos Added fields to the log of orders Correct loging of orders Remove the option to download the receipt Automatic work in/out for the employees Remove the possibility to refund work in/out Precision made to the sales report Added some restriction on the settings of a pos_config Remove the possibility of multi-company when using a certified pos Corrected some behavior that were not meeting requirements (split,...) Forward-Port-Of: odoo/enterprise#69826
A new dependency has been introduced by mistake. Even if it still makes sense from a functional point of view, this modification wasn't respecting our stable policy and thus should be reverted. Error introduced at https://github.com/odoo/enterprise/pull/63481 Forward-Port-Of: odoo/enterprise#70173
Original PR description
A new dependency has been introduced by mistake. Even if it still makes sense from a functional point of view, this modification wasn't respecting our stable policy and thus should be reverted. Error introduced at https://github.com/odoo/enterprise/pull/63481 Forward-Port-Of: odoo/enterprise#70173
When parsing a claim status from the SII, the list of events in the response can either be a single event or a list of events. If a list was returned this would fail with a parsing error because the original implementation only expects a single event. That then led to the status getting repeatedly checked and logging "list indices must be integers or slices, not str" when done through a cron. This fix supports both the single and multiple event scenario. The l10n_cl_claim field is not display
Original PR description
When parsing a claim status from the SII, the list of events in the response can either be a single event or a list of events. If a list was returned this would fail with a parsing error because the…
When parsing a claim status from the SII, the list of events in the response can either be a single event or a list of events. If a list was returned this would fail with a parsing error because the original implementation only expects a single event. That then led to the status getting repeatedly checked and logging "list indices must be integers or slices, not str" when done through a cron. This fix supports both the single and multiple event scenario. The l10n_cl_claim field is not displayed anywhere by default and is only used to check if the claim status still needs to be logged in the chatter or not. Since multiple response codes are possible, in theory it should be a list instead of a single value, but that would be more appropriate for a change in master. A boolean flag would also suffice if the response code doesn't need to be displayed separately. We currently just set the last code that was returned. The responses observed in the customer database include the code NCA, which isn't expected by Odoo. This code was added as a valid one. opw-3920273 Forward-Port-Of: odoo/enterprise#70167 Forward-Port-Of: odoo/enterprise#66498