Call MyScript()

Sub MyScript()

' script code… now possibly including an "exit sub" command

End sub

Thanks this did work to fix the error I was seeing. My script still isn't working but I did get past that first hurdle with your help. Do you know of any resources I can use for doing UI scripting? I have really only done BOI scripting which triggers from a Sage event so I am not as familiar with how to write without the oBusObj. That is the error I am now getting when trying to run the VI script and when I try to run this script from a button it just doesn't do anything. I assume that I have not written the field value retrieval correctly which is why the script isn't working. Any direction you can give me would be much appreciated!

For a button script, to access business objects on an Advanced / Premium system, you need to run the script from the server (option where you configure the button script).

What are you trying to accomplish?

Ultimately, I would like to have this script run after using a VI import into Sales Order History Detail to add tracking numbers to a UDF. There is a current tracking string field and an all tracking string field as each line item may have more than one tracking number. The all track will accumulate all the current tracking numbers after import by looking in the string, if current tracking exists already in the all tracking field it exits the script, if it doesn't it adds it on to the end of the script. I got the script to work testing in Sales Order Entry but it needs to be run in History as sometimes the orders will already be invoiced when additional tracking numbers come in. I have tried running it every way I can think of at this point and may be a little turned around from focusing on it so long. I have done several BOI scripts but have not ventured into any UI scripts yet so this is new territory for me. Thank you!

I think maybe all the issues are related to trying to write into a history file vs an open file. I worked with the person looking for the script and she agreed to have it write into the open purchase order file instead and the script works after running VI now, even without the extra call sub function. Thanks so much for showing me that bit of scripting though. I learn so much from this community!

I think maybe all the issues are related to trying to write into a history file vs an open file. I worked with the person looking for the script and she agreed to have it write into the open purchase order file instead and the script works after running VI now, even without the extra call sub function. Thanks so much for showing me that bit of scripting though. I learn so much from this community!