Initial commit: Odoo 18.0-20251222 extra-addons
This commit is contained in:
23
date_range/readme/CONFIGURE.md
Normal file
23
date_range/readme/CONFIGURE.md
Normal 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:
|
||||
|
||||
> 
|
||||
|
||||
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"
|
||||
```
|
||||
8
date_range/readme/CONTRIBUTORS.md
Normal file
8
date_range/readme/CONTRIBUTORS.md
Normal 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>\>
|
||||
5
date_range/readme/DESCRIPTION.md
Normal file
5
date_range/readme/DESCRIPTION.md
Normal 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.
|
||||
2
date_range/readme/INSTALL.md
Normal file
2
date_range/readme/INSTALL.md
Normal file
@@ -0,0 +1,2 @@
|
||||
The addon use the daterange method from postgres. This method is
|
||||
supported as of postgresql 9.2
|
||||
45
date_range/readme/USAGE.md
Normal file
45
date_range/readme/USAGE.md
Normal 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.
|
||||
|
||||

|
||||
|
||||
- Go to Settings \> Technical \> Date ranges \> Date Ranges where you
|
||||
can create date ranges.
|
||||
|
||||

|
||||
|
||||
It's also possible to launch a wizard from the 'Generate Date Ranges'
|
||||
menu.
|
||||
|
||||

|
||||
|
||||
The wizard is useful to generate recurring periods. Set an end date or
|
||||
enter the number of ranges to create.
|
||||
|
||||

|
||||
|
||||
- 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
|
||||
|
||||

|
||||
|
||||
Once a type is selected, date ranges of this type are porposed as a
|
||||
filter value
|
||||
|
||||

|
||||
|
||||
And the dates specified into the date range are used to filter your
|
||||
result.
|
||||
|
||||

|
||||
|
||||
- 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.
|
||||
|
||||

|
||||
Reference in New Issue
Block a user