Latest Contributions by BradJones3

I had this problem if I was writing any data to the SAN, accessing data on, or writing data to, the SAN (shapefiles, File GDB, .loc files, any package files, and even .sde connection files).  I'm working around the problem and probably won't visit again until we upgrade to 3.0.  I posted here to see if anyone else experienced this or if maybe someone at Esri had thoughts. ... View more

Nope.  I don't think there is a way. ... View more

Thanks for the quick reply.  I'll wait for 2.7 ... View more

I was thinking along the lines of what we are capable with the ArcGIS API for Javascript, synchronized between map and charts. No worries, I've moved to developing my own app/dashboard. ... View more

Oh, dear... Robert, I'm such an idiot. It's 'outFields' not 'outfields'. I went to AJAX and it was working because i was using outFields A typo will be the death of me someday. I apologize for taking up your time. *places dunce developer hat upon head and heads to the corner* ... View more

Still only returns TAGNAME field. ["geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.AF2295LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.AS1941CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.AS1941LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.CAB2295LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.CR1941CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.CR1941LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.CV1942CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.HR1942CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.JR1941CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.LA1941CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.LA1941LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.LF1941CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.LF1941LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.LM1941CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.LM1941LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.RR1942CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.RR1942LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.SE1942CAT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"ADAMS.SE1942LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"FOURCHE.FC2295LQT.F_CV"},"popupTemplate":null},{"geometry":null,"symbol":null,"attributes":{"TAGNAME":"MAUMELLE.LM1941CAT.F_CV"},"popupTemplate":null}]{ ... View more

When you declare your rainAmtTbl do you specify the outFields parameter? If you do not then only fields that are used in the renderer will be returned along with ObjectID and Shape fields. Originally I didn't, but I added it and get the same result. Also, this is a GDB table, not a featureclass. So no geometry fields. Maybe this is the problem? const rainAmtTbl = new FeatureLayer ({ url:'https://gis.lrwu.com/server/rest/services/RainGauges/Rain_Gauges/FeatureServer/2', outFields: ['*'] }); So is that a parameterized query in an enterprise database? If not then the where clause looks strange. I'm using template strings. Just a different formatting option.  It's the same as "TAGNAME = '" + tag + "'"  query.where = `TAGNAME = '${tag}'`;    3. Or are you using  jQuery in your app? No jQuery. I hate to say this but at one point the result included all the fields but I can't remember what I did in that instance. I might have been attempting to go through the related featureclass. In that instance I tried parsing the json but that didn't work. For the most part I have working with queryFeatures or using a QueryTask.  I pretty much get the same results.  ... View more

Here's what is happening: The SelectLayerByLocation_management function is using the subbasin layer— before the definition query is applied— as the selecting features input. Whatever definition query is applied to the subbasin layer when the project is opened is the one used for the spatial selection. Even though I get the correct layer object and use it as a parameter in the selection (line 33). In the image below there was no definition query applied to the subbasin layer before the tool ran, so the selecting features were all the subbasins. I even had the tool sleep for 30 sec (line 30) while I manually refreshed the map to no effect (BTW, there is no refresh method in the Map class of the mp module). Next step is to export the layer with the definition query applied then use that output as the selecting features in the spatial selection. EDIT: CopyFeatures_management does the same thing as SelectLayerByLocation_management This is only an issue when run as a GP tool.  No issue in the python console. Sure would be nice if someone from Esri would comment on this... import arcpy from arcpy import env import time # Global variables # ---------------- aprx = arcpy.mp.ArcGISProject('CURRENT') myMap = aprx.listMaps('Map')[0] sbCode = arcpy.GetParameterAsText(0) sbAIName = f'Subbasin {sbCode}' sbDefQ = f'AREA_CODE = {sbCode}' # Get the layer objects mshLayer = myMap.listLayers('Mapsheets')[0] mshAILayer = myMap.listLayers('AI Mapsheets')[0] aiResultLayer = myMap.listLayers('AI Results')[0] sbAILayer = myMap.listLayers('Subbasin *') myMap.clearSelection() for sb in sbAILayer: arcpy.AddMessage(f'Layer name start of loop: {sb}') arcpy.AddMessage(f'Subbasin query string: {sbDefQ}') sb.definitionQuery = sbDefQ arcpy.AddMessage('Definition query applied to AI Subbasins.') sb.name = sbAIName arcpy.AddMessage(f'AI Subbasin layer name changed to {sbAIName}') arcpy.AddMessage(f'Layer name end of loop: {sb}') arcpy.AddMessage('Sleeping for 30 seconds...') time.sleep(30) # Manually refresh the map during sleep # Layer object again to ensure I have the correct one for selecting feature below sbSelection = myMap.listLayers(sbAIName)[0] # Perform spatial selections # -------------------------- # Select Acoustic Inspection results in desired subbasin resultsSelect = arcpy.SelectLayerByLocation_management(aiResultLayer, 'WITHIN', sbSelection, 0, 'NEW_SELECTION') arcpy.AddMessage(resultsSelect) ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

That's the problem...There were no selections.  The selections are cleared each time.   And I'm deleting the display cache.  I may try rebuilding the project from scratch. ... View more

I tested everything in the Python console before I moved it to the script tool.  So the first time it ran as a script tool the mapsheets/grid selection was same as the previous run in the console—not the desired result. I created a new project, imported the maps and layouts, and created another script tool and the result is the same.  The mapsheet/grid selection result is what was desired in the last run in the other project. ... View more

I gave the layers completely unique names as a quick test and the result is the same. I think I may just rebuild it as an ArcGIS Pro add-in. ... View more