This is not a bug and is not a change in behavior.
Further: it is easy to attach the primary key of the child record as a script parameter to the script associated with the GTRR operation.
No workarounds or updates are required. Just accurate and specific scripting for the particular intent of your script.
( see attatched example )
GTRR_test.fmp12.zip 69.5 K
I'm confused by this:
"One of my favorite applications is the use of GTRR in another table to isolate a found set or single record. The later clearly an option in the GTRR window. That simple later step [GTRR, single record] no longer seems to function under OS10.9.x."
If you're referring to this option:
"Match current record only" versus "Match all records in current found set" refers to the parent table, not the related table. In other words, GTRR does not - and never has - allowed you to choose one particular related record out of the related set. It only allows you to choose whether you grab the related records from the current parent record, or from all parent records in the current found set.
I also do not understand this:
"I would like to continue to use the portal remedy as it allows one to find what is there, rather than what might bethere."
By definition, if you GTRR from a portal, then the records are there. I don't understand how GTRR would show you anything else.
If you mean something different, please clarify.