Data query + User Interface Designer

I jumped in late to this conversation but the error message you are getting is the same message you get if you don't link the button to a function.
In the designer:
1) Click on the button
2) Select the actions from the properties
3) Select Function on left
4) paste in "BUTTON_OnClick" without the quotes

Of course if this is not the problem please ignore. Hope This Helps.

Robert

Thank you, robert. The function is linked to the button. When I click the button, it begins to step through the function. However, it bails out with the "Token" required message.

Are you aware of any sample code that I could try in order to obtain a "proof of concept" for accessing a piece of related data not currently on the form, and then displaying the output on the custom form?

If your willing to try, I've included a script I use in IC12.1 to populate some of the cost/qty information on the main form so they don't have to drill. For your test you could probably just convert what I have as text fields to alerts.

Let me know if this helped.

function FORM_OnAfterTransaction(data)

{
var vCompany = lawForm.getDataValue("ITL-COMPANY");
var vLocation = lawForm.getDataValue("ITL-LOCATION");
var vItem = lawForm.getDataValue("ITL-ITEM");
var strPDL = portalWnd.oUserProfile.getAttribute("productline");

//DME call
var s = "?PROD="+strPDL;
s += "&FILE=ITEMLOC";
s += "&INDEX=ITLSET1&KEY=" + vCompany + "=" + vLocation + "=" + vItem;
s += "&FIELD=LAST-REC-COST;LAST-ISS-COST;SOH-QTY;ALLOCATABLE";
s += "&MAX=1&OUT=XML";
//alert(s);
var sReturn = portalWnd.httpRequest(portalWnd.DMEPath + s);

if (!sReturn || sReturn.status)
{
var msg="Error calling DME ";

msg += (sReturn
? "(status code): " + sReturn.status
: "bad server response.");
alert(msg);
return true;
}

var vObjDMEXML = new portalWnd.DataStorage(sReturn);

var vRecord = vObjDMEXML.document.getElementsByTagName("RECORD");

if (vRecord.length == 0)
{
return true;
}

lawForm.setDataValueById("text47","");
lawForm.setDataValueById("text48","");
lawForm.setDataValueById("text49","");
lawForm.setDataValueById("text50","");

vCols = vRecord[0].getElementsByTagName("COL");

lawForm.setFormValue("text47",vCols[2].firstChild.data);
lawForm.setFormValue("text48",vCols[3].firstChild.data);
lawForm.setFormValue("text49",vCols[0].firstChild.data);
lawForm.setFormValue("text50",vCols[1].firstChild.data);

return true;
}

Robert, Thank you very much! I will give this a shot and let you know how I make out. Your help is really appreciated.

Robert, Data values were returned!!! This is a break through! Thank you so, so much for your time and attention.

Unbelievably, though, the same error message box still pops up before displaying the information. I don't know how to address this error message. Is there a way to suppress the message, given that the system actually does return results now?

I am thrilled to have finally "made contact" with other Lawson tables accessed from a custom form. It opens up a whole new world.

Again, your help, and that of David Williams, has been invaluable to me. Thank you both! And, thank you Lawson Guru.

Heidi

I beginning to believe this has nothing to do with the DME and more to do with the form. I would start over by deleting your current design studio form and regenerating a fresh copy. Validate it works before entering any scripting or buttons.

Did you try the script I provided on IC12 and that is were you got the error?

Robert, Yes, I used your script "right out of the box", with exception of calling it from a Button Click, as opposed to the "OnAfterTransaction".

I started with a fresh, new form, as I had not yet done any work on any of the IC12 forms. I added four text boxes that matched where you output the DME values.
Then, a new button was added, to retrieve the data.

Your script worked like a charm!

I am working in our testing environment, where there are multiple productlines. Could the errant message have something to do with that?

I guess it could be. Alert the product line and verify or for testing purposes hard code the product line to test.

While I don't have a full solution yet to share, it appears that the errant, unnecessary message may be caused by a LID run type "pgmdef" setting. Once the issue is fully resolved, I will post what it took to resolve.

Again, your help and time is appreciated!