Object Types Reference > Siebel Object Types >

Pick Map

Siebel Object Types > Business Component > Field > Pick Map

Specifies instructions for copying fields when a picklist is used by a field.

Properties

Property
Description/Usage
Valid Values/Examples
Constrain (O)
A TRUE or FALSE value.
TRUE = Defines the pick map as a constraint pick map.
FALSE = Defines the pick map as a copy pick map.
Field (R)
The field in the parent business component with which the pick map is dealing.
 
No Clear (O)
A TRUE or FALSE value.
TRUE = Causes the field specified in the pick map not to be set to NULL when no value is picked from the picklist.
Pick List Field (O)
The field in the picklist business component with which the pick map is dealing.
 
Sequence (O)
Integer value that specifies the order in which the field values will be copied back to the business component after a particular row has been picked.
Note that Siebel applications do not always use the Sequence property of Pick Map. Pick List Source Id will always get set first, overriding Sequence in the Pick Map.
 

See Also

Business Component
Field
MVF Pick Map
Pick List
Pick Map UpdOnlyIfNull
SVF Pick Map

Usage

Siebel Object Types > Business Component > Field > Pick Map

Copy and constraint pick maps

There are two kinds of pick maps: copy pick maps and constraint pick maps. The type of pick map is determined by the value in the Constrain property. If a pick map is a copy pick map, then the value of the field in the picklist business component specified by the Pick List Field property will be copied into the field of the parent business component specified by the Field property. If the pick map is a constraint pick map, then the value from the field in the parent business component specified by the Field property will be applied as a search specification on the field in the picklist business component specified by the Pick List Field property.

Constraining picklists on multi-value fields

You cannot use a field in the parent business component to constrain a picklist on a multi-value field. You can use only multi-value fields that are part of the detail business component.


 Object Types Reference 
 Published: 18 April 2003