About LoadData Method

Use the LoadData method to load business component data into a property set. The property set follows the vector format. The following table describes the input and output parameters for this method.

Note: Default the Search Spec, Sort Spec, Hierarchical Key, Key Field, Value Field, and Aggregate field arguments by defining these as user properties on the source business component. Pre-fix the BC user property with FINS Data Loader to identify these fields.

For example, define the default search spec as the Buscomp user property: FINS Data Loader Search Spec.

Parameter Name	Direction	Description
BusComp	Input	The name of a Siebel BC.
IsCachedData	Input	If true, the resulting vector is cached within the OM. Further requests to load data from the same business component are handled through the cache. Cached data is retrieved based on the business component name. If a second retrieval request uses different search spec, fields, format, and so on, release the original cached data first.
Search Spec	Input	The search spec applied to the business component when loading data. Since the FINS CAP Data Loader Service works outside the context of a business object, the search spec must include the appropriate user key fields.
Hierarchical Key [n]	Input	Hierarchical keys define the hierarchy within the vector. These keys identify the unique key at each level. Specify multiple hierarchical keys by defining [n] = 1, 2, 3 … n Refer to the ProductRate vector illustrated under Defining Properties for a Business Rule Process. In the ProductRate vector, Region and Product fields represent the hierarchical keys.
Sort Spec	Input	The sort specification applied to the business component when loading data. It is important to match the Sort Spec and the hierarchical keys when creating the vector. When a business component is accessed through the FINS CAP Buscomp Data Loader Service, sorting controls the shape of the parent/child tree structure. Records are processed sequentially and are aware of only the last parent node key. When children nodes are added to a parent node, they continue to be added until a new value is retrieved for the hierarchical key. When a new key value is discovered, a new parent node is immediate created, and children are assembled under that parent. This process continues until all records are collected. If a key equal to a previously processed node is retrieved after a different node key has been processed, a new node is produced rather than adding to the original.
Field [n]	Input	The name of Buscomp fields whose values are retrieved as the leaf propertyset properties. The property name is the field name, and the property value is the field value. [n]=1,2,… This represents one approach to how Buscomp fields can be retrieved. See Example of LoadData Method Using Field [n].
Key Field & Value Field	Input	Used to retrieve data as Key/value pair and store as a property in the leaf propertyset. The field value of the Key Field is the name of the property and the value of Value Field is stored as the value of the property. This is an alternative approach to Field [n] to retrieve data. See Example of LoadData Method Using Key Field and Value Field. Duplicate Key/Value pairs are not allowed. If duplicates are found when the vector is created, the new entry replaces the old entry.
Aggregate Field[n]	Input	Fields that are aggregated if duplicates occur. Multiple aggregate fields can be specified by defining [n] = 1, 2, 3 … n This parameter is useful with the Key Field/Value Field data retrieval approach. For example, a contact can have multiple income records with different types. If the Aggregate Field is defined, the data loader service automatically sums the income and stores this as a single income key/value pair.
Vector	Output	The resultant vector output.