All Novulo applications allow for searches in every column in the search grid. By default, for text columns, the operator is contain: all results that contain the search string, are returned.
By default, when there are more than 10,000 rows to dispay, the application will only show the first 100 rows and disable sorting. This can be changed using web.config.
Furthermore, by default, the grid is queried with SQL default settings, preventing ‘dirty reads’. In applications with high usage, running with (readuncommitted) is typically preferred. Also this can be set using web.config.
Overriding grid defaults
The following web.config keys allow for changing default grid behaviour:
| Web.config key | Type | Explanation |
|---|---|---|
gridpanel.maxloadrows |
integer | The maximum number of rows that are displayed in a (fully functional) grid. Setting it to -1 disables the limit (not recommended). Default: 10000. |
gridpanel.maxsortrows |
integer | The maximum number of rows for which sorting a grid is allowed. Should be less than or equal to gridpanel.maxloadrows. Setting it to -1 disables the limit (not recommended). Default: 10000 |
gridpanel.selectwithreaduncommitted |
true/false | Setting this to true causes all grid-queries to do read-uncommitted reads. Default: false |
(for setting web.config keys, please refer to Allowing media hosts - #2 by j.batzke )
Overriding grid searches
Using prefixes in the search, it is possible to search differently, as it is visible using the question mark:
In some cases, users want to change the default behaviour from contains to starts with or equal.
Typically there are two reasons:
- For performance reasons: in large datasets,
starts withorequaloperators are considerably faster - To eliminate useless search results, like when searching in alphanumeric product codes, customer codes or invoice numbers
Using web.config settings, this can be modified at application level. As of today (3.9 framework) it is not yet possible to set it from the Architect or in-app configuration.
The syntax is at follows. In this example:
- For searches in the contacts table, on the field
invoice_address.postal_code, grid searches are now being performed usingstarts with - For searches in the purchases table, on the field
purchase_number, grid searches are now being performed usingequal
<novulo.presentationlayers.kendo>
<quickSearchOperatorOverrides>
<add dataType="contacts" fieldExpression="invoice_address.postal_code" defaultOperator="ValueStartsWith" />
<add dataType="purchases" fieldExpression="number" defaultOperator="Equal" />
</quickSearchOperatorOverrides>
</novulo.presentationlayers.kendo>
As this configuration is based on record types and fields, it can be copied between applications.
Overriding search link searches
Similar to the grid search, also search links search using contains. This can also be overridden, although in a different syntax.
It is also in the <novulo.presentationlayers.kendo> - both types must be combined into one section.
Here, the overrides are configured per element, based on elementId or structure ID.
The search expression here is defined as a Novulo expression; the search param is %0
<novulo.presentationlayers.kendo>
<searchLinkSearchExpressionOverrides>
<add elementId="125216" searchExpression="product.code.startswith(%0)" />
<add elementId="723769" searchExpression="number.tostring().equals(%0)" />
</searchLinkSearchExpressionOverrides>
</novulo.presentationlayers.kendo>
The elementId can be found using the browser plug-in.
These numbers are unique for every application so this configuration cannot be copied between applications without changing the ID’s.
