Using the [NOT] EXISTS Operator with Multivalue Groups

To reference a multivalue group field, you can specify the [NOT] EXISTS operator in a query by example or in the Search Specification property of an object. Siebel CRM uses a multivalue group field to display the child records of a parent record in the parent record applet. For example, assume the following:

• Opportunities are a separate entity.

• Contacts are a separate entity.

• The Opportunity business object references the Opportunity and Contact business components.

• A many-to-many relationship exists between opportunities and contacts:

  • One or more contacts can modify an opportunity.

  • A contact can modify one and only one opportunity.

• A form applet displays and manages opportunity information and displays any contact information that is specific to the opportunity. This applet includes the following fields that reference the Opportunity business component:

  • Opportunity Name

  • Contact First Name

  • Contact Last Name

This form applet displays the opportunity name in a predefined text box control. Siebel CRM defines the contact first name as a multivalue group field and the last name as a multivalue group field instead of as predefined edit controls. If you use query by example on a multivalue field (MVF), then you must include only multivalue fields that Siebel CRM displays in the originating business component.

Assume you set the search specification for the opportunity name to the following value:

Wine Festival

In this example, the Opportunity business component returns all opportunities that contain a name of Wine Festival.

Assume you set the search specification for the contact last name to the following value:

Smith

In this example, the Opportunity business component returns all opportunities that include a contact with a last name of Smith. This situation occurs because you defined the search specification on the Opportunity business component and not on the Contact business component.