Find Field Object Rules and Assumptions

• Boolean operators are not supported when searching on a Find object.

• The field specified in a find field must be a field that exists in the business component for the applet for the Find object definition.

• The Search Center-Find category and a query by example (QBE) can have different behavior for multi value fields, because the Search Center will generate the same query as if you did an EXISTS query on the field in QBE. You can verify this by embedding your QBE expression with Exists(), for example, (Ada*).

• QBE supports both types of querying, but to keep the Search Center simple, Siebel CRM implements a query that works in all cases. This query uses the syntax Ada* (where the wildcard, as indicated by an asterisk (*) is appended to the search text). If you want to mimic the behavior of the nonExists version with the Search Center-Find category, you must create a join from the primary ID field for the MVLink to the table containing the data. Then add a field to the table you joined to, and point your find field to this new field. This configuration change will cause the query to do a query on the join field that does not use EXISTS.

• If you want to do an exact search in a Find field, prefix the search text with an equal sign (=), for example, = Ada. The query uses the syntax = Ada. (No wildcard is appended to the text.)

• Do not configure the State field as a Find Field for a Find object.

  For example, if the Accounts Find object configuration in Siebel Tools includes the State Find Field, then the State field appears as an option (in the Accounts Find object menu) in the UI. In such a case, do the following in Siebel Tools to remove the State field from the Accounts Find object menu:

  • Deactivate the Find Field, then update the repository and deliver the update.

  • Disable the State field for the required language.

  • Disable the State Find Field for the Accounts Find Object.