Latest Contributions by JoeBorgione

click in the link in my post... Also, depending on what you are using, you will be presented the same Arcade edit window, which allows you, test, access global variables and functions.     ... View more

In this post I provide an arcade attribute rule: is that what you are asking for? ... View more

Check out the logic page for arcade Also, you can use the Arcade Playground to do just that: play with Arcade.  I played around with this statement there until I got it right...   var field1 = 12 var field2 = 250 if (field1 == 12 && field2 < 300 && field2 > 200){ Console("yay")}   The playground is the only place I know where the Console() function works. It's the same as the print() function in python. ... View more

ArcGIS Pro 2.4.1 is being used. BUG000127016...  ArcGIS Pro 2.4.2 and fixed in ArcGIS Pro 2.6.x. Good detective work @Robert_LeClair  ... View more

Perhaps you could use the 'Insert/Edit Code Sample' tool in the expanded tool bar and copy and past your code up to an including the line that fails.     (choose python)   ... View more

The parameters are what the create locator tool uses.  If you go to your geoprocessing history you can grab the parameters and copy and paste them into a text file.  I do that all the time so I can paste that text in a python script.  See gif below.   At sometime I thought I read about the same problem that I had or someone else had and posted it here.  But I couldn't find anything.  Sending a shout out to a couple of ESRI Geocoding SMEs: Shana or Brad, is there an issue with zone/no zone once you publish a locator? @ShanaBritt  @BradNiemand    ... View more

You make a list of all the fields you want to concatenate; then step through that list, and if a given field is empty or null, you do not concatenate that into the returned output.   ... View more

Can you post the parameters from the tool history that show how it was set up?  What type of locator is it:  A single or multiple role.  Did it work as expected before you published it? ... View more

Google that error and you'll come across this from ESRI.  It looks like a fairly generic, non-specific error so I really don't know what the problem is.  You may want to consult ESRI tech support. ... View more

Here's another vote for a data issue; I won't even go into my usual tirade of special characters in free text fields.  You've already discovered one of the reasons I don't like them.... ... View more

The only thing I can think of is perhaps make your edit calls outside of the try/except block:   def calcNorthing(): edit.StartEditing(False,True) edit.startOperation() try: do your thing except: trap the exception edit.stopOperation() edit.stopEditing(True)   You could also check the edit status in main() to be sure if it's stopped or not before making the call to your function. Take a look at this too.. ... View more

I'm not familiar with importing the cursors module. Instead I suggest you use the da.UpdateCursor. When editing an enterprise geodatabase (aka SDE), you need to start an edit session and close it it as well:   ws = r'X:\some\path\to\your\enterprise.gdb' edit = arcpy.da.Editor(ws) edit.startEditing(False,False) #see the documentation on the parameters edit.startOperation() with arcpy.da.UpdateCursor(blah, blah bla) as cursor: for row in cursor: blah blah blah cursor.updateRow(row) edit.stopOperation() edit.stopEditing(True)     @DavidPike , using 'with' in any da cursor is traditionally the way to go; I've used that approach hundreds of times without an issue... ... View more

You said you are sure that no one else is on the db and yet you get a schema lock.  Okay, then something else must be wrong.  All I'm saying is it's easier to learn how to craft attribute rules without the overhead of an enterprise gdb getting in your way.  Your call... ... View more

I suggest you copy your data to a file geodatabase and do your development there. ... View more