Populate a Select Datum

Hi all,

my environment is TS 6.7.1 SP1 and LS 3.0.2.

I would like to dynamically populate a Select datum in a component.

I would like to read all the Options values and labels in a database and show a Select Single datum to the user with those values so he can choose a value that is used by the component to display some content.

Is this possible?

Thank you for your help.

Find more posts tagged with

Comments

Stokes

The answer is "Generator", but I'm not sure where to direct you in 3.0.2 because I don't think it's in the docs.

The syntax is something like:


<Datum Exposed="true" ID="SAMPLE1" Name="Selection 1" Type="SelectSingle">
  <Generator Method="getSampleOptions" Object="com.interwoven.livesite.external.runtime.example.SampleGenerators"/>
</Datum>

So the method getSampleOptions() gets called on the Java class SampleGenerators to generate the

s.

You might search your LS install for

*Generator*

to see examples, and I think that SampleGenerators class will be in the runtime .jar so you can get the method signature there.

--Stokes.

sabeer

Hi,

You can also try the below solution for your queries.

1)Call the external in your component as like below ex:

< Datum Exposed="true" ID="PARAM-1" Name="Sample" Type="SelectSingle" >
< External >
< Object >com.XXXX.XXXXX.XXXXX.Sample< /Object > < Method >GetListing< /Method >
< /External >
< Option Order="1" Selected="true" >
< Display >-----Loading...-----< /Display >
< Value/ >
< /Option >
< /Datum >
2)In your sample class create the Connection to DB and get the values and populates those values like below:

< Options >
< Option >
< Display >DBVal1< /Display >
< Value >DBvalue1< /Value >
< /Option >
< Option >
< Display >DBVal2< /Display >
< Value >DBvalue2< /Value >
< /Option >
< /Options >

3)This will create dynamic data from the DB to your select List.

Hope this will help you..

Cheers

AlexC

Generator is the right way to do it, the above example one works in 2.2.1 and was deprecated in 3.0.

michaelangel0

Generator is the right way to do it, the above example one works in 2.2.1 and was deprecated in 3.0.

While the Generator looks like the right way to go on the face of it, in reality it doesn't appear to work.

It is possible to create a java class with a method that returns a document node containing a bunch of options, but the resulting content in the Datum element does not match what is expected by the component editor.

According to the LiveSite Developers Guide, the SelectSingle (and other datum types that define options) the XML should be of the form :

[html]

Label 1Value 1
Label 2Value 2

[/html]

but what results from using the is:
[html]

Label 1Value 1
Label 2Value 2

[/html]

If you try to edit the component in a SitePublisher page you get a message saying :

One or more properties (marked in red below) were automatically updated because their current value was out of sync with the available values. To save the updated values click the Apply button below. .

The additional <Options> element is messing things up. I can only assume it was included so that a valid XML Document could be returned by the generator method (multiple document nodes not being allowed) but it appears that this structure is not valid within the context of the Datum element.

Any one got any ideas how this might be resolved?

AlexC

The Options are not additional, they replace the defaults (from what I remember). So if you have a value selected that is not part of the returned by Generator then it will complain about the sync.

Tyr using only values generated by Generator.

michaelangel0

Thanks, I see how it works now. What was throwing me was the fact that the selected option appears separately from the other options in the generated XML (for the page):

[html]

Item0
Item_0

Item0
Item_0

Item1
Item_1

Item2
Item_2

[/html]

combined with the fact that my XPath had been written as Options/Option[@Selected='true'] when attempting to retrieve the selected option whereas I should just have specified Option[@Selected='true'].

Many thanks