Methods BPM - Copy Operation Comment when changing Resource Group - Not Validating

Sorry, BPM aren’t my area of expertise and I’m stuck.

Erp.BO.EngWorkBench.ChangECOOPROpCode / Pre-Processing / Copy Operation Comment
foreach ( var ttECOOpr in ds.ECOOpr.Where( x => x.Updated() ) )
{
callContextBpmData.Character01 = ds.ECOOpr.CommentText;
message(“Comment:” + callContextBpmData.Character01);
}

Erp.BO.EngWorkBench.ChangECOOPROpCode / Post-Processing / Copy Operation Comment to New Resource

foreach ( var ttECOOpr in ds.ECOOpr.Where( x => x.Updated() ) )
{
ds.ECOOpr.CommentText = callContextBpmData.Character01;
message(“Patrick Restore Comment:” + callContextBpmData.Character01);
}

@Patrick These compile, but I can’t run them. it is a couple of different ways to hopefully get the info. I think message was ABL to write to the server log. That is like the Ice.Diagnostic which you see in the serverlog and event viewer. The PublishInfoMessage will do a popup.

foreach ( var ttECOOprRow in ttECOOpr.Where( x => x.Updated() ) )
{
callContextBpmData.Character01 = ttECOOprRow.CommentText;
//message(“Comment:” + callContextBpmData.Character01);

}

foreach ( var ttECOOpr in ds.ECOOpr.Where( x => x.Updated() ) )
{
ds.ECOOpr[0].CommentText = callContextBpmData.Character01;
//message(“Patrick Restore Comment:” + callContextBpmData.Character01);
}
	string InfoMsg = string.Empty;
	InfoMsg = “Patrick Restore Comment:” + callContextBpmData.Character01;
	this.PublishInfoMessage(InfoMsg, Ice.Common.BusinessObjectMessageType.Information, Ice.Bpm.InfoMessageDisplayMode.Individual, "FirstVar","SecondVar");

Ice.Diagnostics.Log.WriteEntry(“Patrick Restore Comment:” + callContextBpmData.Character01);

I’m seeing the same, it compiles but error’s out on the POST update.

What is the error in the event log? Add the Write Diag lines and check in the event viewer to see if the call context is getting set.

foreach ( var ttECOOpr in ds.ECOOpr.Where( x => x.Updated() ) )
{
ttECOOpr.CommentText = callContextBpmData.Character01;
}

This worked on the Post-Processing
Thanks for pointing me in the right direction.