|
Siebel Developer's Reference > User Properties > Business Component User Properties >
Sort Field Map n
Several opportunity-related business components, such as Opportunity and Global Account Opportunity, have a one-to-many relationship with the Revenue business component. These relationships enable master/detail views that display the revenue records associated with an opportunity. Opportunities typically have several multivalue fields that reference fields in the Revenue business component. For example, the Revenue and Close Date fields on the Opportunity business component reference the Revenue and Date fields on the Revenue business component, respectively. Existing predefined queries on opportunities may include sort specifications based on one or more of these multivalue revenue fields. The Sort Field Map user property is used at run time to redirect such sorts on revenue multivalue fields to corresponding single-value fields on the opportunity. For example, a sort specification on the Revenue multivalue field on the Opportunity business component is typically redirected to the Primary Revenue Amount field, which is the revenue amount for the opportunity's primary revenue record. NOTE: It is unlikely that you need to use this user property to redirect new predefined queries. Instead, write the sort specification to reference a single-value field, as described in the Usage topic for this user property.
For information on sort specifications in predefined queries, see About Sorting Through Predefined Queries. For information on the primary revenue record for an opportunity, see Siebel Applications Administration Guide.
Value |
"field", "redirect field" where:
- field is the name of a multivalue field on the current opportunity-related business component, such as Close Date or Revenue, that maps to a field on the Revenue business component.
- redirect field is the name of the single-value field on the current opportunity-related business component that maps to the same revenue field on the primary revenue record for the opportunity, for example, Primary Revenue Close Date or Primary Revenue Amount.
|
Usage |
This property can be specified with or without the numeric suffix. However, typically several instances are added to specify redirection of several revenue fields, so the numeric suffix differentiates the instances. For example, define the following user properties on the Opportunity business component, as well as similar ones for other revenue fields:
- Sort Field Map 1 with value "Revenue","Primary Revenue Amount"
- Sort Field Map 2 with value "Close Date","Primary Revenue Close Date"
For the sort specification 'Opportunity'.Sort = "Revenue (Descending)"in a predefined query, the result set would be sorted in descending order of the revenue amounts in the primary revenue records of the opportunities in the result set. Similarly, the sort specification 'Opportunity'.Sort = "Close Date "in a predefined query would base the sort on the revenue close dates in the primary revenue records. NOTE: For new predefined queries, do not set sort specifications to reference multivalue fields. Instead of necessitating the redirection by the Sort Field Map user property, define the sort specification with the corresponding Primary Revenue field initially. For example, define the preceding sort specification as 'Opportunity'.Sort = "Primary Revenue Close Date".
Do not inactivate or modify the values for this user property. You can create new instances of this user property. See also About Setting Numbered Instances of a User Property. |
Parent Object Type |
Business Component |
Functional Area |
Predefined queries on opportunity-related business components |
|
