I've inherited a layout that has multiple portals. In the second portal, I'm trying to let the user jump to the portal record in the related table but when they get there, they cannot make any changes because the record is "being modified in a different window".

I thought I could add a 'commit' in the script that executes the jump to the related table, but once the commit step is executed, the portal becomes inactive and the 'Goto Related Record' step doesn't execute correctly.

So then I thought that I could capture the portal row number and just go back to that row after the commit is executed. But because the portal is no longer active, it's not working either.

Any suggestions?

Thanks,

I found that by naming the portal object, I was able to use the 'Go to Object' script step and that seems to work.

Thought I had it, but I don't. The problem is that when the script hits the 'commit' step, it resorts the portal based on the relationship's sort (reverse date). Therefore FM loses the pointer to the correct record.

Is there any way to store something that would identify the correct record in the portal and use that to find that same record in the portal after the commit takes place?

I believe this (and the link from there) should help.