Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread Dawn Lockhart
My bad, it does work. I didn't have a selection set and was looking at the item instead. Thanks for the quick reply! Dawn On 2/27/08 6:24 PM, "John Larson" <[EMAIL PROTECTED]> wrote: > No, it should set the field as null with only one value in the list. > To be clear, there should be two select

Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread John Larson
No, it should set the field as null with only one value in the list. To be clear, there should be two selections in the list; the item from the list array and ">select value<" or whatever you have as the noSelectionString. Of course nothing will happen if you don't have your submit button

Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread Dawn Lockhart
Didn't know about the noSelectionString either. So I added it and it is not returning null for me, it is returning the first item in the WOPopupButton. Could this be because right now I only have one item and once I add more then it will return null? __

Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread Susanne Schneider
Hi Archibald, don't you mean the "noSelectionString"? Just set this binding to a string like "- please select a value -" or anything similar. No further hassling necessary ;-) HTH Susanne -- Susanne Schneider Coordinator secuSuite Development iAS interActive Systems GmbH Dieffenbachstraße 33

Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread Archibal Singleton
On 27 Feb 2008, at 12:01, Mike Schrag wrote: So I'm curious to know how you guys deal with this "problem"? Not sure if I'm reading this correctly, but you should be able to just set noSelectionString = "Select a Person" (or whatever) ... When noSelectionString is submitted, it binds back to

Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread George Domurot
Try binding the noSelectionString attribute to "> Select One <" and see what happens. -G On Feb 27, 2008, at 6:53 AM, Archibal Singleton wrote: Hi everybody, I was wondering what would be the best way to solve the following recurring problem: You want to present a user with a list of op

Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread Mike Schrag
So I'm curious to know how you guys deal with this "problem"? Not sure if I'm reading this correctly, but you should be able to just set noSelectionString = "Select a Person" (or whatever) ... When noSelectionString is submitted, it binds back to you as a null value. ms

Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread David LeBer
On 27-Feb-08, at 9:53 AM, Archibal Singleton wrote: Hi everybody, I was wondering what would be the best way to solve the following recurring problem: You want to present a user with a list of options, using a WOPopUpButton. Typically those options are some kind of EO. By default, the

Re: Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread Archibal Singleton
Here are two screenshots to illustrate what I mean... <> <> On 27 Feb 2008, at 11:53, Archibal Singleton wrote: Hi everybody, I was wondering what would be the best way to solve the following recurring problem: You want to present a user with a list of options, using a WOPopUpButt

Best practice for dummy empty option in a WOPopupButton

2008-02-27 Thread Archibal Singleton
Hi everybody, I was wondering what would be the best way to solve the following recurring problem: You want to present a user with a list of options, using a WOPopUpButton. Typically those options are some kind of EO. By default, the first time the list is presented, the selected (ideal