Latest Contributions by RussellBrennan

@LindsayRaabe_FPCWA The Truncate tool operates at the data source level (geodatabase feature class or feature service layer) not at the layer level such as feature layers created in Pro maps or geoprocessing workflows. As such it will delete all rows not just a subset defined by a feature layer. ... View more

Hi @LindsayRaabe_FPCWA  At the next  (Autumn/Winter 2021) release of Pro the Truncate tool will be available to you when working with AGOL hosted services AND you are connected as a portal admin or service owner.  We are also looking to make the improvements you request for deleting features/rows in upcoming releases but this likely will not make it into the software until the release after next (approx. Spring/Summer 2022 at the earliest). As a sort of 'hack/workaround' you can use the button to enable undo on the Delete Rows tool. This should execute very quickly because it is first done on the client (Pro). When you then you click save, this is when we will send edits to the server. Doing it this way will result in fewer edit requests to the server which should speed up the deletion. We have some doc on this delayed editing behavior here: https://pro.arcgis.com/en/pro-app/latest/help/data/services/edit-web-feature-layers.htm but you would sort of have to read between the lines to figure this out on your and how it might benefit in these sorts of situations. Hope this helps. Russell ... View more

Hi MTaft,  In the next release of Pro we will consume a new service property for a 'preferred time zone' that will be available in next releases of ArcGIS Online and Enterprise. This preferred time zone is what Pro will use to display your data, as a service owner/admin you will be able to set this property to whatever time zone you want to use to work with your data. We hope to build on this functionality in subsequent releases. Russell ... View more

If you set up your services such that they are published from a versioned dataset (enterprise geodatabase) and you publish by reference instead of a hosted service, this is already supported.  See: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/offline-maps-and-versioned-data.htm This is also a video from 2.1 (but still relevant) for working with versioned data: https://youtu.be/6VnRHvWWjjA?t=796  With this workflow you can perform reconciles after edits have been synced and choose how you want to define conflicts.  I am not sure if this would be helpful for your needs. Or perhaps your request is more specific to working with Hosted data? ... View more

Hi Ted,  Are you asking for the tool 'Table to Domain' to be supported for hosted services (we currently do not not support this tool with services) or are you asking for something else? Thanks. ... View more

I should also add that hosted feature layers do not currently support storing true curves in the data source. So curves are always 'densified' when created in these layers.  FAQ Article: FAQ: Are curves a supported geometry type for hosted feature layers in ArcGIS Online and the REST API?  ... View more

Thanks for reporting this, we have fixed this in Pro 2.6. ... View more

Do you have Fiddler installed on your machine? This could tell you if query requests are being submitted from Pro and it's just slow or if Pro has hung. ... View more

Tom, I am trying to get BUG-000129303 (sync issue) fixed but it's not looking like it will make 2.5.1. I will keep you updated if this changes. ... View more

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