We could use the upper central part of the browse
window to add an Description: input field and a
"Search" button. This would do a LIKE search and show
only the relevant rows.
Ok: I am inserting in table A, and a field is linked to
table B. I open the "browse foreign values" window for table
B, which has thousands of rows. Those rows are sorted by
keyname on one side, and by description on the other side,
with a page selector. If we want to rely on opening another
browser window on table B, do the search, then copy and
paste the result, fine. But it seems to me that a little
search mechanism in the browse foreign value could help here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=192186
What's wrong with search page that we should duplicate it's
functionality?
Logged In: YES
user_id=192186
No reply Marc? :-)
Logged In: YES
user_id=210714
Hmmm, almost one year before I reply :)
Ok: I am inserting in table A, and a field is linked to
table B. I open the "browse foreign values" window for table
B, which has thousands of rows. Those rows are sorted by
keyname on one side, and by description on the other side,
with a page selector. If we want to rely on opening another
browser window on table B, do the search, then copy and
paste the result, fine. But it seems to me that a little
search mechanism in the browse foreign value could help here.
Logged In: YES
user_id=192186
Now I see, but you didn't write anything about foreign keys
in original report. I thought it's about normal browse tab...
Logged In: YES
user_id=192186
Implemented in cvs.
Logged In: YES
user_id=210714
Works very well, thanks.
Was it intentional to remove the page selector?
Logged In: YES
user_id=192186
It was not intentional, it should be removed only if limited
query returns less results. I will fix it.
Logged In: YES
user_id=192186
Fixed.