This topic covers tips, tricks and known issues for making the jump between the two above sessions.
They added Ready to Fulfil Checkbox on Job Materials which cause existing jobs not to show up in fulfilment workbench.
There’s a company config flag that can be flipped (as default) but the existing data doesn’t get updated. You need to fix those via DMT or other method for existing jobs.
Easily overlooked in the Downloads Section. Make sure to apply this HotFix if going to any version 11.2.300.0 - 11.2.300.8. It includes Erp.Triggers.ShipDtl.dll which has to be replaced on any IIS Application Server. You know it’s serious when Epicor provides a one-off hot-fix.
During the Conversion Workbench there are tasks that uplift (convert) your BPMs. In 2023 Epicor now passes the row inside each sub-action, instead of using LINQ always.
// 2022.2
private void A009_SetFieldAction()
{
var query = ds.UD01.Where(row => !row.Unchanged());
foreach (var item in query)
{
item.Number10 = (System.Decimal)(Math.Ceiling(item.Number10));
}
}
// 2023.1
[Epicor.Customization.CustomCode]
private System.Decimal A009_SetFieldAction_Number10(Ice.Tablesets.UD01Row item)
{
return (System.Decimal)(Math.Ceiling(item.Number10));
}
I found that if you have a Set Field condition with your Column wrapped in a Method, like Math.Ceiling(dsUD01Row.Number10) it will not convert that sub-action, somehow it will use Ice.Bpm.Tablesets.UD01TempRow instead of Ice.Tablesets.UD01Row to me the UD01TempRow seems the logical choice, given that we are modifying temp-tables, but it wants UD01Row.
Reselect the Column you are setting, save the BPM and mark as Compatible.
Thank you.
And thank you.
