Odoo Changelog — 2024-04-30

Tuesday, April 30, 2024

3 changes · saas-17.1

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_cz: Redo 17.1+ fw-port #148410

Coresaas-17.1l10n_cz

This corrects the Czech localization accounting configuration so it uses the expected newer data structure. It helps ensure Czech companies receive the right chart of accounts, taxes, tax groups, and fiscal positions during setup or updates.

Original PR description

Fw-port #148410 was merged before smdc-odoo force-pushed his corrections.

As a result, the commit that was merged 39f72f8341b0984da3a324e1a956be0e6e3af030 added chart template data in pre-16.2 format, rather than modify the post-16.2 template files.

This commit fixes the fw-port.

#czech-localization#accounting#taxes

[FIX] project_account: fix customer sequence in blocked by page

PR #153368

Coresaas-17.1project_account

The customer field in the portal's blocked-by task page now prioritizes customer-type contacts, matching behavior in other service-related fields. This makes it easier for portal users to find the right customer when editing task dependencies.

Original PR description

Steps:
- Install project and account app.
- Enable task dependancy from project.
- Share project which at least have one task with blocked by task.
- Open that project in portal.
- Edit customer field in blocked by page.

Issue:
- Customer with customer type are not displaying first like we have in other partner field in service apps.

Cause:
- Forgot to add context on blocked-by page's partner field to display type customer first.

Fix:
- Added a context to work it properly.

task-3716784

#portal#tasks#customers#project

[FIX] planning: Allow users to access Schedule/project in debug modified

PR #61738

Enterprisesaas-17.1planning

Users could encounter an error when opening the Project schedule in the Planning app while debug mode was enabled. This fix prevents that crash so teams can access planning schedules reliably during configuration or troubleshooting.

Original PR description

Steps: - Install `planning` - Enable debug `/web?debug=1` or assets `/web?debug=assets` - Open `planning` - Configuration - Enable "Project Planning" - Schedule/Project - Traceback ```…

Steps:
    - Install `planning`
    - Enable debug `/web?debug=1` or assets `/web?debug=assets`
    - Open `planning`
    - Configuration
    - Enable "Project Planning"
    - Schedule/Project
    - Traceback
```
UncaughtPromiseError > OwlError
Uncaught Promise > Invalid props for component 'PlanningEmployeeAvatar':
'isResourceMaterial' is missing (should be a boolean),
'showPopover' is missing (should be a boolean),
'resourceColor' is missing (should be a number)
```

The error is clear: the `PlanningEmployeeAvatar` component used by the `Gantt` view takes in props
```js
    static props = {
        ...Avatar.props,
        isResourceMaterial: { type: Boolean},
        showPopover: { type: Boolean },
        resourceColor: { type: Number },
    };
```

In the gantt view, we define `Avatar` props via the `avatarProps` variable

https://github.com/odoo/enterprise/blob/d8c76685d09e724ca2060b7dcbcbc062e1fa7444/planning/static/src/views/planning_gantt/planning_gantt_renderer.xml#L28-L34

https://github.com/odoo/enterprise/blob/61afda686a786d4e44d82902c995c0265d742404/planning/static/src/views/planning_gantt/planning_gantt_renderer.js#L79-L83

we use the props of the `Avatar` component inherited by our broken component.

One solution would be either to specify default values for the requested props, or to mark them as optional, which is what this commit does.

opw-3889131

Fw-port #148410 was merged before smdc-odoo force-pushed his corrections. As a result, the commit that was merged 39f72f8341b0984da3a324e1a956be0e6e3af030 added chart template data in pre-16.2 format, rather than modify the post-16.2 template files. This commit fixes the fw-port.

Steps: - Install project and account app. - Enable task dependancy from project. - Share project which at least have one task with blocked by task. - Open that project in portal. - Edit customer field in blocked by page. Issue: - Customer with customer type are not displaying first like we have in other partner field in service apps. Cause: - Forgot to add context on blocked-by page's partner field to display type customer first. Fix: - Added a context to work it properly. task-3716784

Steps: - Install `planning` - Enable debug `/web?debug=1` or assets `/web?debug=assets` - Open `planning` - Configuration - Enable "Project Planning" - Schedule/Project - Traceback ``` UncaughtPromiseError > OwlError Uncaught Promise > Invalid props for component 'PlanningEmployeeAvatar': 'isResourceMaterial' is missing (should be a boolean), 'showPopover' is missing (should be a boolean), 'resourceColor' is missing (should be a number) ``` The error is clear: the `PlanningEmployeeAvatar` component used by the `Gantt` view takes in props ```js static props = { ...Avatar.props, isResourceMaterial: { type: Boolean}, showPopover: { type: Boolean }, resourceColor: { type: Number }, }; ``` In the gantt view, we define `Avatar` props via the `avatarProps` variable https://github.com/odoo/enterprise/blob/d8c76685d09e724ca2060b7dcbcbc062e1fa7444/planning/static/src/views/planning_gantt/planning_gantt_renderer.xml#L28-L34 https://github.com/odoo/enterprise/blob/61afda686a786d4e44d82902c995c0265d742404/planning/static/src/views/planning_gantt/planning_gantt_renderer.js#L79-L83 we use the props of the `Avatar` component inherited by our broken component. One solution would be either to specify default values for the requested props, or to mark them as optional, which is what this commit does. opw-3889131