Hi Guys,

Sorry if there is a simple answer to this one...

I have a portal which looks up table 'accom' where the user can edit fields and add a new row . Each row has a further info link which opens a new window and goes to a layout for 'accom'.

However when this new window opens I get an error saying this record is already being edited in another layout. So I know I have to commit the record before I can then go to related.

When I add this step in however it won't navigate to the selected record it will only got to the first record in 'accom'.

So I looked this online and the best option seems to be storing the portal row number in a variable and then committing records, loading layout and go to record from variable.

So I went to use Get(PortalRowNumber) to store as a variable and I get an error saying thats a invalid parameter of Get and I'm not sure why.

Any ideas?

Thanks in advance,

Dan

You don't want to store the portal row number. You want to store the primary key for the row record, go to the new window, and perform a scripted find for that key.

So I went to use Get(PortalRowNumber) to store as a variable and I get an error saying thats a invalid parameter of Get and I'm not sure why.

Because in version 11 the function has been renamed to Get ( ActivePortalRowNumber ).

the best option seems to be storing the portal row number in a variable and then committing records, loading layout and go to record from variable.

No, the best option is to store the portal row number in a variable (or a script parameter), commit records, go to related record (show related only), then go to the record number.

This, of course, assumes the portal doesn't have its own sort order, different from the relationship's sort order.

You're also assuming it's not a filtered portal. Seems like it ALWAYS works to get the primary key for the portal record and that would be the most reliable method.