WebOffice author > Edit Menu > WebOffice Category > Layer Queries > Query

The Search Field List specifies all search fields available

•	for predefined queries

•	in the query builder form

The definable parameters has impact only on the query builder, since with predefined queries search fields are not selectable for the user.

Search field list configuration

Property

Description

Sort order

Specifies the overall Sort order:

•

ascending

•	descending

Search field list properties

Search Field

Add various Search Fields via right-mouse context menu.

Note: If a field has an attributive index in the database, the field is marked with *.

Search field configuration

Property

Description

Field

Search field. Either a layer field or a table field is referenced.

Note: Define in the Basic Settings whether you want have alias or technical names displayed in the drop-down list.

Alias

Name (alias) to be used for the search field in the WebOffice 10.2 SP3 clients.

Note: It is recommended to use either Geodatabase alias or ArcMap alias definitions instead If possible. See chapter Field Alias for details about best practices regarding alias names.

Sorting

Sorting is either done

•	according to the database field type (fieldtype) or

•	by means of a specific WebOffice sorting algorithm (for TEXT fields only, especially useful for house or parcel numbers and other alphanumerical values) when using configuration value alphanumeric.

Do case insensitive search?

Perform a case insensitive search (Yes) or not (No).

If search performance is poor this may be due to case insensitive search mode. Try "No" then.

Note: Querying a table of an Oracle DB case insensitive will disable the attribute index of the table, leading to a performance decrease.

A query on a search field (type String) from an Oracle DB only works with indexing if

•	the query is executed "case insensitive" (do case insensitive search - No) and

•	the Oracle Index is a functional index on upper case letters ("function based index" on "UPPER" function).

Note: Case insensitive search on feature classes with Joins in Oracle DBs using NLS_UPPER will only work, if:

-	The option ‘keep only matching records’ is set on the ArcMap Join

-	The source table (feature class) and target table (Join table) are from the same data source

If these preconditions are not reached, the Join operation will not work.

For external Calls only?

Defines whether the search field may only be used for external parametrized calls. If activated, the field is neglected for the query builder and the full-text search.

Note: If all defined search fields are defined for external calls only, then the query builder cannot be opened. A warning message will say "The query is not available" (no valid search fields).

Note: It is possible to check in SynAdmin which search fields are indexed for the full-text search. See the HowTo chapter Full-Text Search for details.

Search field properties