| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 404 |
| Technical Name |
datetime_filter |
| License | LGPL-3 |
DatetimeFilter App for Odoo
The DatetimeFilter app for Odoo allows you to filter records based on a selected date range. This feature adds a datetime panel to the control panel, where you can easily pick a date range and filter records that fall within that range. This tool is particularly useful for managing records with datetime fields and improving data accessibility within Odoo.
How the DatetimeFilter Works:
- Datetime Panel in the Control Panel: A datetime filter panel will appear in your Odoo control panel. This panel allows you to select a start and end date, specifying the date range you want to filter records by.
- Select Date Range: Use the panel to choose a date range. Once you select the start and end dates, the app will filter the records and display only those that fall within the specified range.
- Apply Filter to Records: After selecting the date range, the app will automatically filter all relevant records that match the datetime criteria. This helps you to narrow down your results and focus on the records you need.
Optional Context Action Settings:
In context actions, you can add the following code to customize the datetime filter:
{default_dt_field: 'sign_date', search_by_field_date: ['sign_date', 'start_date', 'end_date']}
-
default_dt_field: This is the default datetime field to filter
by (e.g.,
'sign_date'). -
search_by_field_date: This is an optional list of datetime
fields you want to use for filtering (e.g.,
['sign_date', 'start_date', 'end_date']). If not specified, all datetime fields will be available for filtering.
By configuring these settings, you can fine-tune how the datetime filter applies to your records, ensuring it works seamlessly with your data structure.
Note: Make sure the selected datetime fields are properly configured in your models for the filter to work correctly. If no datetime fields are provided, the filter will apply to all datetime fields available in the records.
Please log in to comment on this module