Running “geoprocessing service” disallows saving edits,
I couldn’t figure out why a running “geoprocessing service” disallows saving edits. How come we need to stop the “geoprocessing service” to edit and save. And what if the edits are made via the web application?
How editing can still be performed while “geoprocessing service” is running?
If a running “geoprocessing service” result in disallowing saving edits then how come such environment can be suitable for an integrated piece of work considering the fact that an online web mapping application is in place? Stopping “service” will be bothering users\clients who are accessing the online application!
In return, why “map service” doesn’t cause this sort of lock while “geoprocessing service” does?
A good question about locks in general. It would be best to take this issue up with tech support, they would probably have a specific answer in your situation.
I would appreciate if ESRI experts can provide some comments on this.
It appears that this is not a rule. Publishing the “extract data task” tool as “geoprocessing service” doesn’t disallow saving edits. This is very confusing.
Then when “geoprocessing service” does disallow saving edits and when it doesn’t?