Latest Contributions by BlakeTerhune

In this case, since you are pointing at a layer input by the user, I would suggest that the user have the database connection pointed to the correct version when it's input. If not, you could either create a new database connection (or connection string) pointed to the version you want. Or you can try useing Change Version. ... View more

Does the order of these values matter after you remove duplicates? ... View more

Maybe use None for the wildcard parameter instead of an empty string. df = arcpy.mapping.ListDataFrames(mxd, None)[0] lyr = arcpy.mapping.ListLayers(mxd, None, df)[0]   ... View more

I haven't done this in ArcMap, but your path doesn't look right. Try removing the two trailing back slashes. ... View more

The CIM is a weird and wonderful world. I highly recommend watching the session from the 2024 Esri Developer Summit. ArcPy: Beyond the Basics of arcpy.mp   ... View more

This is possible, but only through manipulating the CIM, which is a bit tedious. Python CIM access—ArcGIS Pro | Documentation def highlightField(map, layer_name, highlight_field_name): lyr = map.listLayers(layer_name)[0] # Get the layer's CIM definition cim_lyr = lyr.getDefinition("V3") # Ensure the featureTable has fieldDescriptions to modify # https://pro.arcgis.com/en/pro-app/latest/arcpy/mapping/python-cim-access.htm#GUID-C80C9CF4-67C8-418E-BEB5-386B18EE6097 if len(cim_lyr.featureTable.fieldDescriptions) == 0: # No CIM field descriptions class; create one. fDesc = arcpy.cim.CreateCIMObjectFromClassName('CIMFieldDescription', 'V3') # Get field info and populate the new field description. highlight_field_props = [f for f in arcpy.ListFields(lyr) if f.name == highlight_field_name][0] fDesc.alias = highlight_field_props.aliasName fDesc.fieldName = highlight_field_props.baseName fDesc.highlight = True fDesc.visible = True fDesc.searchMode = "Exact" # Add new field description to the CIM. cim_lyr.featureTable.fieldDescriptions.append(fDesc) else: # Make changes to field description in CIM. for f in cim_lyr.featureTable.fieldDescriptions: if f.fieldName == highlight_field_name: f.highlight = True # Push the CIM changes back to the layer object lyr.setDefinition(cim_lyr) aprx = arcpy.mp.ArcGISProject("current") highlightField(aprx.activeMap, "MY_LAYER_NAME", "MY_FIELD_NAME") In my testing, the fieldDescriptions was indeed empty (as the documentation notes) so I created a CIMFieldDescription only for the field being highlighted. This has the effect of moving the highlighted field to the beginning of the attribute table view. If that is not acceptable, you will have to create a CIMFieldDescription for each field in the order you want. ... View more

Shout out to the GIS cohort in the Phoenix metro area! @MeleKoneya has inspired the City of Chandler to implement a similar solution for our Fire/Health/Medical teams during big events. ... View more

Unrelated question for you, @JakeSkinner: Do you recommend using del on a cursor even when it's used in a with statement? ... View more

If that hard coded workspace path worked fine, then it's not a problem with the database. I see you are doing some other workspace path manipulation if the input feature class is in a feature dataset. Try some other variations of the path to see if you can get it to fail when hardcoded. My guess is that you're getting something in the workspace that is causing Editor to hang. ... View more

Okay, that looks fine. Now try an isolated test with the arcpy.da.Editor() with that workspace and see what happens. workspace = 'F:\\GIS\\WORKING FILES\\TestProjects\\TestingDB.gdb' with arcpy.da.Editor(workspace, multiuser_mode=False): arcpy.AddMessage('starting edit') # Nothing else, just leave the script. ... View more

Maybe something isn't right with your workspace manipulation. Try messaging out the workspace before you open the editor, then see if it works when you hard code that workspace path (or something else you know to work). ... View more

What version of ArcGIS Pro are you using? ... View more