Re: force D2W query pages to use "contains" operator
Re: force D2W query pages to use "contains" operator
- Subject: Re: force D2W query pages to use "contains" operator
- From: Tim Worman <email@hidden>
- Date: Wed, 25 Apr 2012 12:26:56 -0700
Ramsey:
Thanks for that. I was actually referring to an entity query page, but even so, this is really useful. Thanks much!
Definitely the issue is exactly those types of strings - I can't stand having my users wade through the pop-ups.
Tim
On Apr 25, 2012, at 8:47 AM, Ramsey Gurley <email@hidden> wrote:
> You're talking about the query all page? And that double WOPopup thing? There's no control over what operator is selected in that component. You can only set what operators appear using the relationalQualifierOperators key. The attribute is selected using D2WUtils.smartDefaultKeyForEntity. That method is undocumented and uses magic strings :-P It favors attributes like "name", "title", "description".
>
> On Apr 25, 2012, at 12:07 AM, Tim Worman wrote:
>
>> D2W experts:
>>
>> Is there a RHS key/value pair that will control what the default search operator is for an attribute on a query page? On an entity "search all" page, I have attributes where I don't want my users to have to select the pop-up button in order to switch to the "contains" option.
>>
>> Thanks much,
>>
>> Tim Worman
>> UCLA GSE&IS
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden