Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
protogrid:filter [2020-04-18 15:54] – dru | protogrid:filter [2023-05-16 13:57] (current) – [Filter] dru | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Filter ====== | ====== Filter ====== | ||
- | A Filter is basically a field for choosing a filter | + | Protogrid has built-in |
- | Currently there exist to sorts of filter fields: | + | For every field type you can control specific behavioral aspects which are related to data filtering. |
+ | |||
+ | Additionally to data filters Protogrid provides 2 data security features to restrict access to data: "Read Access Role Definition" | ||
+ | ==== Filter Options ==== | ||
+ | |||
+ | Depending on the field type you have any of the following filtering options available for a field definition: | ||
+ | |||
+ | === Limit Using Compatible Filters on the same Card === | ||
+ | |||
+ | Available for: Relation Field Definition, Tag Field Definition | ||
+ | |||
+ | The available choices are filtered using neighboring relation fields and filters that use the same Proto as a relation field in the target data. | ||
+ | |||
+ | === Additional filter based on read access setting === | ||
+ | |||
+ | Available for: Relation Field Definition | ||
+ | |||
+ | The available choices are filtered based on the read access rights of the target data. The system default is that users can see the shortname of a card, even when the card itself is resticted from access using a read access role definition. | ||
+ | |||
+ | === Disable filter effect on neighboured fields on the same card === | ||
+ | |||
+ | Available for: Relation Field Definition | ||
+ | |||
+ | With this option you can disable the filtering effect on neighboring relation or tags fields. | ||
+ | |||
+ | === Filtering of cards represented in this field === | ||
+ | |||
+ | Available for: TableView Definition | ||
+ | |||
+ | With this option you can control if the TableView is filtered at all, only by filter fields, only by relation fields, or both. | ||
+ | ==== Filter Fields ==== | ||
+ | |||
+ | A Filter field is basically a field for choosing a filter condition and limiting which Cards are shown in a Table View or Chart View. | ||
+ | |||
+ | Currently there exist 4 types of filter fields: | ||
* Relation Filter Field | * Relation Filter Field | ||
+ | * Text Filter Field | ||
+ | * Number Filter Field | ||
* Date Filter Field | * Date Filter Field | ||
+ | |||
+ | === Relation Filter === | ||
+ | |||
+ | A relation filter field let's the user select from the available values in the target field and limits the embedded tableview based on the selection. | ||
+ | |||
+ | === Text Filter === | ||
+ | |||
+ | A text filter field let's the user enter any input. Filtering occurs only on full match of the input term. | ||
+ | |||
+ | Please note that the content of text fields is relevant for filtering only up to and including the 300th character. | ||
+ | |||
+ | === Number Filter === | ||
+ | |||
+ | A number filter field let's the user enter any input. Filtering occurs only on full match of the input number. | ||
+ | |||
+ | === Date Filter === | ||
+ | |||
+ | A date filter field provides a date picker to select a date. Filtering for time values is not supported. | ||
+ | |||
=== Example: Creating a Relation Filter to filter a Table View === | === Example: Creating a Relation Filter to filter a Table View === | ||
Line 15: | Line 70: | ||
- Save & Close the " | - Save & Close the " | ||
- The new " | - The new " | ||
- | - Open the Table View, you want to filter, and use the new " | + | - Open the Table View you want to filter, and use the new " |
=== Example: Creating a Date Filter to filter a Chart View === | === Example: Creating a Date Filter to filter a Chart View === |