Examples of search terms

Checkboxes can have one of three states. For searching for these states, the search terms in the table are available.

The search terms can be combined, e.g., n | null returns all checkboxes that are not set or empty.

Choice box and radio button fields only save certain entries specified by the selection. You can select these entries for use as search terms in the Quickfinder.

Searching in date fields is also possible in the Quickfinder, but is much more convenient using the search in the filter form. There are several search operators for searching in the Quickfinder in order to search

• for a specific date,
• before or after a specific date,
• within a time period (from day 1 to day 2).

Entering incomplete date values is supported. Date values are automatically recognized based on the data format of the relevant field (as well as in the field itself). The Quickfinder qualifies as follows:

Input: 230507 is recognized as (> =23.05.2007 & <=23.05.2007) and delivers as a result only this date.

Input: <010104 is recognized as <01.01.2004 and returns all results before (until) this date.

Input: >010104 is recognized as >01.01.2004 and returns all results after this day.

If you use the equals sign (=) after the respective relation sign, you will include the respective date in the search.

Input: >010108 & <010608 is recognized as >01.01.2008 & <01.06.2008 and delivers the results from 1/1/2008 to 6/1/2008.

Input: >=010108 & <=010608 is recognized as >=01.01.2008 & <=01.06.2008 and delivers the results including 1/1/2008 to 6/1/2008 included.

If the ampersand is not set between the character strings, then it is an OR query that the system interprets as such: Show all results except for the specified restriction.

Input: >010108 <010608 is recognized as> 01.01.2008 <01.06.2008 and delivers only the results before 1/1/2008 and after 6/1/2008.

Tip: Rather open the filter form, find the date field concerned, and use convenient attributes such as "from the", "until the" within" etc.

The search for phone numbers for external contacts can be extended to the internal telephone fields. This feature can be activated via environment variables and is activated by default.

All non-numeric characters are removed when searching for telephone numbers. A leading + is replaced by 00.

Search entries in numerical fields cannot contain wildcard characters (% or ?). The system prevents you from entering them.

In text or BLOB fields, you can find empty entries using null, and non-empty entries using % or !null. For all other field types (integer, float, money, logic, date), null or !null must be entered in the Quickfinder.

In the Web-Client simply click on the field selection at the Quickfinder and see the fields with check mark for which a search entry exists.

In a structured scope of delivery of a sales or service transaction that is displayed expanded, the Quickfinder can only find those lines in the expanded list as hits that are at the top level.

The behavior of the search in a structured scope of delivery is due to technical reasons, as the scope of delivery is represented as a tree.

For reports in noselect mode (e.g. overview list of all cases), filters and search entries are evaluated in the dialog. The search conditions and the sorting defined in a filter are transferred to the loader. Any sorting defined in the loader is overloaded.

In some scenarios, it is not possible to search using the Quickfinder because the fields are either not visible in the form or are locked or only represent a status at runtime, such as various BLOB fields. Example:

Synchronization state

The synchronization status of an appointment cannot be searched for via the Sync.status field, as this is a Calculate field that is only calculated at runtime.

The following assignments apply to the PSA_ACT.SYN_PIC field:

• "PSA_OEX_NON" (or empty): not synchronized
• "PSA_OEX_EXP": exported (CRM to Groupware)
• "PSA_OEX_IMP": imported (Groupware to CRM)
• "PSA_OEX_CFL": conflict (competing change in the CRM and groupware)
• "PSA_OEX_ERR": Error during synchronization

Since the multi-language message text of one of the five messages is written into this calculate field (e.g. PSA_SYN_STA_NON or PSA_SYN_STA_EXP), you can filter for "Contains one of the words" (case-sensitive) on this blob name and enter "NON", "EXP", "IMP", "CFL" or "ERR" as a word to restrict the activi­ties to one of the categories.