Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Developer's Reference > Business Component User Properties > Controlling Search and Sort > Specifying How to Sort Predefined Queries for OpportunitiesThe Sort Field Map n user property determines how Siebel CRM sorts a predefined query on a business component that stores opportunity data. It uses the following format:
A one-to-many relationship exists between a business component that handles opportunity data and the Revenue business component. This relationship enables the master and detail view that displays the revenue records that Siebel CRM associates with an opportunity. The Opportunity business component and the Global Account Opportunity business component are examples of business components that handle opportunity data. Opportunities typically include multivalue fields that reference fields that reside in the Revenue business component. For example, the Revenue field that resides in the Opportunity business component references the Revenue field that resides in the Revenue business component. An existing predefined query on opportunities might include a sort specification that references one or more of these multivalue revenue fields. The Sort Field Map user property redirects this sort to the corresponding single-value field in the opportunity at runtime. For example, it redirects a sort specification that resides on the Revenue multivalue field in the Opportunity business component to the Primary Revenue Amount field. This field contains the revenue amount for the primary revenue record of the opportunity. You can use the Sort Field Map n user property to specify how Siebel CRM does this redirect. You can specify this user property with or without the numeric suffix. However, you typically add multiple instances to redirect multiple revenue fields. The numeric suffix differentiates these instances. For more information, see Numbering Instances of a User Property. You must not configure Siebel CRM to deactivate this user property or modify the value for it, but you can configure Siebel CRM to create a new instance of it. For information about configuring a sort specification in a predefined query, see Configuring Siebel Business Applications. For information about the primary revenue record for an opportunity, see Siebel Applications Administration Guide. Example of Configuring the Sort Field Map User PropertyFor an example of configuring the Sort Field Map user property, assume you define the user properties that Table 22 describes in the Opportunity business component. In this example, the following sort specification in a predefined query provides a result set that Siebel CRM sorts in descending order according to the revenue amounts that exist in the primary revenue records of the opportunities: 'Opportunity'.Sort = "Revenue (Descending)" The following sort specification in a predefined query provides a result set that Siebel CRM sorts according to the revenue close dates that exist in the primary revenue records: 'Opportunity'.Sort = "Close Date " Alternative to Configuring the Sort Field Map User PropertyFor a new predefined query, it is recommended that you do not configure the sort specification to reference a multivalue field. You can configure the sort specification to reference a single-value field instead of using the Sort Field Map user property to do a redirect. For example, you can use the corresponding Primary Revenue field. You can use the following instead of using 'Opportunity'.Sort = "Close Date ": |
![]() ![]() |
Siebel Developer's Reference | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |