BPM server side code throws an exception I can't catch

Epicor ERP 10
1

I am migrating a Client UI customization to a Server side BPM. This customization adds a operation to a Quote using QuoteAsm BO. I am making what appear to be identical calls in the BPM and the UI customization (thru the Adapter though) but in the BPM it is throwing the following message

Cannot manually update the Production Labor Rate in QuoteOpr.
Cannot manually update the Production Burden Rate in QuoteOpr.
Cannot manually update the Setup Labor Rate in QuoteOpr.
Cannot manually update the Setup Burden Rate in QuoteOpr.

But not in the UI.

Here is the code segment from the BPM, OpCode is set earlie, _tsQuoteAsm is the Tableset and Opr is a newly added row to the Tableset.

  String RefreshMsg = "";
  try
  {
    Opr.OpCode = OpCode;
    Opr.OpDesc = ThisOpMaster["OpDesc"].ToString();
    if (Opr.RowMod != "A") Opr.RowMod = "U";
    _boQuoteAsm.Update(ref _tsQuoteAsm);
  }
  catch (System.Exception ex)
  { 
      DebugMsg("Error updating Oper OpCode - " + ex.Message);
  }

The catch NEVER catches the error, instead the BPM exits abruptly.

The code in the UI looks like this

	Opr.OpCode = OpCode;
	Opr.OpDesc = ThisOpMaster[0]["OpDesc"].ToString();
	Opr.RowMod = "U";
	_quoteAsmAdapter.Update();

Which works fine, even thou it is changing the RowMod to U, which failed in the BPM (needed to leave it as A so the zero SysRowID is ok)

Any thoughts would be appreciated. This is driving me crazy.

Also this server is in the cloud running 10.2.500.

Mercer

2

If you can’t catch it it’s already being caught and handled so maybe event viewer on the server? Hopefully they don’t have an empty catch somewhere (though it does happen…)

3

It is clear that the Adapter is catching it somehow cause it doesn’t happen with the Adapter.

4

¯_(ツ)_/¯ jam it through the Db object vs the BO? Not ideal but probably not fields that have dependencies.

5

Obviously this isn’t all of your code, but are you doing this inside a loop?

6

This is called as part of an add operation function. Basically add a new Operation then set its OpCode followed by optionally setting the OpStd.

7

I thought of that and that might be the way around this, but I’d prefer to go thru the BO. Its frustrating that clearly the adapter has some way of preventing the the exception or catching it so it doesn’t throw the message and abort the update.

8

What screen are you in and what is the full code for this method?

9

This is part of a customization to Quote Entry - sort of a mini-configurator. It works well as a UI customization but it is way too slow. So I am moving it to the server side using a Quote.Update BPM. The code has been migrated and adjusted to the BPM requirements and it is working really well except for this situation.

10

Got it. So this is a BPM, but the code snippet you sent does not appear to be the full code. This means we can’t help you understand what is causing the error (or suggest simpler code).

11

I created a custom app that couldn’t be simpler. Click button, and this runs:

try
{	
	Erp.Adapters.JobEntryAdapter JEAdapter = new Erp.Adapters.JobEntryAdapter(oTrans);
	Erp.BO.JobEntryDataSet JobEntryDS = new Erp.BO.JobEntryDataSet();
	JEAdapter.BOConnect();
	bool JEresult = JEAdapter.GetByID(vJobNum);
			
	if (JEresult)
	{
		JobEntryDS = JEAdapter.JobEntryData;
		JEAdapter.GetDetails(vJobNum,0,"Method",0,0,"",0,vPartNum,vRevisionNum,"",true,false,false,false);
		JEAdapter.Update();
	}
}
catch (Exception ex)
{
	vTotErrorCount +=1;
	string myPath = "Sumthin";
	string ErrorFile = myPath + "Errors.CSV";
	
	using (StreamWriter sw = File.AppendText(ErrorFile))
	{	
		string WriteError = string.Format("\"" + vJobNum + "\"" + "," + "\"" + ex.ToString() + "\"");
		sw.WriteLine(WriteError);
	}
}

When I purposefully run it to get an error, nothing writes. When I swap in a custom MessageBox, nothing displays… What’s even more perplexing is this Try/Catch works perfectly fine in 10.2.4, but in 2023.1.6 it appears to be “uncatchable”. The error always displays, waiting for an OK click:
image

Which is unacceptable to users as this thing can cycle hundreds to thousands of records… Why would a BLException be uncatchable? I tried catch(Ice.BLException ex) but that did the same as code above. What-a-head-scratcher… Hoping one of you have successfully caught a BLException from the JobAdapter.

Thank you!