FilterBehaviorFlags

This indicates none.

This indicates default value.

Turning on this flag will cause non-static (ex: dynamic custom fields/columns) to be ignored during the generation of filters and sort criteria.

If set, then the expression tree will generate a sql statement which will be logged.

This will only count the number of records matching criteria but DO NOT fetch and materialize any data from the database.

if

Reserved for internal tests

Before Public API, dynamic custom fields (DCF) values are returned using this naming convention: ''dcf_123' (where 123 is [dbo].[dcf].[dcf_id]). With advent of Public API, [dbo].[dcf].[dcf_label] is returned instead in addition to dcf_id as the Key. This will double the amount of data returned to the API consumer (namely MVC grid) so if dcf label is not being used by the grid, Do not return it to the consumer

Sometimes We want a grid to fetch extra (nested DTO models/objects) that is not directly related to the Server Side Grid Data. Strictly speaking, the grids only contain primitive scalar values (such as strings, decimals, inteters, etc). Complex data types, such as IList, IEnumerable, or nested DTO

This flag was introduced during implementation of Change Tracking Log Capture Query API. If specified, then information about the outer parent level will be fetched in the results returned. Note this flag differs from the flag FetchNestedDetailRecords since it fetches information about the record which is logically the ''grand-parent''.

Introduced this flag during implementation of Change Tracking Log Capture Query API. If set, get the change details, including the property name, the old/previous and the new/current value captured. By default, this flag is not specified. This flag fetchs records which are children of the current record.

If specified (turned on), then render this: ( xx.some_id IS NULL ) OR xx.some_id IN (1,2,3,4,...) INSTEAD OF THIS: ( xx.some_id IS NOT NULL ) AND xx.some_id IN (1,2,3,4,...)