Thursday, September 19, 2024
8 changes · 17.0
New functionality added to Odoo
This update introduces a new feature to calculate and account for corporate tax obligations for UAE corporations. When a company's profits exceed a defined threshold, this system automatically generates the necessary tax reports, streamlining compliance processes. This addition ensures accurate tax reporting and adherence to local regulations.
Original PR description
When a corporation's annual net profits exceeds a certain limit, a corporate tax has to be paid. This commit implements the calculation and accounting of this corporate tax. task: 3690934
Enhancements to existing features
The subscription refresh button on the database expiration panel is now displayed as a clear text button instead of just an icon. This makes it easier for users to find and use the refresh action when their subscription has been renewed but the system hasn't updated yet, helping them quickly unblock their database without confusion.
Original PR description
For on premise instances, when the database expire and user renew its subscription, the update is not immediate; on the expiration panel there is a already a button to forcefully refresh the…
Resolved issues and error corrections
This fix resolves an issue where the postage cost calculation for SnailMail follow-up letters was not being computed correctly. Previously, when sending follow-up notices to customers with multiple contacts, the system would incorrectly show only 1 stamp regardless of the actual number of letters being sent. This update ensures the cost calculation properly reflects the actual number of follow-up letters being processed.
Original PR description
Problem: The `snailmail_cost` field was not being computed because the compute method was not being called. Steps to reproduce: - Enable "SnailMail" in Settings. - Navigate to Accounting > Follow-up Reports. - Open a report. - Follow up on the report. - Observe that the stamps count is 1, even if the partner has multiple follow-up contacts. opw-4160083 Forward-Port-Of: odoo/enterprise#70236
For on premise instances, when the database expire and user renew its subscription, the update is not immediate; on the expiration panel there is a already a button to forcefully refresh the subscription status and unblock the database, but it's not really visible (its not clear that the 'refresh' icon right next to "Renew your subscription" / "Upgrade your subscription" buttons is just to refresh the subscription status and not to re-do that action again). This commit now shows the 'Refresh subscription status' action as a textual button to make it more visible to users. [opw-3942907](https://www.odoo.com/odoo/project.task/3942907) Note: the goal is to introduce a slight [wording change](https://github.com/odoo/enterprise/compare/16.0...odoo-dev:enterprise:16.0-opw-3942907-exp-panel-increase-sub-refresh-act-visibility-xal#diff-915475ae004db6256f7efc2757edfead13697a1581ee8c609251b1bafdcf9d06R24) (cf ticket) in 16.0 and later forward port, we're not doing it for 15.0 as the translation is still loaded in db Forward-Port-Of: odoo/enterprise#70238 Forward-Port-Of: odoo/enterprise#65768
Fixed a technical error that occurred when generating bank reconciliation reports for accounts with zero balances. The system was attempting an invalid mathematical calculation that caused the report to fail. This fix ensures the report generates successfully in all scenarios.
Original PR description
The issue: When we have entries that are linked to a bank statement with a balance of 0, this will lead to a division by zero error when generating a reconciliation report The Fix: check for the suspense balance value, if it is zero, then there is no need to compute the rate since zero divided by anything = 0 opw-3990116 Forward-Port-Of: odoo/enterprise#66603 Forward-Port-Of: odoo/enterprise#65095
This fix resolves an issue where manually changing a line's parent category in Account Reports would not update its position in the report display. The parent_id field has been removed from the editing interface since the hierarchy is already properly managed by the system's display widget, preventing confusion and incorrect report layouts.
Original PR description
### Steps to reproduce issue: 1. Go to _Accounting > Configuration > Account Reports_ 2. Select Balance Sheet and Add a line in it 3. Select the new line and give it ASSETS as parent_id 4. Go to Reporting > Balance Sheet 5. The new line is still at the end of the report ### Explanation: Lines have a `sequence` to sort them in the report. It is not computed to change along with `parent_id`, since the lines are supposed to be arranged through the `AccountReportListRenderer` widget. Because of it a line whose `parent_id` changes will not be placed correctly. ### Fix reasoning: The `parent_id` field will be removed from the view, the hierarchy is already shown in the widget. opw-4101282
Users were unable to upload image files when creating invoices in the Kenya EDI system due to a technical error. This fix resolves the issue by properly handling image file uploads, allowing users to attach images to invoices without encountering errors.
Original PR description
Currently, an exception is generated when the user tries to upload an image file for creating an invoice. error: `UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position 0: invalid start byte` This is because below code line tries to load image context of uploaded image file. https://github.com/odoo/enterprise/blob/799b80d12680153a5ba42ee97501723ba38052b1/l10n_ke_edi_oscu/models/account_move.py#L567 This commit fixes the above issue by handling `UnicodeDecodeError` in `contextlib.suppress.` sentry-5757745777
Users with restricted access permissions were unable to download planning reports due to permission errors when accessing related sales order and project information. This fix grants the system temporary elevated access to retrieve the necessary data for report generation, allowing all authorized users to successfully download their planning reports.
Original PR description
- 17.0 ### Steps to reproduce: - Install sale_planning and project_forecast app. - Create a sale order with the planning product (e.g. Developer (Plan services)) and confirm it. - Create planning for that sale order and set resource (e.g. Marc demo) to it. - Click 'Publish & Send' button. - Set 'User: Own Documents Only' rights for the sales and 'User' or 'none' for the project and planning for Marc demo. - Login from that user and open the planning app. - Open assigned planning form view. - Print planning. ### Issue: - Traceback occurs of access right. ### Cause: - While downloading the report, it goes to access the "display_name" and "name" field of sale order line and project respectively that is computed in the _compute_display_name, but the user cannot access "sale.order.line" and "project" due to record rule. ### Solution: - Give access to the record by using sudo(). task-3978552
This fix prevents users from accidentally mismatching products when creating quality checks. Previously, if a user selected a quality point from a different product, the system would silently change the product instead of alerting them to the error. Now the system properly validates that the quality point and quality check must belong to the same product, protecting data integrity.
Original PR description
Steps to Reproduce the Bug: - Create two storable products, "P1" and "P2". - Create a Quality Point: - Product: P1 - Type: Manufacturing - Create a Quality Check: - Product: P2 - Select the Quality Point of P1 Problem: The product is updated to P1 instead of triggering a user error. opw-4030133 Forward-Port-Of: odoo/enterprise#69362