infor eam - Error in processing entity WorkOrder unable to create entity object -
Text after "div class =" itemprop = "text">
The following error is being sent to GetAssetEquipmentOp:
"Unable to create error WorkOrder in the processing unit Unit Item "
Here the code is now:
public stringType getAssetDescription (string toolcode) {try {// Setup service objects MP0302_GetAssetEquipment_001.GetAssetEquipmentService getservice = New MP0302_GetAssetEquipment_001.GetAssetEquipmentService (); MP0302_GetAssetEquipment_001.MP0302_GetAssetEquipment_001 getrequest = new MP0302_GetAssetEquipment_001.MP0302_GetAssetEquipment_001 (); MP0302_GetAssetEquipment_001.MP0302_GetAssetEquipment_001_Result getresult = New MP0302_GetAssetEquipment_001.MP0302_GetAssetEquipment_001_Result (); // Setup Object Type the string desc = new stringType (); // Setup service parameter getrequest.ASSETID = new MP0302_GetAssetEquipment_001.EQUIPMENTID_Type (); Getrequest.ASSETID.EQUIPMENTCODE = equipmentcode; Getrequest.ASSETID.ORGANIZATIONID = New MP0302_GetAssetEquipment_001.ORGANIZATIONID_Type (); Getrequest.ASSETID.ORGANIZATIONID.ORGANIZATIONCODE = _orgCodeBody; // Setup Datastream Object Datastream.EWS.Session sex = new Datastream.EWS.Session (_userid, _passwd, _orgCodeHead, _url, _tenant, false); // Ready service request sess.PrepareServiceRequest (haservice); // Call the web service and get results getreshult = getservice.GetAssetEquipmentOp (getrequest); // Remove Description desc.stringValue = getresult.ResultData.AssetEquipment.ASSETID.DESCRIPTION; Desc.errorNum = 0; // Close / Settle sess.CompleteServiceRequest (clever); Sess.Dispose (); // Return value return details; } Hold (exception before) {stringType errorStringType = new stringType (); ErrorStringType.errorNum = 1; ErrorStringType.errorDesc = ex.Message; Return error string type; }}
I have checked the following:
- The user group has interface permissions including BECONN - the user selector has selected "option" - the user has Any help would be appreciated.
The problem is resolved! The problem was that the task order number was not present. This is a very deceptive error, but once the existing work order was tested, it did not get any problem with the order of the order.
Comments
Post a Comment