FieldCapabilities Enumeration |
Namespace: NetQuarry.Data
Member name![]() | Value![]() | Description | |
---|---|---|---|
Sorting | 0 | The field can be used to sort. Generally a field can be sorted unless it is marked with ExcludeFromSelect (indicating that there may be no underlying column) or is bound to a column with an unsortable data type (e.g. LongVarChar in SQL-Server). | |
Filtering | 1 | The field can be used to filter. Generally a field can be used to filter unless it is marked with ExcludeFromSelect (indicating that there may be no underlying column) or is bound to a column with an unfilterable data type. | |
Setting | 2 | The field's value can be set. Generally a field can be set unless it is marked with ExcludeFromSelect (indicating that there may be no underlying column), is an Identify column, or has a CellType for which setting is not meaningful (e.g. a Button). | |
Saving | 3 | The field's value can be saved. Generally a field can be saved unless it is marked with ExcludeFromSelect (indicating that there may be no underlying column), is an Identify column. | |
UnsecuredUse | 4 |
The field can be used where its value may be accessible to the user even when the field
is not supposed to be visible. The following rules are observed as to which fields are allowed for unsecure use when not explicitly visible:
| |
Reading | 5 | The field value can be read. Generally a field can be read unless it is a password field or it is permissioned to not allow Read access. | |
Navigating | 6 | The field can be used as a link to navigate. This applies only to fields for which navigation is relevant and is primarily driven by the Navigation field permission. | |
SizingHorizontally | 7 | The field can be resized horizontally during layout. | |
SizingVertically | 8 | The field can be resized vertically during layout. | |
StrictUnsecuredUse | 9 | Similar to UnsecuredUse except that the application is always considered to have IsStrictMode set. |