Ugh, the copy button. I had one job where the copy button would always copy a certain field and break this one workflow we had. So I disabled it. Then I had a bunch of users come ask for the copy button back and I told them about this issue and that they need to be careful about it and go check that field before saving or it would break the workflow, and I re-enabled it for them. And then they proceeded to not check that field and break the workflow again. So I took the button away again. And they all came and asked for the button back, and I told them that if they sent an email copying me and my boss (the CIO) saying they were the reason the workflow broke earlier after I had warned them about it, they could have the copy button back. Suddenly no one seemed to need the copy button that badly anymore. 😆

LOL 😅

Same deal here. Had the copy button destroy numerous workflows. I inherited the mess from someone else and I took away the copy button (which wasnt supposed to be used) and did not tell them. The guy causing the problems revealed himself after a couple of weeks and I dared him to tell the CFO. He didnt and the copy button is still not available to those forms for that client 7 years later.

I just disabled it, let's see what happens.

Careful - memorized transactions can have the same problem

Will keep that in mind, thanks.