Latest Contributions by BlakeTerhune

This is likely the issue. The other way to accidentally use the feature class instead of the layer is when choosing the value in the parameter at run time of the script tool. I'm assuming you have a parameter for "Project_Layer". If you're browsing to the feature class in a geodatabase for this parameter instead of choosing it from the list of layers in the map, then it'll calculate on all records (without the selection). Also, if you have the same feature class added to the map in more than one layer and you choose the wrong one (without a selection), it will calculate on all records. So there's multiple ways to mess this up. It might be worth adding some validation in your script tool to check if the layer has a selection. You can use the getSelectionSet() method on the Layer object. ... View more

After making a selection, you can use the CalculateField Python command (or geoprocessing tool) to edit the fields of only the selected records. However, make sure your input for it is the layer with the selection and not a generic path to the feature class in the geodatabase. In the latter case, it won't have a selection and it will field calc all records. You can also run the tool with an undo option in case there is unexpected behavior. ... View more

If you check the documentation for Split(), you'll see the last parameter is removeEmpty. There's something in the logic of how Split() works that can create empty items in the array and setting removeEmpty to true will resolve that. ... View more

Could you make another GraphicsLayer for display? When a graphic in the "base" layer is clicked, you add it to the "display" layer (above the base). Then remove it from the "display" layer when something else is clicked. ... View more

You might need to use Convert() in the SQL expression to explicitly specify the value is a date and not a string. I also reorganized a little bit for readability.   # Fetch data from both tables workorders_data = [] and_expressions = [ f"Type = '{type_query}'", f"teamLeader = '{leader_query}'", f"teamAssigned = '{assigned_query}'", f"dateReceived <= Convert(datetime, '{date_before}')", f"dateReceived >= Convert(datetime, '{date_after}')" ] expression = " AND ".join(and_expressions) with arcpy.da.SearchCursor(f'{gdb_path}\\{workorders_fc}', workorders_fields, where_clause=expression) as cursor: for row in cursor: workorders_data.append(row)     ... View more

I use ArcSDESQLExecute for querying non-spatial databases too. Your mileage may vary as the SQL gets more complex. ... View more

I've been able to use ArcSDESQLExecute as a replacement for basic things. ... View more

I think ArcGIS Pro Questions is a safe bet. ... View more

I have had this happen when clicking links in the automatic subscription emails, but it's rare; maybe 10% of the time. ... View more

You could create a script tool or Python toolbox that runs inside ArcGIS Pro. Both give you a simple user interface and custom messaging. ... View more

Esri has some documentation called the ArcGIS Well-Architected Framework that might be useful to get started with. ... View more

Do the users have ArcGIS Pro installed? ... View more

You can use Python to open a search cursor using the fields in the order you want with a sql_clause parameter to sort on the field you want. Iterate through each row of the cursor and write the data to your text file. You can even use the Python CSV module. ... View more