Initial commit: Odoo 18.0-20251222 extra-addons
Some checks failed
pre-commit / pre-commit (push) Has been cancelled
tests / Detect unreleased dependencies (push) Has been cancelled
tests / test with OCB (push) Has been cancelled
tests / test with Odoo (push) Has been cancelled

This commit is contained in:
tocmo0nlord
2026-03-13 20:43:25 +00:00
parent 36e847a7df
commit adbe430761
9472 changed files with 1265727 additions and 0 deletions

View File

@@ -0,0 +1,23 @@
For regular usage, see Usage below. This section is to clarify optional
functionality to developers.
To configure a model to use the Many2one style search field, make the
model inherit from \`date.range.search.mixin\`:
```
class AccountMove(models.Model):
_name = "account.move"
_inherit = ["account.move", "date.range.search.mixin"]
```
This will make a Period field show up in the search view:
> ![search_view](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_many2one_search_field.png)
By default, the mixin works on the date field. If you want the mixin to
work on a field with a different name, you can set a property on your
model:
```
_date_range_search_field = "invoice_date"
```

View File

@@ -0,0 +1,8 @@
- Laurent Mignon \<<laurent.mignon@acsone.eu>\>
- Alexis de Lattre \<<alexis.delattre@akretion.com>\>
- Miquel Raïch \<<miquel.raich@forgeflow.com>\>
- Andrea Stirpe \<<a.stirpe@onestein.nl>\>
- Stefan Rijnhart \<<stefan@opener.amsterdam>\>
- David Ramia \<<@ramiadavid>\>
- Son Ho \<<sonhd@trobz.com>\>
- Bert Van Groenendael \<<bert.vangroenendael@dynapps.eu>\>

View File

@@ -0,0 +1,5 @@
This module lets you define global date ranges that can be used to
filter your values in tree views.
It also provides a mixin model for developers that extends the model's
search view so that date ranges can be search as any relational field.

View File

@@ -0,0 +1,2 @@
The addon use the daterange method from postgres. This method is
supported as of postgresql 9.2

View File

@@ -0,0 +1,45 @@
To configure this module, you need to:
- Go to Settings \> Technical \> Date ranges \> Date Range Types where
you can create types of date ranges.
![](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_type_create.png)
- Go to Settings \> Technical \> Date ranges \> Date Ranges where you
can create date ranges.
![](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_create.png)
It's also possible to launch a wizard from the 'Generate Date Ranges'
menu.
![](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_wizard.png)
The wizard is useful to generate recurring periods. Set an end date or
enter the number of ranges to create.
![](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_wizard_result.png)
- Your date ranges are now available in the search filter for any date
or datetime fields
Date range types are proposed as a filter operator
![](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_type_as_filter.png)
Once a type is selected, date ranges of this type are porposed as a
filter value
![](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_as_filter.png)
And the dates specified into the date range are used to filter your
result.
![](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_as_filter_result.png)
- You can configure date range types with default values for the
generation wizard on the Generation tab. In the same tab you can also
configure date range types for auto-generation. New ranges for types
configured for this are generated by a scheduled task that runs daily.
![](https://raw.githubusercontent.com/OCA/server-ux/18.0/date_range/static/description/date_range_type_autogeneration.png)