Is there a way to handle a server side error incurred from trying to set a field by a wf? I am trying to add a way to update the Posting Period field after approval automatically, and I thought to do with with a custom field that's set during draft stages as user knows when the final posting period should be for transaction. Use case causing errors though, is what if the transaction was left in Pending while AP was Locked. Upon approval it throws an error and mucks up the wf process. I thought to resolve this with a custom field check for Locked periods, but apparently NS doesn't recognize a Period as AP/AR Locked unless all subsidiaries are Locked so a saved search won't catch it.

There is a setting in accounting preferences that will move your period forward on all transactions when you lock AP or AR

I love that this is a specific enough problem that you had to make a niche solution for it

Haha yeah. We’ve seen so much of this problem over the years