The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
SLX Web client lookups - contains..
Posted: 17 Nov 06 10:46 AM
|
fiogf49gjkf0d In the lan client, when you do a lookup you get the options of begins with, contains, accounts you bring to a desert island.. er, ok the first two and others. In the web client you any choice you want as long as it is 'Begins with'. I would like an account lookup that has the choice of 'Contains'.
Has anyone done this? Is it possible in web? Thanks |
|
|
|
Re: SLX Web client lookups - contains..
Posted: 17 Nov 06 11:01 AM
|
fiogf49gjkf0d I think that query returns the records based on the various condition sets defined in it.
So make a combo and depending on what is selected in that combo, you have to get to a different Condition Set(thru JS if i remember correctly)with Tab, Page Buttons and Record Captions checkboxes checked.
So can you try making a New Set with Account.Account 'contains' :text ..?
|
|
|
|
Re: SLX Web client lookups - contains..
Posted: 17 Nov 06 11:51 AM
|
fiogf49gjkf0d On a basic level you can't do contains searches for lookups in the web client.
What you can do is use the same query as starting with except send in a % value at the end.
i.e desert%
You will need to put HTMLEncoding on the percent so it will become
desert%25
The only down side to this approach is the next previous buttons won't work as they can't handle the % value in the query.
Hope this helps
--
Duncan |
|
|
|
Re: SLX Web client lookups - contains..
Posted: 21 Nov 06 2:06 AM
|
fiogf49gjkf0d Yes I also used the append % (URLEncoded) to the beginning of the lookup value. To get the next page buttons working just URL encode these also. I think Duncans example appears to put the percentage sign at the end, but it is needed at the beginning, as by default it already looks up the value 'Starting with'....
Thanks
Nick |
|
|
|
Re: SLX Web client lookups - contains..
Posted: 21 Nov 06 9:50 AM
|
fiogf49gjkf0d Actually I just changed the condition of the last name in the lookup config to contains as oppsed to start with. Seems to work fine. |
|
|
| |
|