How to add operation to MRP created job selectively based on criteria

[jtownsend (John Townsend)]

I don’t really see an alternative to your solution. This will require some custom coding to work, and jobs can be finicky to update, especially if you don’t allow changes on engineered jobs.

Good news, is that I’ve already done the hard part of figuring out the basics of job edits for you. This post is intended for use in a mass-edit function. The specific snippet will wipe a job’s MOM/BOM and re-pull latest rev (never actually used it since it was easier just to tell people to stop firming jobs months ahead of when we actually needed to start work), but you can clip that part out and add a method call for adding your op.

Using Epicor Custom Functions to Update PartOpr and JobOper

That doesn’t look like Function syntax. There’s also a few caveats with JobEntry specifically, at least if you don’t allow edits to engineered jobs. This is from a function I wrote that uplifts the revision on a job. This snippet first unengineers the job, then runs the update of the now-editable record. Note the lambda (=>) syntax vs the using statement more common in BPM’s, foreach (var job in jobs) { try { //Placing the txScope here instead of at the function itself …

For your use, you may not need to go down the mass edit route. You could trigger it based on changes to the demand link. Without the loop requirement, you could probably even use the widgets if you’re so inclined.