Epicor BPM: Update a UD Field, a PO Cost or a Table, and Update vs UpdateExt

How to update data from a BPM

1. 1If the record is the one being saved, set the field on the ttTable row in a Pre or Post-Processing directive instead of calling another update.
2. 2For a UD field, use the UD field helper on the row or the indexer with the column name, such as Character01.
3. 3For another record, call the right business object: GetByID, change the row, set RowMod to U, then Update or UpdateExt.
4. 4Prefer UpdateExt when you want to handle errors yourself, and check the returned error flag.
5. 5For bulk changes, loop over a query result and call the service for each, in small batches.
6. 6For a table with no service (such as a UD table), use Db, change the rows and call Db.Validate inside a transaction scope.
7. 7Test with a record locked by another user to see the behaviour.

Update vs UpdateExt, and updating a purchase order cost

bool errors;
this.CallService<Erp.Contracts.POSvc>(svc =>
{
    var ds = svc.GetByID(poNum);
    var line = ds.PODetail.FirstOrDefault(l => l.POLine == poLine);
    if (line != null)
    {
        line.RowMod = "U";
        line.DocUnitCost = newCost;
        svc.UpdateExt(ref ds, out errors);
    }
});

Common pitfalls

• !Calling Update on the same record you are already saving, causing recursion or record in process.
• !Writing cost or status columns with Db and skipping business rules.
• !Not setting RowMod to U, so the service ignores the change.
• !Using Update in a loop where one error should not stop the batch.
• !Relying on EventLog.WriteEntry in cloud tenants.