Guys , I have a some question concerning for the behavior of SaveOptions field. I am aware on what’s the use of the field. One trick I tested is if I try to remove the field/item from an action in the view or run an agent to remove the field, the state of the document will not change. If you have a value for SaveOptions of zero before then remove it in background it will still behave as is that field is existing. My question is that how that field behave that even though you have already remove it, it’s property still retain?
Subject: SaveOptions Tricks
It not just as simple as removing it from backend… If You have defined the field in the form and it is computed - it will be added to the backend when opening the document.
SaveOptions field should not be edited or computed. It should be computed for display to avoid such problems.
hth