Determining the filtered set of records

[brian rich]

A GTRR step using the portal relationship gives the unfiltered portal results - I want to be able to select the filtered set - is there a way of establishing the set of records that are being displayed so I can process these in isolation?

Thanks

Brian

[comment]

If I understand your question correctly, you need to place the button that runs GTTR inside the filtered portal.

[brian rich]

I'll explain what I am trying to do.

I have two copies of the same portal on the same layout. The records in the portal table have a date field that either has a value or it doesn't. The first portal has a filter set so that if there is no date in the field, the record is displayed: isempty(<date field>). The second portal has a filter set so if there is a date in the field, the record is displayed: not isempty(<date field>) I have a small button on the first portal's row that runs a script which enters the current date in the date field and then commits the record - this causes the record to disappear from the first portal and appear in the second. When I've manipulated the records into the appropriate portal, I need to do some further processing on both sets of records, so I need to know which records are in each set.

As far as I can see, I have to run a GTRR step using the portal relationship and then constrain the found set using the filter values. I was wondering whether there was a way of using the GTRR step with the filter settings included.

Thanks

Brian

[comment]

I was wondering whether there was a way of using the GTRR step with the filter settings included.

As I said, you must call the step while the filtered portal is active.