Do you have any reason for adding 2nd criteria to relationship? You can add it to filter calculation.
and ( IsEmpty ( transactions::PROC ) or transactions::PROC = all_items_PROC::type )
hmm.. not sure that works. Yes the reason for 2nd criteria is I have a list of items, which includes procedures, which also includes "favorite" procedures.
I want to use a selector button to narrow down to favorites. and then still be able to use the cartesian search method with gSearch field and script trigger onmodify.
here is my current portal filter calc:
IsEmpty ( transactions::gSearch) or PatternCount (all_items_PROC::descr ; transactions::gSearch)
transactions:PROC is a "P" for every record linked to type P in items table.
Criterias in relationship is always defined as AND criteria, then if you use X with some other condition, in result X will be ignored.
So try changing the filter (with parrenthesis, for clear order of and/or).
(yours) and (I wrote)