The QBE (Query By Example) Filtering tab of the Custom View Designer can be used to add fixed filters to Custom Views, limiting the amount of rows/objects they return.
To add a Filtering Condition in the QBE Filtering tab, follow these steps:
| 1. | Right-click the Expression node and select Add Condition from its context menu. |
| 2. | In the Edit Condition panel, configure the controls to create the desired filtering condition and click the Add button. |
An existing Filtering Condition can be modified by clicking it, changing the filtering settings and clicking the Apply button.
A Filtering Condition can be removed by right-clicking it and selecting Delete Condition from its context menu.
Limitations
When using decimal values or date values, the format used must match the regional settings of the computer used. This also applies for the generated output of BO-Layer projects using filtered Custom Views. When projects or their generated output are transferred to other computers using other regional settings, runtime errors may occur.
Currently the QBE values requested (typed) are not strongly typed so when used be aware that you must use the format from your machine regional settings (culture).Also, if the DataStore (or the BOLayer) is used on a different machine the cultures must be the same or otherwise the test will fail with a casting error.
Filtering Conditions using decimal values and dates will be made insensitive to regional settings in a future release: issue tracking number ERS#2889.
See also
GenWise Studio has various other options for filtering data:
The NHibernate Templates support Filtering and Sorting using NHibernate's ICriteria querying technique.
With the ASP.NET 2.0 Templates, various forms of filtering can be used on the Browse Template, see: static filtering, dynamic filtering and advanced filtering.