Best Practice - Update Entire Tableset?

I have a best practice question for all of you experts out there.

I am working on a function for Job Entry where I am taking a value and updating every single operation in the job. Is it best to change one op at a time and update? Or is it ok to change every op in the job and then run update?

I’m by no means an expert, but many of the BO’s don’t accept multiple dirty rows. They are designed to work in the UI where changing rows triggers a save, so there wouldn’t be more than one. If it allows it, go for it, but I don’t think (I could be wrong though) the JOB BO allows it.

Interesting. I was not aware of that, thanks @Banderson .

I’m with @Banderson . If it will take multiple records, by all means do it. Much more efficient.

It’s not always obvious which ones will though, so testing is usually in order.