ReportQty fails when CallContextBPMData is populated

OK. This is weird: I’ve customized the ReportQty form in MES by adding a text field and binding it to CallContextBpmData.Character06. If I do not put anything in this field, the report qty works as per normal, but if I put some text in the field it fails. I’ve put a trace log on the form and it is completely blank… There is nothing in the customization of the form itself that refers to that form field in any way. If I unbind the field, it runs as expected. Is there something I should check or am I just using the CallContextBpmData in the wrong way?

Well I’ve managed to make a work around. I just leave the field unbound, and then set up a “Leave” event tigger:
private void txtComment_Leave(object sender, System.EventArgs args)
{
// ** Place Event Handling Code Here **
EpiTextBox txtComment = (EpiTextBox)csm.GetNativeControlReference(“78717496-9b04-42fb-b85b-8672a7347973”);
EpiDataView edvComment = (EpiDataView)(oTrans.EpiDataViews[“CallContextBpmData”]);
edvComment.dataView[edvComment.Row][“Character06”] = txtComment.Text;
}

That seems to have done the trick …

Most forms do not have a row in the CallCOntextBpmData. I have to check if there is a row and if not, create it. This is why it is working now for you.

2 Likes