G
G. Tarazi
Hi
This is a very important issue, the developer must be able to restrict the
undo, redo operations in InfoPath, I have this problem and it's because of
the undo option.
Have a look at this scenario:
One InfoPath form
10 pages long
1000+ controls in multiple repeatable sections
Internal complex mechanisms
Supported by 10+ web services during runtime.
Saves to a web service
The web service saves to 110+ database tables
The entire form is reloaded after every save from the database using a
second DOM, and the replace node mechanism.
Now the end user will call the undo function after loading it, and will save
again, that is breaking the entire db logic that we have.
I know, we can write couple of thousands of lines of additional code to
handle undo, or Microsoft can simply restrict it in the next InfoPath
I just need to tell InfoPath (disable undo) or clear the previous undo,
where the user can do undo on the changes he makes after the undo point, not
before it.
Thanks
This is a very important issue, the developer must be able to restrict the
undo, redo operations in InfoPath, I have this problem and it's because of
the undo option.
Have a look at this scenario:
One InfoPath form
10 pages long
1000+ controls in multiple repeatable sections
Internal complex mechanisms
Supported by 10+ web services during runtime.
Saves to a web service
The web service saves to 110+ database tables
The entire form is reloaded after every save from the database using a
second DOM, and the replace node mechanism.
Now the end user will call the undo function after loading it, and will save
again, that is breaking the entire db logic that we have.
I know, we can write couple of thousands of lines of additional code to
handle undo, or Microsoft can simply restrict it in the next InfoPath
I just need to tell InfoPath (disable undo) or clear the previous undo,
where the user can do undo on the changes he makes after the undo point, not
before it.
Thanks