Daily updates from Odoo
Wednesday, August 10, 2022
4 changes
New functionality added to Odoo
Spreadsheet users can now create date filters based on recent periods such as the last 7, 30, or 365 days, or the last 3 years. This makes dashboards and reports stay up to date automatically without manually adjusting date ranges, while excluding the current day for consistent reporting.
Original PR description
Add a new option in the date global fitler to create a relative date filter. The filter can have the value : - last 7 Days (last_week) - last 30 Days (lasy_month) - last 365 Days (last_year) - last 3 Years (last_three_years) The current day is never included. Odoo task [2909075](https://www.odoo.com/web#id=2909075&menu_id=4720&cids=1&action=333&active_id=2328&model=project.task&view_type=form)
Enhancements to existing features
Odoo now reduces manual work when connecting a bank by automatically matching fetched bank accounts to suitable journals where possible. If no match is found, it can reuse empty journals or create new ones during synchronization, making onboarding faster and less error-prone.
Original PR description
When synchronizing with a bank to fetch transactions in Odoo, we have a
wizard that pop up at the end of the linking process so that the user
can link the fetched accounts with a journal. Actually the user must
select what to do for each account (create a new journal or linked with
an existing journal). What we want to do is to ease the flow by using
the following rules.
- if a journal with a similar bank account exists, we assign it to
the corresponding new online account.
- for the remaining online accounts, we assing empty journals with no
bank account set.
- when syncing the online accounts (last step),
online accounts with no journal set get newly created journals.Map views now handle grouping by multi-value fields such as assignees correctly. This ensures groups show clear labels, records appear under each relevant person, and map pins stay consistent with the record list.
Original PR description
The x2many 'group by' was available for the map view but was not handled specifically. Resulting in - The 'grouped by' map view with no group label - The grouped by was by set of ids in the x2many and thus not grouped by each id in the x2many. - The pin in the map had IDs that do not exist in the list of records on the right Example: Project->My Tasks -> Map View -> Group by assignee - There is no label for each users - there is a "group by" for the set ["Mitchell Admin", "Marc Demo"] instead to find the same record in the group record of Mitchell and also in the group record of Marc - There is a pin record with the number 52 but this number does not exist anymore in the list on the right. task_id: 2721035
Resolved issues and error corrections
The Planning roles list view has been switched back to the older display system to avoid a compatibility issue that was breaking employee avatar fields. This restores the affected view for users while a fuller technical update can be handled later.
Original PR description
With the conversion to the new views, legacy x2many fields go through a thin and incomplete compatibility layer to talk to the new model. This compatibility layer is not very robust and as such most custom x2many fields are broken in this configuration, in this case the field "many2many_avatar_employee". The proper fix is to convert this field widget, but in the meantime, the simple fix is to force this view to keep using the legacy view instead of the new view.