I'm trying to implement my first production version of a filtered portal and have fallen flat.

All I'm trying to do is display records that contain characters from a user-entered string. No matter what I do after entering the characters, I can't get the portal to refresh until I step away from the current parent record. Then it updates immediately.

I've modified Mr. Vodka's simple example to show the results I'm getting. Indeed, if I change my field to a value list selection, it updates just like his example did. (BTW, my match field has to be in a separate record, as shown ... but this shouldn't make a difference.)

Any guidance will be appreciated.

Portal_Filter_Blues.ZIP

All you were missing was committing the record. Also, the relationship to 'MyTest' table wasn't necessary.

That's a pretty cool trick; I haven't tried that one yet. I suspect it could be slow if the tables got large (or via WAN), but I don't know.

Portal_Filter_Blues_rev.zip

Thank you, sir.

It's the combination of Commit Records and Flush Cached Join Results that does the trick. I was giving too much credit to Flush doing the job. Hope this helps others. I haven't seen it mentioned anywhere else.