Latest Contributions by RussellBrennan

@JasonRoss1 this went into Pro 3.6 which is released. ... View more

I am pleased to share that we have implemented this enhancement for the next release of ArcGIS Pro. Note: This uses an origin > destination approach where the origin table must be the feature data and the destination table must be the stand-alone table. If the stand-alone table is the origin table the stand-alone table will be empty when taken offline using this new option. We will be providing a check box on the Download Map button to allow you to take only the stand-alone records that are related to features in the map. This is what it will look like.   ... View more

Thanks for bringing this to our attention and apologies that we missed this in our internal testing. We have been able to reproduce this in house and are currently working on a fix. Barring any unforeseen problems or compatibility issues, we are planning to have this fixed in a Pro 3.5 patch.  ... View more

Hi all, have any of you submitted a support case? If you have a case number you can share I can reach out to the Support analyst directly. Can you confirm these are the steps to reproduce: 1. Add an AGOL feature service layer/table (layer 1) and it's related layer/table (layer 2) to a map in Pro. 2. Open the attribute table for layer 1. 3. From the attribute table window click on the 'burger' and then select 'Related Data' > layer 2 4. This should select the related record in the map for layer 2 and open layer 2's attribute table with the related record selected. Bug> step 3 doesn't do anything.   Edit: this seems to be feature services in general not specific to AGOL based feature services ... View more

This idea has been implemented in ArcGIS Pro 3.5. The Add WFS Layer(s) dialog box appears when you add a WFS layer to the map. Use this dialog box to optionally limit features to an area of interest, set the maximum number of features returned, or set the page size to be used. The default value being used to limit the number of features added to the map will be displayed and available to edit before adding the layer to the map. The link above will have additional details when 3.5 goes live. ... View more

@JamesRains Happy to hear that helped! ... View more

Hi @JamesRains It looks like the layer is coming from a Map Image Layer (Map Service)? By default, these are added as composite layers:  https://pro.arcgis.com/en/pro-app/3.3/help/data/services/use-map-image-layers.htm#ESRI_SECTION1_1B5AB5F9429F4295827ACBB30AB493FF The UI in the screenshot shows a composite layer as indicated by the connector I have highlighted below: I suspect  that if you add the sublayer of the Map Service as a feature layer, you should be able to get the functionality you are looking for.  To add a map image layer's sub layer as a feature layer you have two options: The first option: In the Contents pane go to your Portal and find the map image layer item. Double click on the item to display the sub layers. Once you see the sub layers you can drag and drop into your map or right click and choose to add to a map. The second option: Get the URL of the Map Service and use the sub layer URL with the 'Add Data From Path' option: https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/add-layers-to-a-map.htm#ESRI_SECTION1_FABB01A75AFE4A1FB0BEC3D7CE74E3C5. When using this second option you would want to pass in the URL pointing to the sub layer not to the map service. For example: Use this with the /1 for the first layer: https://sampleserver6.arcgisonline.com/arcgis/rest/services/PoolPermits/MapServer/1 Do not use this without the /1 for the entire service: https://sampleserver6.arcgisonline.com/arcgis/rest/services/PoolPermits/MapServer         ... View more

Hi Michael, BUG-000150723 was resolved for the case where features were disappearing after split in a named branch version. Here is the repro case for this bug which I am no longer able to reproduce in 3.0.6, 3.1.3, 3.2: Polygon Branch Versioned Feature Layer (Version must be the non default version) Load in the a Branch Versioned Polygon Feature Class into Pro Select a feature on the map and run the split tool from the editing tool bar to split the polygon Reselect the polygon and run another split on it. Notice in the attribute table that it will say 3 features are selected, but only two are visible in the attribute table. We did work in 3.2 to resolve this issue and installed those same fixes in the 3.0.6 and 3.1.3 updates. I am no longer able to reproduce the behavior as described in the repro case. Likewise, in my testing I could not reproduce BUG-000151169 when testing with 3.0.6, 3.1.3, or 3.2. Here is the repro case I received for BUG-000151169:   In the editing menu, select the "Split" tool Select the polygon, perform a split operation. This is successful. We'll call the created features polygon #1 and polygon #2. Without de-selecting anything, perform a 2nd split operation on polygon #2. This fails with an error message: "Splitting features failed. ERROR: Unable to complete operation. Unable to perform applyEdits operation. Error: A polygon cut operation could not classify all parts of the polygon as left or right of the cutting line." Press escape, discard edits, clear all selections. In the editing menu, select the "Split" tool. Select polygon #2 and attempt the "Split" operation. This succeeds, but not in the way intended. BUG: The result "cuts" or "removes" part of the polygon (it disappears) instead of performing a split. I recently marked this issue as non-reproducible because I could not reproduce with any of our supported/patched software. Can you please work with Technical Support to get a bug logged with the behavior you are seeing as it appears to be slightly different than these two bugs? This will be the easiest way for my team to get the appropriate repro case for this. Unfortunately the error message "Error: A polygon cut operation could not classify all parts of the polygon as left or right of the cutting line" can arise in many scenarios and seems to be causing multiple issues to be convolved.   ... View more

@MichaelJimenez you need to escape the quotes. I came across this looking for answers when I ran into the same issue so I assume you have moved on. Since the outstatistics parameter is JSON not just a simple string you need to escape the quotes in the outstatistics JSON that is passed in. This is the code I wrote for my case.  # Set variables before execution lName = "TestLayer" #layer name from contents pane statField = 'TextField255' #field to get statistics from whereClause = '1=1' #optional where clause import arcpy from arcgis.gis import GIS from arcgis.features import FeatureLayer gis = GIS("home") url = arcpy.Describe(lName).catalogPath layer = FeatureLayer(url) hClause = "Count({}) > 1".format(statField) queryResult = layer.query(where=whereClause, groupByFieldsForStatistics=statField, havingClause=hClause, outStatistics="[{\"statisticType\":\"count\",\"onStatisticField\":\"%s\",\"outStatisticFieldName\":\"NonUniqueCount\"}]" % (statField)) queryResult.sdf[['TextField255', 'NonUniqueCount']] Note that I was using this inside of Pro so I have a mix of arcpy and arcgis api for python in my example. Hope this helps you or someone else reading this later. ... View more

@LindsayRaabe_FPCWAHave you seen this doc: https://developers.arcgis.com/rest/services-reference/online/truncate-feature-layer-.htm My understanding is that you cannot set this property, rather it will be true if the following conditions are met. 1. you need to be running Truncate as owner (publisher) of the feature layer or a portal administrator to be able to truncate 2. the layer cannot have sync or change tracking enabled. 3. the layer cannot have relationships with other layers 4. the layer cannot be a view layer or be a hosted layer that other view layers are created off of. I am trying to get confirmation on my statements above to make sure I am correct. ... View more

@LindsayRaabe_FPCWA I am happy to report that this should be a lot faster in Pro 3.1. We are now grouping edits into fewer round trips to the feature service so it should work a lot faster especially in cases where you are deleting a lot of data. This is for both Delete Rows and Delete Features tools.  We have also made some server side changes that allow us to put more edits into each ApplyEdits request we send to the feature service (Asynchronous ApplyEdits and ApplyEdits with UploadID) . Look for these server side changes in Enterprise 11.1 and the next (summer update) to ArcGIS Online. ... View more