Script Trigger behaving differently than a script on a button.

[rain_girl]

I have a script that tells a portal row to set a global field and activate another portal (portal #2). Then proceed to the portal #2 for data entry.

If you attach the script to a button on the first portal, works great. I can use a view as form and then a go to field script step to jump the user to the next portal.

However, if you attach the script to a trigger on a field in portal #1, it will not jump to the second portal. It always jumps down to the next creation record in the first portal.

This is confusing to users because that new row in the first portal sets the global to nothing and then they get an error message in the second portal.

Is there something I am missing as far as behavior differences?

[mr_vodka]

Can you post a file?

A wild guess here but I think that you should capture either the object name or field to know which portal to go to.