Sorry about the vagueness in the first post. Reading back over it, I jumped straight to talking about what I’d tried to solve the problem, without properly outlining what the problem was.
It’s pretty simple.
Setting it up:
[ul]
[li]Make a new repeater.
[/li][li]Put a droplist widget in the repeater.
[/li][li]Throw some values in to the droplist.
[/li][li]Make a new column in the repeater dataset and fill it with values that match those you put in the repeater.
[/li][/ul]
The problem:
[ul]
[li]How do you get the droplist to display the values in the dataset?
[/li][/ul]
As I said before, it looks as though this isn’t possible directly.
So I tried:
[ul]
[li]Add a label widget to the repeater, hidden behind some other element.
[/li][li]Fill label widget with values from the dataset.
[/li][li]As the final action in the repeater’s onLoad interaction, add a “Set Selected List Option” in the case editor, targeting the droplist in the repeater.
[/li][li]Under “Set selected option to,” set “Text on widget,” and point it to the label widget.
[/li][/ul]
But… that doesn’t seem to do anything. In fact, I can’t really understand why that particular action sequence exists, since it doesn’t seem to be capable of affecting a droplist, even outside of a repeater.
So, failing that, I’m curious as to whether anyone has come up with a simple workaround, or if my only option is to build a fake droplist out of tables – or avoid the combination altogether.
Cheers.
That narrowing of search results you talk about isn’t really what I was after, however it sounds like a pretty sweet piece of work. I reckon a lot of people here would be interested to know how you achieved it.