Reviving an Arcpy Addins Extension

Question

A year or so ago I was working with Arcpy Addins. I had created an extension that used to run a def openDocument() that creates a numpy array out of a table view: class ExtensionClass1(object): """Implementation for AddressValidatorExtension_addin.extension2 (Extension)""" def __init__(self): # For performance considerations, please remove all unused methods in this class. self.enabled = True def openDocument(self): myTable = r"I:\GIS\ArcSDE\SuperUser\slcogis\gdb_ADD\gdb_ADD@slcogis.sde\SLCOGIS.gdb_ADD.JoesArray_vw" fields = ['FULLNAME', 'LowCoordName', 'HighCoordName','Alias1','Alias2','Alias3','Alias4','STR2_LOW_RANGE','STR2_HIGH_RANGE'] global arr arr = arcpy.da.TableToNumPyArray(myTable,fields)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ The problem is when I try to execute the other functionalities of the extension it errors out at the first call to that array: Traceback (most recent call last): File "C:\Users\JBorgione\AppData\Local\ESRI\Desktop10.5\AssemblyCache\{FB53601C-244C-4DF3-87C2-E18F723FA707}\AddressValidatorExtension_addin.py", line 71, in onEnter name = arr[np.where(arr['FULLNAME'] == enteredName)] NameError: global name 'arr' is not defined ‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Not sure what I'm missing, and hoping another set of eyes can catch it

JoeBorgione · Answer

I'm thinking there is something wrong with the way I using the openDocument() method within the extension itself. I just took a took look at ArcMap Python Add In Extension does not execute where Darren Wiens‌ provides a means to test. I created an extension that only does one thing: open a message box. However, with the extension added to an mxd, when I open that mxd, no message box appears.... ##### this is the entire python script for my TestOnOpen extension... import arcpy import pythonaddins class ExtensionClass1(object): """Implementation for TestOnOpen_addin.extension2 (Extension)""" def __init__(self): # For performance considerations, please remove all unused methods in this class. self.enabled = True def openDocument(self): pythonaddins.MessageBox('It Ran!!!','INFO',0)‍‍‍‍‍‍‍‍‍‍‍‍‍

DanPatterson_Retired · Answer

This is what I use sometimes. It needs field objects, just not their name (edit the code otherwise). You can change what you want as the returned value. I normally just return the min for the data type. For string/text, just the string representation of text def null_dict(flds): """Produce a null dictionary from a list of fields These must be field objects and not just their name. """ dump_flds = ["OBJECTID","Shape_Length", "Shape_Area", "Shape"] flds_oth = [f for f in flds if f.name not in dump_flds] nulls = {'Double':np.nan, 'Single':np.nan, 'Short':np.iinfo(np.int16).min, 'SmallInteger':np.iinfo(np.int16).min, 'Long':np.iinfo(np.int32).min, 'Float':np.nan, 'Integer':np.iinfo(np.int32).min, 'String':str(None), 'Text':str(None)} fld_dict = {i.name: i.type for i in flds_oth} nulls = {f.name:nulls[fld_dict[f.name]] for f in flds_oth} return nulls‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

JoeBorgione · Answer

I can't afford to skip a row if one of the lesser-used fields has a null or empty value, so I need to take that into consideration.  Just to get it up and running I can substitute a more ArcGIS friendly datasource (feature class or table and then make feature layer or make table view as needed) for the SQL view.  We have the SQL view in place because (if you recall) the data is actually stored in a mainframe and we get a db dump from it and then SQL-view the dump.  Big fun....