Set Variable [$$TriggersOff ; value: True ]
Put rest of script here
Set Variable [$$TriggersOff ; value: "" ]
You might also set the globals before you open the popover. A regular button could perform a script that sets the globals, then uses go to object to open the popover by specifying the object name of the popover's panel. The actual popover button can be hidden via Hide Object When so that you can put the regular button in its place.
You are a brilliant person. It sounds like the regular button and hidden popover button is simplest route, I will try that now. Thank you!
You don't need to change layout by going to another table just to fill globals with values.
Just fill the globals with an ExecuteSQL based upon a TO of the "different table", using the Profile_ID in the WHERE part.
I am pretty new to the ExecuteSQL scripting. Do you recommend any links to tutorials on ExecuteSQL best practices or how to utilize it fully?
Beverly's pdf remains the most complete approach to this, IMHO.
Basically, if you are on table A and there's a Table B with records having an ID and you have no relationship from A to B but you have a TO for table B and you have the ID of a record in table B, you can get values of fields located in table B, in the record having the ID you've got. But you can accomplish much more via ExecuteSQL.