Daily updates from Odoo
Tuesday, August 17, 2021
15 changes · master
Enhancements to existing features
Gantt chart tooltips have been standardized across several business apps to make schedule details easier to read. Time ranges now appear consistently on one line, helping users compare dates and timings more quickly.
Original PR description
Applies to the following modules: - event_enterprise - hr_appraisal - hr_holidays_gantt - hr_work_entry_contract_enterprise - industry_fsm - infustry_fsm_report - planning - project_enterprise - project_timesheet_forecast - sale_renting - sale_stock_renting - website_event_track_gantt Cleans up the gantt tooltip for the above modules, mainly replaces the format from `Field: data` to `Field - data` and unifies the format to display the time range; previously Start and End would be on two separate lines, they are now in the format `start -> end` with the same print 'format' everywhere. Task ID: 2618228
Resolved issues and error corrections
The signed report ribbon in Field Service worksheet reports now displays correctly after the recent Odoo design update. This prevents visual issues in customer-facing service reports and keeps documents looking professional.
Original PR description
Since the recent relook of odoo, the sign report ribbon was badly displayed, this commit aims to fix that issue. Task ID: 2615505
The appointment slot list in Website Calendar now uses a standard layout instead of custom column sizing. This fixes a minor visual glitch and makes the editable list easier and more consistent to use.
Original PR description
This commit fixes a minor UI glitch within the editable tree view of calendar.appointment.slots. Indeed, the current implementation uses custom classes and tags to try to alter the size of the tree view columns, which results in strange UI display. Trying to alter the tree view column sizes is generally not a good idea and not clearly supported. This commit removes the various customizations to fall back to a more standard tree view definition. Task-2625696
The Norway SAF-T test data was updated so invoices can be posted correctly when the Norwegian EDI feature is also installed. This prevents avoidable test failures caused by a missing required company identifier, helping keep the reporting module reliable across installed configurations.
Original PR description
When posting an invoice, l10n_no_bronnoysund_number is required to generate the edi and will raise an error if not present.
The invoice form no longer shows a Spanish reporting tab for companies using other localizations. This avoids confusion in multi-company setups where Spanish reports are installed but not relevant to every company.
Original PR description
In a multi-company environment, with l10n_es_reports installed, a tab was added to the invoice form view. That tab was also visible in other localizations as well, which was not desired. Task: 2611256
This fix ensures accounting test scenarios that use multiple currencies explicitly activate the currencies they need. It helps keep automated checks reliable after a platform change made currencies inactive by default, reducing the risk of false test failures.
Original PR description
Since [commit 4402949](https://github.com/odoo/odoo/commit/44029495bc4f85c9f99b16dbab0a49c6ba0f19f9), all currencies are inactive by default - activate currencies required for tests
Code cleanup and technical improvements
This update keeps Studio and Documents Spreadsheet aligned with recent platform changes. It helps ensure these areas continue working smoothly after underlying template and service naming changes.
Miscellaneous changes
…nd create is selected When clicking on the 'New rental' action, if no current customer is linked to the lead, a popup opens with the following options: - Create a new customer - Link to an existing customer - Do not link to a customer If odoo found a potential matching customer but we decide it is the wrong one and select the first option, a new one should always be created opw-2545065 Task-2622793 Forward-Port-Of: odoo/enterprise#20275
Original PR description
…nd create is selected When clicking on the 'New rental' action, if no current customer is linked to the lead, a popup opens with the following options: - Create a new customer - Link to an existing customer - Do not link to a customer If odoo found a potential matching customer but we decide it is the wrong one and select the first option, a new one should always be created opw-2545065 Task-2622793 Forward-Port-Of: odoo/enterprise#20275
How to reproduce the problem: - Install the sale_subscription module - Create a SO with a subscription product (e.g. 'Office Cleaning Subscription (Monthly)') - In the 'Other info' tab of the SO, write something in the Customer Reference field - Save & Confirm the SO. Click on the Subscription button. - (Activate the debug mode if not already done.) Click on Generate Invoice - The Payment Reference of the created invoie is empty: it should correspond to the Customer Reference of the SO
Original PR description
How to reproduce the problem: - Install the sale_subscription module - Create a SO with a subscription product (e.g. 'Office Cleaning Subscription (Monthly)') - In the 'Other info' tab of the SO, write something in the Customer Reference field - Save & Confirm the SO. Click on the Subscription button. - (Activate the debug mode if not already done.) Click on Generate Invoice - The Payment Reference of the created invoie is empty: it should correspond to the Customer Reference of the SO Cause of the problem : the value was simply not fetched Solution : the reference is fetched from the sale order that generated the Subscription opw-2525643 Forward-Port-Of: odoo/enterprise#19895
Before this commit, the invoiced orders were not considered when validating the session with Fiskaly. Without l10n_de_pos_cert, the normal behaviour at the validation of a session is to change the state of 'paid' orders to 'done'. However, 'invoiced' orders do not change their states. These orders also need to be taken into account. opw-2619365 Forward-Port-Of: odoo/enterprise#20260 Forward-Port-Of: odoo/enterprise#20210
Original PR description
Before this commit, the invoiced orders were not considered when validating the session with Fiskaly. Without l10n_de_pos_cert, the normal behaviour at the validation of a session is to change the state of 'paid' orders to 'done'. However, 'invoiced' orders do not change their states. These orders also need to be taken into account. opw-2619365 Forward-Port-Of: odoo/enterprise#20260 Forward-Port-Of: odoo/enterprise#20210
…ack to draft Issue: After cancelling a sale order with a active subscription linked to it, we could set it to quotation (set to draft), this would add another quantity to the sale order Steps to reproduce: 1) Create a product that is a subscription product (Product Form > Sales) with Subscription addon installed 2) Create a Sales order with that 1 unit of that subscription 3) Confirm the sale 3a) Optional: Check subscriptions linked to that SO, it will have a quantity of 1 4) C
Original PR description
…ack to draft Issue: After cancelling a sale order with a active subscription linked to it, we could set it to quotation (set to draft), this would add another quantity to the sale order Steps to…
…ack to draft Issue: After cancelling a sale order with a active subscription linked to it, we could set it to quotation (set to draft), this would add another quantity to the sale order Steps to reproduce: 1) Create a product that is a subscription product (Product Form > Sales) with Subscription addon installed 2) Create a Sales order with that 1 unit of that subscription 3) Confirm the sale 3a) Optional: Check subscriptions linked to that SO, it will have a quantity of 1 4) Cancel the sale 5) Set to quotation the sale 6) Confirm the sale again 7) Check subscriptions linked to that SO, it will have a quantity of 2 Why is that a bug: When cancelling a confirmed sales order, the subscription associated with it should be cancelled too, and when reconfirming it, the quantity of the new subscription should match the new sales order. Also, in V14, the behaviour is the same than after this commit Side-note : as said in the ticket, this was done to match the actual flow of 14.0 where you cannot cancel either a closed or in_progess subscription, because the quantity increase is present whether the subscription is closed or in_progress opw-2527954 Forward-Port-Of: odoo/enterprise#20122 Forward-Port-Of: odoo/enterprise#19969
When every order in a session has a total of 0.0$, the 'payment_types' field is empty. This leads to a Traceback error when validating the pos session. Before this commit, when all orders in a session are of 0.0$, we sent an empty list in the 'payment_types' field to Fiskaly, resulting in a traceback when the user needs to validate his session: 'requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://dsfinvk.fiskaly.com/api/v0/cash_point_closings/XXXXXXXX-XXXX-XXXX-XXXX
Original PR description
When every order in a session has a total of 0.0$, the 'payment_types' field is empty. This leads to a Traceback error when validating the pos session.
Before this commit, when all orders in a session are of 0.0$, we sent an empty list in the 'payment_types' field to Fiskaly, resulting in a traceback when the user needs to validate his session:
'requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://dsfinvk.fiskaly.com/api/v0/cash_point_closings/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX'
Here is the complete response from Fiskaly:
'{"code":"E_FAILED_SCHEMA_VALIDATION","message":"Payment types are empty","status_code":400,"error":"Bad Request"}'
opw-2620199
Forward-Port-Of: odoo/enterprise#20212This commit fixes https://github.com/odoo/enterprise/commit/ad5cba918fed0ecd1cd45a16cf10e449ff000728 Task: 2572261 Forward-Port-Of: odoo/enterprise#19126
Original PR description
This commit fixes https://github.com/odoo/enterprise/commit/ad5cba918fed0ecd1cd45a16cf10e449ff000728 Task: 2572261 Forward-Port-Of: odoo/enterprise#19126
Forward-Port-Of: odoo/enterprise#20252
Original PR description
Forward-Port-Of: odoo/enterprise#20252
- Have pricelist A and B - Have a rentable product [TEST] with rental pricing defined for both A and B (Rental tab in product record) - Create a SO, add pricelist A and [TEST], configure the rent period via wizard - Switch to pricelist B, hit 'update prices' Nothing will change This occur because the pricing for the rent product is not defined in the pricelist but is computed via rental wizard. opw-2574866 Forward-Port-Of: odoo/enterprise#20197
Original PR description
- Have pricelist A and B
- Have a rentable product [TEST] with rental pricing defined
for both A and B (Rental tab in product record)
- Create a SO, add pricelist A and [TEST], configure the rent period via
wizard
- Switch to pricelist B, hit 'update prices'
Nothing will change
This occur because the pricing for the rent product is not defined in the
pricelist but is computed via rental wizard.
opw-2574866
Forward-Port-Of: odoo/enterprise#20197