Latest Contributions by FredSpataro

Hi All, Sort of new to Survey123 so I might be missing something simple or doing something beyond the capabilities...Here's what I've got: Created a polygon feature class and table (the survey columns) in ArcCatalog along with a Simple, 1-Many relationship class between the feature (polygon 1) and table (many) using the GlobalId as the linking column.  This setup is then published to our online org account as a host feature layer.  I don't have any issues editing data in either the file geodatabase with ArcMap locally or the hosted feature layer via JavaScript API or map viewer.   Created a Survey123 with Connect (3.4.29b) using the feature service as the template.  Used xls to modify the columns, submission url and form id to the correct values.  Saved and loaded the xls. Published the survey.  Everything seems fine there.  When I run the survey from the web site form (not the device app - haven't tried that yet), all good until the submit.  Submit fails with error: - Operation rolled back. Operation rolled back. Incorrect geometry type. Which seems odd since I shouldn't be submitting any geometry to the table.   Watching the network tab in chrome shows the applyedits operation to the hosted feature layer.  Sure enough, it's adding a feature to the polygon layer with an (0,0) point.  The feature json to the table is correct.  I can copy and paste it to the REST pages and get a successful insert.  So I'm not sure why the survey is trying to submit a record to the polygon layer.  I don't have geopoint column in the XLS but it does have one listed in the "schema" tab of the Connect app.  I can't find a way to delete it there.   Is there some other setting to tell the survey to skip any geometry edits?  Is the explicit relationship class causing some sort of problem? Thanks for the help. ... View more

Hi All,  I have a GeoEvent Server dataset stored in the Spatiotemporal Big Data Store and registered as a feature service in our portal.  I can individually update the feature values using the ApplyEdits operation but I need to run a bulk update on about 75% of the dataset to modify an attribute that got incorrectly calculated during the input processing.  The service endpoint displays the "Calculate" operation but returns a error 500, blank message when I try anything even a simple set integer or string. Is it possible to use the Calculate operation on this type of feature service?  If not, I can't find any documentation that says so.   Is there another back-door management operation I can use to bulk update data?  Thanks Fred ... View more

Hi All,  I've found an issue with using 'TOP N' in the sql_clause parameter and the default * wildcard for fields when executing a arcpy.da.SearchCursor.  The resulting error message: An expected Field was not found or could not be retrieved properly. [TOP 1 OBJECTID]  ArcGIS 10.6 Occurs in both ArcCatalog python window and 64-Bit python console (ArcGISx64106\python.exe) Database is SQL Server 2017, licensed geodatabase  Occurs ONLY in registered Feature Classes.... I have an assortment of versioned, archived and non-versioned/non-archived, in feature dataset, non-feature dataset, all fail with the same error.   I have 1 registered table in the geodatabase that does NOT fail and a number of other non-registered/non-objectid tables that also do NOT fail.   I have a few non-registered spatial tables with a generic column call OBJECTID that do NOT fail I tried a couple different geodatabases in the same server, all fail same way.  I don't have a second database server to test right now.  The generic SELECT TOP 1 * FROM FC(_evw) works fine in SSMS Works fine if I include a specific fields list... but that requires extra code step and performance hit to run "describe" fc = "YourDatabaseConnectionFile.sde/Database.Schema.FeatureClass" sql_clause = ("TOP 1", None) with arcpy.da.SearchCursor(fc, "*", None, None, False, sql_clause) as rows:     row = rows.next()     print row Runtime error Traceback (most recent call last): File "<string>", line 2, in <module> RuntimeError: An expected Field was not found or could not be retrieved properly. [TOP 1 OBJECTID]‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Thanks Fred ... View more

Hi All,  Crazy technical issue... I'm creating a set of "helper tools" for power editors in an enterprise environment.  Ideally the tools will run correctly when the user is "in an arcmap edit session" or not.  I'd be fine with forcing them users to only be in an edit session when using the tools but the problem there is that after edits are made by the tool.  The arcmap editor doesn't seem to know changes have been made; clicking the "stop editing" button doesn't present the user with the save option and dumps the edits.  This is probably an edge case but --- man --- will users be mad if they lose edits and the proper attribution doesn't get pushed during a reconcile/post.   Details below.  You can also grab the source file in this repo: GitHub - fspataro/PYT-EditingIssues: Demostration of issues use ArcGIS PYT tools with an ArcMap edit session  SETUP SQLServer database  geodatabase enabled Feature dataset Feature class GlobalIds added Editor tracking enabled registered as versioned Archiving Enabled Python toolbox (pyt) based on template/help sample opens arcpy.da.UpdateCursor sets text field to input value updateRow() Geoprocessing Options Background Processing disabled Note: I re-ran all the test below with "background process enabled" but it doesn't appear to use the background processor for pyt tools. (?) TEST SCENARIO/RESULTS If 'ArcMap edit session' is closed, tools fails as expected:    "Objects in this class cannot be updated outside an edit session [TestsGDB.DBO.TES_Polygon]" If 'arcmap edit session' is open, tool succeeds, attribute update is visible in table. However, when clicking "stop editing", there's no warning that edits are pending and the session will close and reset the data. Added arcpy.da.Editor to check if 'isEditing': returns false regardless of the ArcMap editor state --- makes sense that it's not the same session Added editor.startOperation() and editor.stopOperation() with the ArcMap edit session open fails with "start an edit session" Added editor.startEditing() with the ArcMap edit session open, but no closing editor.stopEditing() this produces a successful tool run and the "save edits" dialog prompts when clicking 'stop editing' when the ArcMap edit session is closed, the tool will appear to run successfully but the edits don't persist. This seems logical since I never closed the session. Adding editor.stopEditing() with the arcmap session open this throws an error on the editor.stopEditing() with the message - "start edit session" this result baffles me ???? the attribute edits are correctly placed and the "save edits" dialog prompts when clicking 'stop editing'. So it's almost correct behavior except for the "tool failed result" when the ArcMap edit session is closed, the tool will execute as expected and the edits persist It seems like my choice is use the full script edit session management and sink the error on stopEditing so it works in and out of the ArcMap edit session or don't use the script edit session and the user can only work in an ArcMap session and might not get the prompt. ... View more