globals in popovers do work, however the context of them is different for WebDirect. The best way to think about it is if you're running a scheduled server script, that's a similar context. This is why it can work on pro/go, but be entirely different for server/webdirect/CWP.
I threw a global into a popover and tested, screenshot attached.
you change the context? At the top of the script, do I use a Go to layout object step and then a go to record step?
I believe you would go to the record first, then the object after. Unless I saw a copy of your script and layout though I wouldn't really be able to speculate the best way.