Report comment

Hey Rudi!
Glad it's working out well for you.

Unfortunately, script variables ($) have a scope that's limited to the script that created them;
Global variables ($$) are limited to the file that they were created in;
And global fields are limited to the session that they were created in.

My recommended solution is to take advantage of some of the optional parameters that can be passed to my 'PSOR - Ask Robot To Run This' script. It's not really well documented, but you'll notice in my 'Sample Report Script' that I have a couple of commented out function calls in the script parameter:

//& NameValuePair_Browse__cf ( _fieldName ; _value )
//& NameValuePair_Find__cf ( _fieldName ; _value )

Both commented out lines of code here are referencing custom functions which I have created.
They both take 2 parameters:
_fieldName => a fully qualified fieldname (I recommend using GetFieldName())
_value => the value that is to be set into specified field

Each of these custom functions can be called an arbitrary number of times (simply by concatenation ... as they don't return anything). When the robot machine receives them, they get handled differently based on whether the browse mode ones were used and/or the find mode ones were used.

The find mode ones will be used by the robot in find mode -- so that you can try to recreate the same found set for instance,
and the browse mode ones usually get used for setting some fields in browse mode (ie a global field).

What I might recommend, is that you use a browse mode one to set a global field equal to the account name of the person running the script from web direct, and then you in turn set that value into the account name field of your choice within your own script.

I know this is pretty wordy, but I hope this makes sense.

Best Regards;