Specifying Search Specifications with Multiple Integration Objects
You can customize a report so it that it runs across multiple business objects. To do this, you use multiple integration objects, where one integration object is the primary and all others are nonprimary integration objects.
If you specify an integration object in the report template in the Integration Objects list, then the search specification property of every nonprimary integration object must include a valid search specification. For example, you can use the following format:
'Integration_Component_Name'.Search = "[Field_Name] = ""value_to_filter"""For example:
'Contact'.Search = "[Last Name] = ""Sh"""Siebel CRM sends the query that a user runs in a view to the primary integration object. It does not send this query to a nonprimary integration object. It requires a valid search specification so that it can filter the data for nonprimary integration objects. If a nonprimary integration object does not include a valid search specification, then this integration object returns all data from the business components, including unwanted data, and it might degrade performance.
It is recommended that you test these search specifications to make sure they are valid. For more information about search specifications, see Configuring Siebel Business Applications.
How Siebel CRM Applies Search Specifications to Filter Reports
The following items can filter the records that Siebel CRM displays in a report:
Client query (the user enters a query in a field)
Predefined query
Search specification on the business component
Search specification on the applet
Search specification on the integration object
The following table describes different examples Siebel CRM applies search specifications to filter reports. In all rows, assume that the applet and the business component each include a search specification. For example, the first row describes how Siebel CRM filters records if the user enters a query in the client, does not use a predefined query, there is no search specification for the integration object, and the applet and the business component each include a search specification. For more information about creating search specifications, see Configuring Siebel Business Applications.
| Client Query | Predefined Query | Integration Object | Filters That Siebel CRM Applies |
|---|---|---|---|
Y |
N |
N |
Applies the UI query, applet search specification, and business component search specification. |
N |
Y |
N |
Applies the predefined query, applet search specification, and business component search specification. |
Y |
N |
Y |
Applies the applet search specification and business component search specification. Appends the integration object search expression and overrides the UI query. For more information about search expressions and sort specifications, see Configuring Siebel Business Applications. |
N |
Y |
Y |
Applies the applet search specification and business component search specification. Appends the integration object search expression and overrides the predefined query. |
The following items apply for each row in the previous table.
The Position automatically preserves visibility, organization visibility, and view mode. For information, see How Siebel Controls Access to Reports.
Using the CTRL key to choose records does not affect query behavior. For more information, see Using the CTRL Key to Choose Multiple Records for a Report.
Mobile Web Client functionality is not adversely affected.
Multilingual behavior does not affect the functionality.