go to related record will do that. There are a couple ways of doing what you want
1. In your script, right after go to related record, you can do Show All Records, Omit Record, Show Omitted Only
2. Create a global field in your parent table, create a new table occurrence of your child table and relate it to your parent table with global field = child primary key, then in your script above the go to related record add a Set Field step and set your global field to the primary key of the child record using the portal's table occurrence, then change your Go To Related Record script step to use the new table occurrence
#1 is the quickest and easiest to implement, but will cause any On Record Load script triggers on your child layout to fire needlessly, so if you have those then don't use this
#2 is the best from an execution stand-point but it requires you to add a field and a table occurrence which is slightly more difficult for you to have to maintain
Amazing, thanks so much for your help. That one seemed to be a real stumbling block for me.
The #1 one method, can, in rare cases, fail to isolate a single record if there are multiple users interacting with your database at the same time. If one user creates a new record at just the wrong fraction of a second in time, the Show Omitted Only step can bring back both the intended record and also the newly created record.
This can be avoided if you use the records primary key (unique identifier) in a find to find just that one record instead of using Show All, Omit, Show Omitted...
Thanks again Phil :)