Latest Contributions by RussellBrennan

The timeout issue with large geometries/rows has been resolved in current development builds of 2.6 and provided the fix remains stable until we ship the software, it should be there when we ship. I am not sure if it will make it into a 2.5.x release or not I am working on the details of that now. ... View more

Rob,  How exactly does it work? For services that do not have the version management (VM) capability the edit session (undo/redo/save/discard) functionality is new in 2.5. For services with version managment capability enabled the edit session functionality remains as it has since 2.2. With these (non VM enabled) services in 2.5 it is a client side* implementation, meaning that edits are stored locally in Pro until you save.  Is the AGOL server rolling back the edits? Or do the feature updates not get submitted until you save? Or is some other local caching option in play? AGOL/ArcGIS Server/Enterprise is not doing the undo/redo, most of the edits get submitted during save. See my note below about inserts. If I update a large number of rows, is there an impact to the undo capability? The impact is in the amount of time that it takes for the save operation to complete. The more edits that are stored up client side the longer it may take for the save operation to complete. Other considerations: There are three behaviors that Pro delegates to the 'server' that will not be available until you save.  - Relationship classes - the primary/foreign key management is done by the server. You can create a relationship  between records but will not be able to navigate the relationship until saving. - Attribute rules that are 'excluded from client side evaluation'. These rules rely on server execution, you won't see the behavior of these rules until you save edits. - Editor tracking. Editor tracking values will not display on your rows until save. *For inserts we insert the feature immediately on the server in order to obtain an row identifier (OID). An undo of this insert results in a delete of the row during save.  Here are some slides I was going to present at Dev Summit on this topic sort of re-iterating what I posted above. Note that the distinction between versioned and non-versioned is not an official Esri term. I am using this distinction in for the presentation to describe the two types of services more succinctly. Officially these are 'web feature layers with the version management capability enabled' or 'web feature layers without the version management capability'. The scenario that Tom describes above is a change in behavior that we are considering a bug and have already resolved in the next release of Pro. When you have data that has very large geometries (large multipart or very dense/high number of vertices per feature) editing attributes of those rows may time out. This is because editing those rows in 2.5 is sending the full row rather than just the edited field. In 2.4 we were only sending the edited fields so the geometries would not be sent and thus cause a timeout. However, to be fair, our testing showed that the same row edits would time out in Pro 2.4 as well if the geometries were edited. ... View more

The code below (or a slightly modified version) should also give you the behavior you are looking for. Run this from the python window with the map you are interested in renaming layers for. aprx = arcpy.mp.ArcGISProject("CURRENT") map = aprx.activeMap for lyr in map.listLayers():     if lyr.dataSource.find("FeatureServer"): # can change "Feature Server" to any text that might be in your URLs         lyr.name = lyr.name + " (HFS)" # can change "HFS" to any label you want. Note that you can change "FeatureServer" to any part of the URL you want to use to identify your layer as a service layer. You can also change what gets appended to the layer name by changing (HFS) to something else eg: (Service Layer) or similar. ... View more

Hi John,  Pro currently checks the editability of the layer and sets these editing capabilities internally resulting in the behaviour you are seeing. We are looking into better support for server roles and behaviour in the release of Pro following 2.2.  ... View more

Thanks for bringing this to our attention. We are looking into what can be done to resolve this for the next release. ... View more

Hi Paul, This is currently a limit with feature services in Pro. In the current software appending is done one row at a time. We are investigating possible performance improvements for the next few releases such as grouping the edits into fewer calls or use the Append API on the back end.  ... View more

Collin, This issue was resolved with Pro 2.0. There is also a new Append option on the item page in the latest release of ArcGIS Online. This is a very efficient way to load data into your hosted services. I would recommend looking into this if you are using AGOL hosted feature services.  Russell ... View more

Hi Paul, This is a bug that was introduced at Pro 1.4. We are investigating the cause of it now and plan to have a fix for this in the next release. If our investigations reveal a workaround I will post it here. - Russell ... View more

There is still no way to create a historical marker via python as of 10.3.1. However you can connect to your geodatabase at a point in time using python. If you use the Create Database Connection tool (which was new at 10.1 I believe). This tool lets you specify a point in time you wish to connect to. This will connect to your archived data at that point in time. Not quite a historical version but pretty close. ... View more

Hi Juho, Are you using ArcGIS Server feature services or hosted feature services from ArcGIS.com? Why is it that you want to use per replica instead of per layer sync? ... View more

Yes ... View more

Can you post some of the code that you are trying to execute? There is an example in the help for how to work with this: import arcpy import os fc = 'Database Connections/Portland.sde/portland.jgp.schools' workspace = os.path.dirname(fc) # Start an edit session. Must provide the worksapce. edit = arcpy.da.Editor(workspace) # Edit session is started without an undo/redo stack for versioned data # (for second argument, use False for unversioned data) edit.startEditing(False, True) # Start an edit operation edit.startOperation() # Insert a row into the table. with arcpy.da.InsertCursor(fc, ('SHAPE@', 'Name')) as icur:    icur.insertRow([(7642471.100, 686465.725), 'New School']) # Stop the edit operation. edit.stopOperation() # Stop the edit session and save the changes edit.stopEditing(True) ... View more