Comments on: Siebel Hierarchical Picklist revisited

By: MSA

Mon, 14 Dec 2009 04:15:17 +0000

Another solution for Second Question:
—————————————-
Set the “Immediate Post Change” property to True for Country field. This will ensure that whenever the Country name is changed, the new value is updated in the database immediately. So, the State picklist will pick up the State values, based on the ‘new’ Country name.

However, please note that execessive use of Immediate Post Change property affects performance.

Neel/Danish – Please check if my answer is correct.

By: Danish (http://mailtodanish.blogspot.com)

Wed, 10 Jun 2009 05:05:55 +0000

Hi,
Siebel has given two seprate BC Picklist generic and Picklist Hierarchy.
According to my understanding ,Reson for this is performance only.

Picklist generic is used very commonly for statis picklist And this BC hav’t any join so data fetching is very fast and simple compare to picklist hierarchy ,that’s having self joins “Parent LOV”.

Dummy field in picklist hierarchy is just to make configuration simple.we can make it by a number of means.

Regards,Danish

By: Danish (http://mailtodanish.blogspot.com)

Wed, 10 Jun 2009 04:58:22 +0000

Hi ,
I would like to add a point here , technically differece between BC:picklist Generic and BC:Picklist Hierarchical is a BC property :”Cache Data” that consist “TRUE/False” vale.

TRUE — Data is read once for each query; that is, if the same query on a given business component is executed twice, the data is read only once. If the business component is queried again with different search specifications, the data is read again.

FALSE — Business component data is read each time the data is requested.

It is TRUE for Hierarchical Picklist and FALSE for Generic picklist.

Danish
“When you focus on giving you will never be at a loss”