Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
visionx:data_modeling_and_representation [2020/06/08 12:18] cduncan [Filters] |
visionx:data_modeling_and_representation [2020/06/08 12:21] cduncan [Specify a BETWEEN filter] |
||
---|---|---|---|
Line 505: | Line 505: | ||
{{:visionx:data_modeling_and_representation:filters_step3.png?nolink|Filters: result desktop}} | {{:visionx:data_modeling_and_representation:filters_step3.png?nolink|Filters: result desktop}} | ||
- | ===== Filters use IConditions ===== | + | ===== Filters Use IConditions ===== |
How does this work? Each filter editor creates an [[http://www.sibvisions.com/files/jvx/current/api/index.html?javax/rad/model/condition/ICondition.html|ICondition]] and is connected to other conditions by the logical operator AND. In other words, if multiple filters are set, the result contains only those rows that match all of the filters. | How does this work? Each filter editor creates an [[http://www.sibvisions.com/files/jvx/current/api/index.html?javax/rad/model/condition/ICondition.html|ICondition]] and is connected to other conditions by the logical operator AND. In other words, if multiple filters are set, the result contains only those rows that match all of the filters. | ||
- | Of course VisionX supports more than one search mode to use in filters and conditions. These are: | + | Of course, VisionX supports more than one search mode to use in filters and conditions. These are: |
^Search mode ^Description ^ | ^Search mode ^Description ^ | ||
Line 521: | Line 521: | ||
|**Starts with** |Matches all literals that start with the entered value ignoring the character casing. <html><br></html>Supports ?, * and % as wildcards. | | |**Starts with** |Matches all literals that start with the entered value ignoring the character casing. <html><br></html>Supports ?, * and % as wildcards. | | ||
- | All the above filters operate on a specific column. | + | All of the above filters operate on a specific column. |
- | ===== Full text search ===== | + | ===== Full Text Search ===== |
- | And what about the default search editor, we've used in all our screens so far? If you just drag and drop the "Search" editor to a screen, a filter with the following specification is created: | + | What about the default search editor we've used in all of our screens so far? If you just drag and drop the "Search" editor to a screen, a filter with the following specification is created: |
^Search mode ^Description ^ | ^Search mode ^Description ^ | ||
Line 532: | Line 532: | ||
The "full text search filter" operates on all columns of the data object. | The "full text search filter" operates on all columns of the data object. | ||
- | ===== Specify a BETWEEN filter ===== | + | ===== Specify a BETWEEN Filter ===== |
- | Let's implement the possibility to filter for assets issued in a specific timespan, in other words, between two dates. Simply drag and drop two Search Editors and bind them to "[Localized Assets.Issue Date]" (1). Use "Greater equals" (2) for the first filter and "Less equals" for the second filter. | + | Let's implement the possibility to filter for assets issued in a specific time span, in other words, between two dates. Simply drag and drop two search editors and bind them to "[Localized Assets.Issue Date]" (1). Use "Greater equals" (2) for the first filter and "Less equals" for the second filter. |
{{:visionx:data_modeling_and_representation:filters_step4.png?nolink|Filters: specify between filters}} | {{:visionx:data_modeling_and_representation:filters_step4.png?nolink|Filters: specify between filters}} |