commit portal record before going to related ?

[Thomas An]

In a portal, each row has a button.

This button pops-up a larger window of that same portal row.

The problem is, if the user has started typing something in the portal, then runs out of space and so without committing the changes clicks the zoom button to get to a larger view of that record ...

... we have a conflict, because the record is being edited from two different windows.

If we use the commit function before calling the popup window then the "go to related record" step is lost.

Is there an elegant way to commit before going to a related record ? (right now I have to do some trickery with having both windows and then bringing the previous window in focus and committing it ... however, this causes flicker even with the freeze window command)

[Thomas An]

problem solved.

In the related table, created a new calculated field containing the record number for each record ... then...

...instead of using the "go to related record" script step, we query and store the related portal record number in a global script variable, commit the current layout, open a new window, go to the desired layout and navigate using the data in the stored script variable. (basically completely bypassing the use of the "go to related record" script step)

-

[Miriam]

If you script it, you could save the portal row number to a variable, commit the record, then got to portal row number then gtrr.