BTW Your changes would only get returned to the client - requiring them to save it. If you want to make sure it is saved, set the row state to updated then call the Part.Update method
Based on your screenshot, it looks like you’re trying to set fields in a Post-Processing directive. While it can vary, as a general rule, field updates need to happen in a Pre-Processing directive.
Post-Processing directives generally take place after method changes have been made to the database, so it is usually “too late” to use a set field in a post-processing and have it just work out of the box.
If there is a specific reason that you need the update to happen in the post-processing side, you’ll likely need to call some additional BO methods to commit the save to the DB. If there isn’t a specific reason that you’re using post-processing, you might try to move your logic to the pre-processing directive and see if it works.
Did you also do a Part.Update after marking the row as updated? A Pre-Processing Method Directive as @jepp suggested isn’t possible for DupicatePart because the new part hasn’t been created yet.
You need your BPM to modify fields then Update to save your changes while in Post-Processing
Thanks for the help, but I can’t seem to get this to work. I have tried setting the RowMod field in both a pre & post-processing workflow and I cannot see this in the trace (I am using Developer Tools in Chrome to trace).
Something else to try as a troubleshooting step… throw in a Show 0Message box, and in that box have the message give you the value of the PartPlant.MinOrderQty field. If it shows nothing (a blank value), then the PartPlant record doesn’t exist yet (so it isn’t possible to update it).