topic Re: Calling arcpy.da.Editor from geoprocessing service in webapp in Python Questions

Calling arcpy.da.Editor from geoprocessing service in webapp

_watcher_ — Fri, 21 May 2021 01:55:17 GMT

I’m a newbie so please excuse a dumb question; I’m just finding the documentation rather confusing.

Can I use arcpy.da.Editor in a geoprocessing service called by a web app? If I can, how do I determine what the workspace is?

This is the code I’m attempting to use:

edit = arcpy.da.Editor(arcpy.env.workspace)

edit.startEditing(False, False)

edit.startOperation()

// my code here

edit.stopOperation()

edit.stopEditing(True)

The full story is there’s an existing ArcMap addin with a toolbox module. I’m attempting to publish the toolbox as a set of geoprocessing services, which will be called from geoprocessing widgets in a new web app (created with web appbuilder). At the moment, calling any of the geoprocessing service is failing with the error “cannot open workspace”.

It seems logical that there might be some extra set up required before trying to get the workspace; this is a web app, not ArcMap (when used in ArcMap, the workspace comes from a settings file). But I’m not sure if it’s even possible to do what the code is trying to do. Because this is an existing (unfamiliar!) codebase, I’m also trying to minimise the changes and identify if the code needs to diverge in order to support the web app.

Re: Calling arcpy.da.Editor from geoprocessing service in webapp

DanPatterson — Fri, 21 May 2021 02:19:02 GMT

The workspace would be a geodatabase or a folder (for shapefies).

Editor—ArcGIS Pro | Documentation

Re: Calling arcpy.da.Editor from geoprocessing service in webapp

_watcher_ — Fri, 21 May 2021 02:52:28 GMT

Thanks Dan!

Something like this perhaps?

arcpy.env.workspace = r"//[servername]/connections/dbconnection.sde"

Re: Calling arcpy.da.Editor from geoprocessing service in webapp

BlakeTerhune — Fri, 21 May 2021 14:34:56 GMT

It would be arcpy.env.workspace = r"\\[servername]\connections\dbconnection.sde"

If you really are going to a database connected saved on a different server, you'll have to include a drive letter like arcpy.env.workspace = r"\\[servername]\c$\connections\dbconnection.sde"

Re: Calling arcpy.da.Editor from geoprocessing service in webapp

BlakeTerhune — Fri, 21 May 2021 17:00:25 GMT

I have to ask, why wouldn't you edit a feature service instead of trying to use Editor?

Re: Calling arcpy.da.Editor from geoprocessing service in webapp

_watcher_ — Sun, 23 May 2021 23:59:05 GMT

Thanks Blake. The connection files sit on a shared folder, so there should be no need for the drive letter, but did I try your both of your suggestions (without success)

Re: Calling arcpy.da.Editor from geoprocessing service in webapp

_watcher_ — Mon, 24 May 2021 00:51:38 GMT

There's an existing toolbox in use in ArcMap containing the functionality that is tested and works. All that's wanted is to provide an additional access point via web app.

Re: Calling arcpy.da.Editor from geoprocessing service in webapp

_watcher_ — Mon, 24 May 2021 01:00:56 GMT

Ok, so according to this question Why would a python script run fine from within ArcMap but not as a geoprocessing service? I need to do the following:

arcpy.env.workspace = os.path.dirname(r"//[servername]/connections/dbconnection.sde")

This call cuts off the dbconnection.sde part of the path. Not sure why this fixes the problem, but I'm now onto a different error in a different part of the code, so that's one step further than I was before.