I suspect this has to do with the fact that your button is in a subsummary rather than on a portal row.
In a sub-sum, it takes you to the related records, but it doesn't know which one.
In a portal row, it takes you to the portal record in which the button was clicked.
If you have a context which allows you to capture the record info of the specific target record as the button is clicked on that record (perform script with script parameter supplied via the button), you can script the navigation to the correct record, with or without using the GTRR step, to be sure of landing in the right record.
Relying on a button which performs only the GTRR function requires that the button be in the exact context for the correct related record, usually a portal row.
Thanks, I suspected this was the case. Not being highly savvy with
scripting, all I want to do is say the Pk in this record/layout is the same
Pk in the record/layout that I want to navigate to. Any suggestions for
On Sat, Aug 2, 2014 at 7:13 PM, Stephen Huston <firstname.lastname@example.org
all I want to do is say the Pk in this record/layout is the same
Pk in the record/layout that I want to navigate to.
Put the button into the body part – that's where the individual records in your summary “are”. You could also capture an ID and perform a find in another layout – but if you are able to capture a specific key, then a GTRR should also work.
If that doesn't work, please post a file and/or some other enlightening material re the exact context where this action is supposed to take place – your description wasn't terribly clear.
You could also simply script getting to the record you want, something along the lines of:
- Set Variable (set to the PK of the relted record you are capturing it from)
- Go to Layout (where you want to view the related record)
- Enter Find Mode
- Set Field (PK to the value of your variable
- Perform Find (not saved)
That should land you where you want to be. Obviously, needs some fine tuning based on your specific file and data structure.