Hi Michelle,

I think the problem is that because this button thinks that the business object it is dealing with is the header object, however, you may not want to use SetValue() in this case anyway since your field is in the grid.  You can use InvokeChange() which emulates the user actually typing in the value.  This is preferred so that normal grid actions take place such as advancing to the next cell etc.  You probably want to change the script slightly to the following

retVal = 0
LookupCode = "CI_ItemCommon"
ItemCode = ""
retLookup = oUIObj.InvokeLookup(LookupCode, ItemCode)

If retVal <> 0 and ItemCode <> "" then

retVal = oUIObj.InvokeChange("UDF_MiscItem$", itemCode, "GD_LINES")

End If

Hope this helps.

Elliott

Hi Michelle,

I think the problem is that because this button thinks that the business object it is dealing with is the header object, however, you may not want to use SetValue() in this case anyway since your field is in the grid.  You can use InvokeChange() which emulates the user actually typing in the value.  This is preferred so that normal grid actions take place such as advancing to the next cell etc.  You probably want to change the script slightly to the following

retVal = 0
LookupCode = "CI_ItemCommon"
ItemCode = ""
retLookup = oUIObj.InvokeLookup(LookupCode, ItemCode)

If retVal <> 0 and ItemCode <> "" then

retVal = oUIObj.InvokeChange("UDF_MiscItem$", itemCode, "GD_LINES")

End If

Hope this helps.

Elliott

This was very helpful.  Worked for my UDT as well.

neatstripe I duplicated this code for a version 2016 UDT, but while the lookup dialog comes up with rows from the UDT, it does not filter with the <StartValue> (3rd InvokeLookup parameter). Did you have success with the <StartValue> parameter?

I wish I could help, but I wasn't using that parameter at the time, the best I can remember (which is not very well!).  Also, I'm in 2019 now, or I would test it.

Paul