Nevermind! I changed the script to InvokeChange() instead of AddLine and it works fine now!

HI nronchetti,

Just curious -  is there documentation available for this particular function (InvokeLookup)?  I have pretty old scripting documentation that was provided after taking the BOI class years ago, but it doesn't include this method.  This would come in very handy, but I'm a little unclear on how you determine the proper 'lookupcode' when using the method.  Thanks!

Hi Justin K ,

The InvokeLookup() function was introduced in the Sage 100 ERP 2015 release.  Here is the basic syntax of the function and how to determine the proper 'lookup code'.  Maybe nronchetti has an alternate way to find the lookup that works better. :)

InvokeLookup(lookupCode, value, [startValue])

lookupCode - A valid Sage 100 ERP lookup code

data       - the value the user selected

startValue – {optional} if a lookup requires a start value, such as the Customer Contact lookup, optionally include this value.

example:

retVal = oUIObj.InvokeLookup(“CI_ItemAll”, item)

Finding the Lookup Code you want

• Turn on debugging (same procedure to use oScript.DebugPrint() )
• Go to location in Sage 100 ERP and start the lookup you want
• Right-Click on title bar – Select Debugging Environment..Watch values window
• From the Edit Menu on the Watch Window select Add new Watch
• Type in the variable control$ and click Add
• You should see the lookup name in the watch window.

Hope that helps.

Elliott

Great, thanks Elliot.  Very helpful.  Just curious - can this be used only with the oUIOBj in Sage, or can it be used with BOI in an external script/application?

Also, A little off topic, but with regards to turning on debugging in a Sage 100 Advanced instance, just wondering:

1.  Should the debugging flag in SOTA.INI be set in the server directory, the workstation directory, or both?

2.  Have you ever had a problem where even after setting Debug=1 in SOTA.INI, you don't get the 'Debug' menu option in any of the Sage tasks?  I have had this issue in more than one client environment, and haven't been able to figure out the cause.

That's what I used for finding the lookup too. Elliot's way is the best way. If you are using advanced you may want to make sure you are editing the right SOTA.ini file. Remember there is one on the workstation and one on the server.

A little correction to this thread.  Earlier I had stated that InvokeLookup() was introduced in Sage 100 ERP 2015 and this is incorrect.  Should be Sage 100 ERP 2013, my apologies.  We currently, in development on the 2015 release so it was probably in my brain when I answered.