[18.0][MIG] base_search_custom_field_filter: Migration to 18.0 #1017
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…via UI
This module allows to define custom filters in the search views for an specific
field belonging to the document or any other related document.
This nature makes the definition quite technical, but once done, it adds the
element in the UI for regular user use.
Configuration
=============
* Go to *Settings > Technical > User Interface > Custom Field Filters*.
* Create a new record, and define following information:
* The **Model** for which you are defining the filter. It will appear in all
the search views of this model.
* The label you want to see on the search line on the **Name** field. This
field allows translations for proper UI in different languages.
* The **Expression**, which is the field chain string with dot notation.
Examples: `product_id`, `product_id.seller_ids.name`, `partner_id.lang`.
* Optionally, you can fill **Position After** for indicating after which
existing field (technical name) the filter will appear. If empty or not
found, the filter will be added at the end.
* You can reorder records for determining sorting for multiple filters for the
same model with the arrow handle in the left part.
Usage
=====
* Go to the menu entry for which you have defined the custom field filter.
* On the search bar, type anything.
* In the filter list, you will see the line for the element you have defined.
As demo data, a custom field filter is included for sample purposes.
Steps for trying this sample:
* Install `contacts` module.
* Go to *Contacts*.
* Type "english" and you'll find the filter "Language" at the end.
…h same field content If the field you are looking for is a relational one, and contains the same value in different records, when you unfold the results and select one of them, the results of the search belongs to the first ocurrence instead the specific selected record. This is due to Odoo JS code using same operator in this kind of search when filter_domain is used in the filter. We avoid this letting the standard field code to act, but injecting a custom attr that overwrites the left leaf of the domain.
Currently translated at 94.7% (18 of 19 strings) Translation: server-ux-14.0/server-ux-14.0-base_search_custom_field_filter Translate-URL: https://translation.odoo-community.org/projects/server-ux-14-0/server-ux-14-0-base_search_custom_field_filter/es/
Currently translated at 100.0% (19 of 19 strings) Translation: server-ux-14.0/server-ux-14.0-base_search_custom_field_filter Translate-URL: https://translation.odoo-community.org/projects/server-ux-14-0/server-ux-14-0-base_search_custom_field_filter/it/
…ression has related fields (dot notation). TT38575
Currently translated at 100.0% (19 of 19 strings) Translation: server-ux-16.0/server-ux-16.0-base_search_custom_field_filter Translate-URL: https://translation.odoo-community.org/projects/server-ux-16-0/server-ux-16-0-base_search_custom_field_filter/es/
Currently translated at 100.0% (19 of 19 strings) Translation: server-ux-16.0/server-ux-16.0-base_search_custom_field_filter Translate-URL: https://translation.odoo-community.org/projects/server-ux-16-0/server-ux-16-0-base_search_custom_field_filter/it/
absal-smile
force-pushed
the
18.0-mig-base_search_custom_field_filter
branch
from
3efeeb6 to
07bea92
Compare
pedrobaeza
changed the title
|
/ocabot migration base_search_custom_field_filter |
absal-smile
force-pushed
the
18.0-mig-base_search_custom_field_filter
branch
4 times, most recently
from
0a05e84 to
536f779
Compare
|
@absal-smile you should require to cla@odoo-community.org for being included in the Smile ICLA for not having every workflow to be approved. |
absal-smile
force-pushed
the
18.0-mig-base_search_custom_field_filter
branch
from
536f779 to
9f3d8d9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.