Tuesday, May 21, 2024
25 changes · saas-17.1
Resolved issues and error corrections
The point of sale now loads customer details that were missing when retrieving linked sale orders. This ensures customer names appear correctly in the sale order list, reducing confusion for staff reviewing or selecting orders.
Original PR description
Prior to this commit, if a partner was not loaded into the PoS, their name would not be displayed in the sale order list. This commit resolves this issue by ensuring missing partners are loaded when retrieving sale orders. opw-3881799 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
[IMP] point_of_sale: display odoo's logs' folder from an url Allow to access odoo logs from the IoT Box even if Odoo's server is down via nginx by displaying /var/log/odoo How : from the IoT Box, go to the url `/odoo-logs` will display all the logs files from Odoo opw-3887623 Forward-Port-Of: odoo/odoo#165765
Original PR description
[IMP] point_of_sale: display odoo's logs' folder from an url Allow to access odoo logs from the IoT Box even if Odoo's server is down via nginx by displaying /var/log/odoo How : from the IoT Box, go to the url `/odoo-logs` will display all the logs files from Odoo opw-3887623 Forward-Port-Of: odoo/odoo#165765
commit that introduced the issue: [1] Steps to reproduce the issue: ============================= - Go to to-do - Add some text - Click shift+enter at the end of the first line - Add some text in the second line - Select a prefix of the second line - Click any character - The selection is back at the start of the paragraph Origin of the issue: ==================== This was done intentionally by the mentioned commit which didn't take into consideration this case. Solution: ==
Original PR description
commit that introduced the issue: [1] Steps to reproduce the issue: ============================= - Go to to-do - Add some text - Click shift+enter at the end of the first line - Add some text in the second line - Select a prefix of the second line - Click any character - The selection is back at the start of the paragraph Origin of the issue: ==================== This was done intentionally by the mentioned commit which didn't take into consideration this case. Solution: ========= We set the curosr at the element index relative to its parent. opw-3829462 [1]: https://github.com/odoo/odoo/commit/06658ff13abfbdaeb7c562b8fd33fc9cf4f56f95 Forward-Port-Of: odoo/odoo#164509
Following the update to the VAT code required to be used with ZATCA sandbox on SA companies, we need to update the demo PCSID and CCSID on the journals as well. Description of the issue/feature this PR addresses: Base demo data for SA company does includes outdated data for the Journals Current behavior before PR: Base demo data for SA companies includes outdated data for the Journals Desired behavior after PR is merged: Base demo data for SA companies includes updated CCSID & PCSID
Original PR description
Following the update to the VAT code required to be used with ZATCA sandbox on SA companies, we need to update the demo PCSID and CCSID on the journals as well. Description of the issue/feature this PR addresses: Base demo data for SA company does includes outdated data for the Journals Current behavior before PR: Base demo data for SA companies includes outdated data for the Journals Desired behavior after PR is merged: Base demo data for SA companies includes updated CCSID & PCSID on the journals --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166106
Previously, only credit notes created from existing Invoices were allowed to be posted & sent to ZATCA. Now, as long as a credit/debit note has a Customer Reference (ref), the system will allow it to be confirmed and submitted Description of the issue/feature this PR addresses: Users are not allowed to confirm/submit Credit Notes if they are not linked to an existing Invoice Current behavior before PR: Upon confirmation/posting of a Credit Note, if it is not linked to an existing Invoice
Original PR description
Previously, only credit notes created from existing Invoices were allowed to be posted & sent to ZATCA. Now, as long as a credit/debit note has a Customer Reference (ref), the system will allow it to be confirmed and submitted Description of the issue/feature this PR addresses: Users are not allowed to confirm/submit Credit Notes if they are not linked to an existing Invoice Current behavior before PR: Upon confirmation/posting of a Credit Note, if it is not linked to an existing Invoice or does not have a Customer Reference, the system blocks the confirmation Desired behavior after PR is merged: As long as a credit note is linked to an existing Invoice or has a valid Custoemr Reference (ref) the system allows it to be confirmed --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166102
**Steps to reproduce:** - Install Delivery, Sales and Stock modules - Create a based on rules Shipping method for a product using weight as a variable - Create a quotation for this product - Add shipping to the quotation - Change the quantity of the order line - Click on 'Update shipping cost' **Current behavior before PR:** The weight of the order does not get updated once we set a shipping cost to the order. This is happening because of this condition https://github.com/odo
Original PR description
**Steps to reproduce:** - Install Delivery, Sales and Stock modules - Create a based on rules Shipping method for a product using weight as a variable - Create a quotation for this product - Add shipping to the quotation - Change the quantity of the order line - Click on 'Update shipping cost' **Current behavior before PR:** The weight of the order does not get updated once we set a shipping cost to the order. This is happening because of this condition https://github.com/odoo/odoo/blob/17.0/addons/delivery/models/sale_order.py#L139 since we can edit the quantity of the order lines then there is not point of not calculating the estimated weight each time. **Desired behavior after PR is merged:** With removing this condition the weight will get updated each time we open the shipping cost wizard. opw-3908453 Forward-Port-Of: odoo/odoo#165838 Forward-Port-Of: odoo/odoo#164928
This commit follows the list view renderer commit 62172737b689d08856f4ad3d3d49beb796c9f42e which adapts the vertical alignment inside the list view. Thus why this fix is in the same task. The btn remove (trash icon) was set to a padding of five pixels making it not vertically align with the rest of the list view text. This comes from commit 258e6a019a21042bf4f6cf70fcce386d37afd50c where the trash icon was moved to align with the new "View" button, but it misaligned the icon in all the oth
Original PR description
This commit follows the list view renderer commit 62172737b689d08856f4ad3d3d49beb796c9f42e which adapts the vertical alignment inside the list view. Thus why this fix is in the same task. The btn remove (trash icon) was set to a padding of five pixels making it not vertically align with the rest of the list view text. This comes from commit 258e6a019a21042bf4f6cf70fcce386d37afd50c where the trash icon was moved to align with the new "View" button, but it misaligned the icon in all the other list views. Applying an align top on the "View" button instead allows an even alignment with the rest of the text content of the list view. task-3557566 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#145457
Creating a 308 which redirects to an existing controller will have unpredictable (and unwanted) behaviors. Indeed, 308 are there to redirect an existing URL (like `/shop`) to a non-existing URL (like `/my-super-shop`) and to make it so that non existing URL will respond with the content of the existing URL. The way it's done is that it simply replace the routing map rule for the given URL by two new rules: - One for the non-existing URL (chosen url_to) which will serve the existing url en
Original PR description
Creating a 308 which redirects to an existing controller will have unpredictable (and unwanted) behaviors. Indeed, 308 are there to redirect an existing URL (like `/shop`) to a non-existing URL (like…
Creating a 308 which redirects to an existing controller will have unpredictable (and unwanted) behaviors. Indeed, 308 are there to redirect an existing URL (like `/shop`) to a non-existing URL (like `/my-super-shop`) and to make it so that non existing URL will respond with the content of the existing URL. The way it's done is that it simply replace the routing map rule for the given URL by two new rules: - One for the non-existing URL (chosen url_to) which will serve the existing url endpoint - One for the existing URL, which will be turned into a redirect endpoint This works fine except if you actually select an existing controller as url_to in the 308 rewrite. In this case, there will be 2 werkzeug Rules for the same URL, which is bad. Worst than that, depending of the selected controller the order of those 2 Rules will change, leading to different behavior. Step to reproduce: - Create a 308 from /blog to / (note that "/" is a controller) - Go to /blog, it will redirect and show the homepage - Go to /, it will show the homepage - Now edit the 308 and redirect /shop to / - Go to /shop, it redirects to / but won't show the homepage, it will show the shop page - Go to /, it will show the shop page Technically, here is the routing map for both cases: 1. 308 shop case ``` <FasterRule '/' -> functools.partial(<bound method WebsiteSale.shop of <odoo.http.CustomerPortal (extended by PortalAccount, PaymentPortal, CustomerPortalExternalTax, SaleStockPortal, CustomerPortal, PaymentPortal, PaymentPortal, WebsiteSaleDelivery, WebsiteSaleExternalTaxCalculation, WebsiteSale, WebsiteSaleStockRenting, WebsiteSaleStockRenting, WebsiteSale, WebsiteSaleRenting, PaymentPortal, CustomerPortalExternalTax, CustomerPortal, WebsiteAccount) object at 0x7f4d9468a6b0>>)>, <FasterRule '/' -> functools.partial(<bound method Website.index of <odoo.http.Home (extended by Home, Home, Routing, AuthSignupHome, Website) object at 0x7f4d94583460>>)>, ``` 2. 308 blog case ``` <FasterRule '/' -> functools.partial(<bound method Website.index of <odoo.http.Home (extended by Home, Home, Routing, AuthSignupHome, Website) object at 0x7f7fc9ebd7e0>>)>, <FasterRule '/' -> functools.partial(<bound method WebsiteBlog.blog of <odoo.http.WebsiteBlog object at 0x7f7fc9d69090>>)>, ``` You see that the Rule order is inverted from one case to another. We could have decided to do another fix and adapt the `_generate_routing_rules()` method to keep only one Route but that seems worst as: 1. 308 are not designed for that in the first place, not even sure what we would want 2. it will technically be far from ideal, having the check routing map to check if exists already and ensure the same behavior all the time Note that testing a few main controllers, only the /shop seems to lead to this different behavior. Note that it's a bit of a non-stable change, so 17.0 seems like a good compromise. Especially since the /shop example is not buggy before 17.0 as somehow the `Website.index` Rule is before the `WebsiteSale.shop`. ``` <FasterRule '/' -> functools.partial(<bound method Website.index of <odoo.http.Home (extended by Home, Home, Routing, AuthSignupHome, Website, WebsiteTest) object at 0x7fad28571660>>)>, <FasterRule '/' -> functools.partial(<bound method WebsiteSale.shop of <odoo.http.WebsiteSale (extended by WebsiteSaleDelivery, WebsiteSale) object at 0x7fad28435e40>>)>, ``` opw-3901713 Forward-Port-Of: odoo/odoo#165083
### Steps to reproduce: - Enable Multi-step Routes in the settings - Inventory > Configuration > Warehouse Management > Warehouses - Enable manufacturing in 2 steps (pbm) - Create a manufacturing order for a product P1 with a demand of 1 x P2 - Confirm the MO (a transfer for 1 x P2 should be created). - Add a line to the MO with a demand of 1 X P2 and save. #### > the related stock picking was updated twice leading to a demand of 3 Cause of the issue: Since pbm is enabled the co
Original PR description
### Steps to reproduce: - Enable Multi-step Routes in the settings - Inventory > Configuration > Warehouse Management > Warehouses - Enable manufacturing in 2 steps (pbm) - Create a manufacturing…
### Steps to reproduce: - Enable Multi-step Routes in the settings - Inventory > Configuration > Warehouse Management > Warehouses - Enable manufacturing in 2 steps (pbm) - Create a manufacturing order for a product P1 with a demand of 1 x P2 - Confirm the MO (a transfer for 1 x P2 should be created). - Add a line to the MO with a demand of 1 X P2 and save. #### > the related stock picking was updated twice leading to a demand of 3 Cause of the issue: Since pbm is enabled the components are required to be in pre-Production for the manufacturing to start with. As such, our MO is associated with two stock moves. One for the local transport of components: - move_inter_1: 1 x P2 from Stock to pre-Production - move_raw_1: 1 x P2 from pre-Production to Production Saving the additional component requirement on the mo will create and confirm a second raw move: - move_raw_2: 1 x P2 from pre-Production to Production During its "_action_confirm", the procurements of this move will create and confirm a second internal move: - move_inter_2: 1 x P2 from Stock to pre-Production During the "_action_confirm" of this internal move a merging process will start since the already existing move_inter_1 is a good candidate: https://github.com/odoo/odoo/blob/f07c1a6b60ac1d07d9a2b098cca6ba8413ffbe0d/addons/stock/models/stock_move.py#L1369-L1370 https://github.com/odoo/odoo/blob/f07c1a6b60ac1d07d9a2b098cca6ba8413ffbe0d/addons/stock/models/stock_move.py#L994-L998 The quantity of move_inter_1 will then be updated: https://github.com/odoo/odoo/blob/f07c1a6b60ac1d07d9a2b098cca6ba8413ffbe0d/addons/stock/models/stock_move.py#L1035 Then, the merging process of move_raw_2 will start since the already existing move_raw_1 is found as a good candidate and the quantity of this move will be updated by a "write" call. However, procurements are also run in the call of the write method unless 'no_procurement' is specified in the context: https://github.com/odoo/odoo/blob/e8f8c9b4286f60733153220511fd0e2bf33370b3/addons/mrp/models/stock_move.py#L344-L348 Since this is not the case, this will create and confirm a new internal move: - move_inter_3: 1 x P2 from Stock to pre-Production This move will also be merged to move_inter_1 (this is the second update). ### Fix: Since procurements will always be run by the "_action_confirm" of the related stock moves, we can safely skip the procurements run by the write method during this flow. opw-3880686 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#163808
Steps to repoduce: - Create an invoice - Add a discount - Post it - Send and print (to get the xml) - Upload the xml on https://face.gob.es/en/facturas/validar-visualizar-facturas Issue: You will get an error from the platform "Línea 111: Element 'DiscountRate': This element is not expected. Expected is ( DiscountReason )." Cause: The default is an empty string and will not be generated. Investigation indicates a delay in ticket arrivals (code from 2023). Presumably, the Spanish Go
Original PR description
Steps to repoduce: - Create an invoice - Add a discount - Post it - Send and print (to get the xml) - Upload the xml on https://face.gob.es/en/facturas/validar-visualizar-facturas Issue: You will get…
Steps to repoduce: - Create an invoice - Add a discount - Post it - Send and print (to get the xml) - Upload the xml on https://face.gob.es/en/facturas/validar-visualizar-facturas Issue: You will get an error from the platform "Línea 111: Element 'DiscountRate': This element is not expected. Expected is ( DiscountReason )." Cause: The default is an empty string and will not be generated. Investigation indicates a delay in ticket arrivals (code from 2023). Presumably, the Spanish Gobierno may have restricted its XML validation. Solution: Add a default value (the same for Charges just in case) We don't add a `t-if` since the value is always empty and the requirements of the Spanish governement only requires a string [0-2500 characters] `3.1.5.2.1.1. DiscountReason Reason why the discount or rebate is made. Y[1..1] TextMax2500Type string positions: 0-2500` sources: - https://www.facturae.gob.es/formato/Versiones%20anteriores/B)%20Versi%C3%B3n%203.0/Esquema_ingles_V3_0.pdf - https://www.facturae.gob.es/formato/Paginas/version-3-2.aspx - https://www.facturae.gob.es/formato/Documents/EnglishFacturae3_0.pdf opw-3911313 Forward-Port-Of: odoo/odoo#165525 Forward-Port-Of: odoo/odoo#165258
Issue: ====== Buttons of type of custom color in colorpicker are misaligned. Steps to reproduce the issue: ============================= - Go to notes and write some text - Select some text and open colorpicker - Got to gradient and click on Custom button Before: ======  After: ==== 
Original PR description
Issue: ====== Buttons of type of custom color in colorpicker are misaligned. Steps to reproduce the issue: ============================= - Go to notes and write some text - Select some text and open colorpicker - Got to gradient and click on Custom button Before: ======  After: ====  task-3562148 Forward-Port-Of: odoo/odoo#157234
As all won / lost leads will have an impact on the PLS frequency table, demo data will have one on the probabilities of leads without team_id set, as their probability is based on all leads, regardless on their team. Therefore, make sure we unlink all leads that are not the ones created in the test. We rebuild the table below, which is needed to ensure we only consider test leads. Follow up of ecac497336826b66799f63c1daa0749535ce73f1 Task-3700966 Forward-Port-Of: odoo/odoo#165842 Forward
Original PR description
As all won / lost leads will have an impact on the PLS frequency table, demo data will have one on the probabilities of leads without team_id set, as their probability is based on all leads, regardless on their team. Therefore, make sure we unlink all leads that are not the ones created in the test. We rebuild the table below, which is needed to ensure we only consider test leads. Follow up of ecac497336826b66799f63c1daa0749535ce73f1 Task-3700966 Forward-Port-Of: odoo/odoo#165842 Forward-Port-Of: odoo/odoo#162414
Before this commit, the root URL of the request was not sent to PayuLatam, leading to redirection to an incorrect website when databases with a different domain were set. To use the url_root, get_base_url must be called from the payment.acquirer instance. opw-3348291 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#165252 Forward-Port-Of: odoo/odoo#165092
Original PR description
Before this commit, the root URL of the request was not sent to PayuLatam, leading to redirection to an incorrect website when databases with a different domain were set. To use the url_root, get_base_url must be called from the payment.acquirer instance. opw-3348291 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#165252 Forward-Port-Of: odoo/odoo#165092
New accounts added in https://github.com/odoo/odoo/commit/d8873ee01f0974e82de2e6cc906b0c77f8a3687f will not be created upon module update because they are stored in a csv. A migration script will trigger their creation by calling `try_loading()`, similarly as was done here for new taxes: https://github.com/odoo/odoo/blob/512574861691f425ec6a17f20fe4b586bb88a299/addons/l10n_fr/migrations/2.1/post-migrate_update_taxes.py#L8 https://github.com/odoo/odoo/blob/eb7ea22ea036c645d3c22049b6e874f9e8ada6d4
Original PR description
New accounts added in https://github.com/odoo/odoo/commit/d8873ee01f0974e82de2e6cc906b0c77f8a3687f will not be created upon module update because they are stored in a csv. A migration script will trigger their creation by calling `try_loading()`, similarly as was done here for new taxes: https://github.com/odoo/odoo/blob/512574861691f425ec6a17f20fe4b586bb88a299/addons/l10n_fr/migrations/2.1/post-migrate_update_taxes.py#L8 https://github.com/odoo/odoo/blob/eb7ea22ea036c645d3c22049b6e874f9e8ada6d4/addons/l10n_ch/migrations/11.1/post-migrate_update_taxes.py#L21 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#165276
Prior to this commit, popups would not appear on the login page due to its z-index being set to 1000. This commit resolves the issue by setting the staring z-index of the popups to 10000, ensuring that popups are displayed on top. opw-3930943 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166016
Original PR description
Prior to this commit, popups would not appear on the login page due to its z-index being set to 1000. This commit resolves the issue by setting the staring z-index of the popups to 10000, ensuring that popups are displayed on top. opw-3930943 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166016
Issue --> The fetchall call made after the querying the dataset in `_saft_fill_report_general_ledger_values` runs into a memory error if there is a large number of rows. Solution --> Use a `while True` loop to use `dictfetchmany` to return rows in batches to optimize memory usage. `dictfetchmany` returns None if no rows are returned, which is the exit condition of the loop. opw-3859206 Forward-Port-Of: odoo/enterprise#62571 Forward-Port-Of: odoo/enterprise#61272
Original PR description
Issue --> The fetchall call made after the querying the dataset in `_saft_fill_report_general_ledger_values` runs into a memory error if there is a large number of rows. Solution --> Use a `while True` loop to use `dictfetchmany` to return rows in batches to optimize memory usage. `dictfetchmany` returns None if no rows are returned, which is the exit condition of the loop. opw-3859206 Forward-Port-Of: odoo/enterprise#62571 Forward-Port-Of: odoo/enterprise#61272
Issue: ------ When we go to a gantt view with the day view, the time format is always displayed in 12-hour format followed by "am" or "pm". Depending on the location, this format may also be 24 hours. Solution: --------- Use the current localization to determine the time display format. opw-3867317 Forward-Port-Of: odoo/enterprise#61209
Original PR description
Issue: ------ When we go to a gantt view with the day view, the time format is always displayed in 12-hour format followed by "am" or "pm". Depending on the location, this format may also be 24 hours. Solution: --------- Use the current localization to determine the time display format. opw-3867317 Forward-Port-Of: odoo/enterprise#61209
A separate tree view is defined in `whatsapp_template_view_form` to display the `variable_ids` field on the Variables page. This tree view contains fields that are not needed to display, such as `model`, `line_type`, and `name`. These fields are made invisible using `column_invisible="1"`. Task-3902030 Forward-Port-Of: odoo/enterprise#61952
Original PR description
A separate tree view is defined in `whatsapp_template_view_form` to display the `variable_ids` field on the Variables page. This tree view contains fields that are not needed to display, such as `model`, `line_type`, and `name`. These fields are made invisible using `column_invisible="1"`. Task-3902030 Forward-Port-Of: odoo/enterprise#61952
The link from 'Balance Sheet (abridged)' to 'Profit & Loss (abridged)' raises an error. ### Steps to reproduce : - Install the l10n_lu_reports module - Change the company to a Luxembourgian company - Go to Accounting > Reporting > Statement Reports > Balance Sheet - Change the report to 'Balance Sheet (abridged) (LU)' - In the report, click on the link 'VI. Profit or loss for the financial year' ### Cause: The action triggered by this link has not the right formatted context. It shou
Original PR description
The link from 'Balance Sheet (abridged)' to 'Profit & Loss (abridged)' raises an error. ### Steps to reproduce : - Install the l10n_lu_reports module - Change the company to a Luxembourgian company - Go to Accounting > Reporting > Statement Reports > Balance Sheet - Change the report to 'Balance Sheet (abridged) (LU)' - In the report, click on the link 'VI. Profit or loss for the financial year' ### Cause: The action triggered by this link has not the right formatted context. It should have the value 'report_id' but has 'model' and 'id' instead. This raises an error in execute_action when trying to read 'report_id' on this action. ### Solution: Remove 'model' in the context and rename 'id' to 'report_id'. opw-3912348 Forward-Port-Of: odoo/enterprise#62715
This commit fixes an issue that was brought by the redesign of Odoo, Milk. This redesign modified a scss variable for kanban views inside of form views which removed the background of the kanban view's headers. Now a new css rule has been added to the kanban embedded view so that the background comes back to its original value inside of Knowledge. task-3930157 Forward-Port-Of: odoo/enterprise#62528
Original PR description
This commit fixes an issue that was brought by the redesign of Odoo, Milk. This redesign modified a scss variable for kanban views inside of form views which removed the background of the kanban view's headers. Now a new css rule has been added to the kanban embedded view so that the background comes back to its original value inside of Knowledge. task-3930157 Forward-Port-Of: odoo/enterprise#62528
When unfolding the journals, a lot of empty, unused space was left around the values. This lead to the report easily becoming too large for the screen, causing the display of an horizontal scrollbar, and hence degrading the user experience. We fix that by removing any notion of minimal width for this report specifically. Forward-Port-Of: odoo/enterprise#62718
Original PR description
When unfolding the journals, a lot of empty, unused space was left around the values. This lead to the report easily becoming too large for the screen, causing the display of an horizontal scrollbar, and hence degrading the user experience. We fix that by removing any notion of minimal width for this report specifically. Forward-Port-Of: odoo/enterprise#62718
# Issue: In a Partner Ledger using the "Prefix Groups Threshold" option, there are the "Open" and "Journal Items" buttons that are available as any other line in partner ledger report but they aren't bind to a specific Partner so the Open button, redirect to a "New partner" page and the Journal Items raise a traceback. # Reproduce: - Go in debug mode - Accounting > Configuration > Accounting Report > Partner Ledger > Options - Set Prefix Groups Threshold to 2 - Go in
Original PR description
# Issue:
In a Partner Ledger using the "Prefix Groups Threshold" option, there are the "Open" and "Journal Items" buttons that are available as any other line in partner ledger report but they aren't bind to a specific Partner so the Open button, redirect to a "New partner" page and the Journal Items raise a traceback.
# Reproduce:
- Go in debug mode
- Accounting > Configuration > Accounting Report > Partner Ledger > Options
- Set Prefix Groups Threshold to 2
- Go in Accounting > Reports > Partner Ledger
- Try to open a journal items on a "Grouping Line"
# Task:
opw-3916555
Forward-Port-Of: odoo/enterprise#62360When accessing EC listing through the "Do not forget to submit the EC Sales list report" warning, the tax report's options used not to be passed onto EC listing. Steps to reproduce original issue: - Install `l10n_be_reports` - Create an invoice for a customer with 'Intra-Community' as a 'Fiscal Position' - Confirm it - Go to: Accounting > Reporting > Statement Reports > Tax Report - Select a period that'd include the invoice - Click on the "Do not forget to submit the EC Sales list re
Original PR description
When accessing EC listing through the "Do not forget to submit the EC Sales list report" warning, the tax report's options used not to be passed onto EC listing. Steps to reproduce original issue: - Install `l10n_be_reports` - Create an invoice for a customer with 'Intra-Community' as a 'Fiscal Position' - Confirm it - Go to: Accounting > Reporting > Statement Reports > Tax Report - Select a period that'd include the invoice - Click on the "Do not forget to submit the EC Sales list report" warning - The period selected will be the wrong one task-3891799 Forward-Port-Of: odoo/enterprise#62761 Forward-Port-Of: odoo/enterprise#62642
Kilometers are only computed using the aller-simple distance instead of aller retour Forward-Port-Of: odoo/enterprise#62366
Original PR description
Kilometers are only computed using the aller-simple distance instead of aller retour Forward-Port-Of: odoo/enterprise#62366
Steps: - Schedule an appointment for one table at a specific time. - Open the POS and verify the appointment. - In a separate tab, open the appointments application and transfer the appointment to a different table. - Return to the POS tab and confirm that the appointment is displayed on both tables. Issue: Both tables display scheduled appointments. Cause: Booking is not removed from the previous table. FIX: When updating an appointment to a new table, the booking is only visibl
Original PR description
Steps: - Schedule an appointment for one table at a specific time. - Open the POS and verify the appointment. - In a separate tab, open the appointments application and transfer the appointment to a different table. - Return to the POS tab and confirm that the appointment is displayed on both tables. Issue: Both tables display scheduled appointments. Cause: Booking is not removed from the previous table. FIX: When updating an appointment to a new table, the booking is only visible on current booking table. task-3893909 Forward-Port-Of: odoo/enterprise#62020