I work around this by always coding custom filters for each grid I create.
It is great having the default capabilities that the search_widget
provides within the grid, but I feel that it is too complicated for our
typical users. For foreign key fields I will usually provide a SELECT
control that will allow them to select the one they want to search on
(providing the list isn't too long). If I want to do an auto-complete I'll
use Kenji's suggest_widget. Not nearly as flexible as the default
search_widget but must simpler for the user and also limits them to just
the filter controls they need.
-Jim
On Sunday, March 10, 2013 8:50:56 PM UTC-5, Cliff Kachinske wrote:
>
> I define a table so:
> db.define_table ('mytable', blah..., format='% (name) s')
>
> So as we know, grid will display the contents of the name field when
> mytable is used as a foreign table.
>
> But if you try to search on that field, the search only works if you
> submit record id integers as search parameters.
>
> Since human users don't generally know the record id or ids, this makes
> the search function less useful than it could be.
>
> Has anyone worked around this? If so, can you share your solution?
>
> Thanks, Cliff Kachinske
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
