Searching to narrow portal results

[Proprius]

Hi,

Sorry if this has been covered before, but I'm currently stuck on this one issue. I have a portal displaying a list of cases, and if the user clicks on one of them it displays details of that case in the other half of the screen. What I'd like to do is allow the user to preform a search using any of the fields in the "details" half, and then display the found results in the portal. All of the cases are in the portal, so the search would just narrow them down. I tried scripting my way through it but I'm getting bogged down. Is what I'm describing possible?

Thanks for the help!

[bcooney]

Portals display records as defined in the relationship from the parent TO to the portal's (child) TO.

I would suggest a find screen for cases, and a list view of cases (rather than a portal).

But, if you like the portal interface, then you need a filtered portal, just add more criteria to the portal's relationship. Too many filters however can be cumbersome and the find screen/list view approach is the way to go.

[Proprius]

Thanks for the input. I'd like to stick with the portal setup, but I need help with the filtering criteria and my relationship. I've done this before but only with one field. In this case I have a lot of different fields that I want the user to be able to sort by. Is there a way to do this without making a separate relationship for each field?

Thanks, and sorry if that wasn't clear.

[bcooney]

You are mixing up the terms sort and find. Assuming you meant find (filter the portal by) then you need to edit the relationship from the parent table to the child table(portal's TO) so that includes all the fields by which you mean to filter.

Usually, to give the user a choice of filters, each filter is a global field with a value list assigned respective to the selection choice required.

[Josh Ormond]

Proprius,

Depending how comfortable you are with scripts, you could fake the portal filter, but still harness the power of the native find. The attached file searches multiple field, grabs the id's (from a separate layout and posts them in a global field that gives you the basis for the relationship filter.

Only drawback, it utilizes the clipboard (Never been a problem for me, but some dislike the very thought of it) . I tested it on Windows...with a database of 30,000 records. It is capable of returning a find set of 14,000 in a matter of seconds. The smaller the find set, the faster the it works.

Post back if you have questions about how to implement. :beertime:

Faux_Portal_Filter.zip