This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
versago3:dataview_filters [2022/09/08 12:20] dlee |
versago3:dataview_filters [2023/10/30 09:17] (current) dlee [User-Applied Filters] |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| User-Applied Filters allow the user to provide input about how they want to filter the information for selection. | User-Applied Filters allow the user to provide input about how they want to filter the information for selection. | ||
| - | {{ :versago:reports6.png?600 |}} | + | {{ :versago3:dv_filters01.png?direct |
| - | - Select User-Applied Filter as the **Filter Type** | + | - Select User-Applied Filter as the **Filter Type** . |
| - | - Select the report value to be filtered from the **Filter Name** drop-down list. | + | - Select the data view field to be filtered from the **Field/Filter Name** drop-down list. |
| - | - **Display | + | - Type a **Display |
| - | - **Data Type** indicates the type of data of the “Filter Name” column. This is for information only and cannot be changed. | + | - **Control Type** defines the type of field used to enter the filter: |
| - | - **Control Type** defines the type of field the user sees for the parameter selection. Options are: | + | - **Dropdown** |
| - | - **Text** presents a text box where the user enters any value they wish. | + | - **Text** |
| - | - **Dropdown** presents a list of unique values from which the user can choose. | + | - **DatePicker** |
| - | - **DatePicker** | + | - **Numeric** |
| - | | + | - **Required** makes a filter |
| - | | + | - **Source** |
| - | - **Mandatory** is used to ensure that the user puts some value in this parameter. | + | - Dynamic creates a list of unique values from the data set. |
| - | - If a parameter is not mandatory | + | - Static allows the developer to create their own list of selection values. |
| - | - **Values | + | - **Operator** sets the default filtering option. |
| - | | + | - **Default Value** sets a default filtering value. The value can be changed by the user at execution time. |
| - | | + | - **Visible** indicates if the user sees the filter. A “Default Value” must be defined if this option is used. |
| - | - Static allows the developer to create their own list of selection values. These values must obviously make sense in the context of the data. If this option is selected an additional dialog page is presented to set the static values. See the // | + | - **Line Break** introduces a line break between filters when multiple filters are used. Otherwise, |
| - | - **Filter Criteria** sets the default filtering option | + | |
| - | - Options for text values include: | + | |
| - | - Equals (exact match) | + | |
| - | - Not Equal (exact match) | + | |
| - | - Contains | + | |
| - | - Starts With | + | |
| - | - Options for numeric and date values include: | + | |
| - | - Equal (exact match) | + | |
| - | - Not Equal (exact match) | + | |
| - | - Greater Than | + | |
| - | - Greater Than or Equal To | + | |
| - | - Less Than | + | |
| - | - Less Than or Equal To | + | |
| - | - Between (top and bottom values inclusive) | + | |
| - | - It is helpful to try and determine the most common filtering option and set it as the default. | + | |
| - | - **Default Value** sets a default filtering value. The value can be changed by the user at report | + | |
| - | - **Visible** indicates if the user sees the parameter or not. This option is used when the report designer wants to filter the report in the same way all the time but does not want to put the filter in the data selection code | + | |
| - | - A “Default Value” must be defined if this option is used. | + | |
| - | - **Control Visibility Order** has no significance for the report developer and can be ignored. | + | |
| - | Click the [**Add Filter**] button to add additional filters. | + | <WRAP center round important 80% > |
| - | Click the red **<color # | + | If **default** values are required for the **between** operator, separate |
| + | </ | ||
| - | ===== User Profile | + | ===== User Account |
| - | Profiles are filters | + | User Account |
| - | | + | {{ : |
| - | - Select the **Profile Name** from the “Filter Name” drop-down list. | + | |
| + | | ||
| + | - Select the **Account Filter** from the “Field/Filter Name” drop-down list. | ||
| - No other information is required. | - No other information is required. | ||
| + | |||
| + | **How to set up an Account Filter** | ||
| + | {{ : | ||
| ===== Application of Filters ===== | ===== Application of Filters ===== | ||
| - | - A report | + | - A data view can have multiple filters. |
| - User-applied filtering is applied based on the display order of the filters. This means that the first value filters the initial data set, giving a data subset. The next value then filters the first data subset, and so on. | - User-applied filtering is applied based on the display order of the filters. This means that the first value filters the initial data set, giving a data subset. The next value then filters the first data subset, and so on. | ||
| - | - Profile values | + | - User account filters |
| - | - When both parameters | + | - When both user-applied |
| - | - In the case where the parameter control is a drop-down list AND the available values listed are coming from the report data (dynamic vs. static): | + | |
| - | - For a Versago report, | + | ---- |
| - | - For a Crystal Report, the parameters are applied first and then the profile filtering is applied. | + | **[[versago3:dataview# |
| - | - The inconsistency between these two situations will be addressed in a future version of Versago. | + | |
| + | **[[versago3: | ||