Latest Contributions by RyanDavis1

Hi @ShaunWalbridge , I appreciate your suggestions. They did confirm my suspicions that the dev toolbox was referencing the prod files. Based on that information, I figured out that the prod toolbox was listed as a favorite to load to all new projects. I typically drag my dev folder into Pro each time for testing. It seems that Pro prefers the file names and paths of the favorite production toolbox. I have since removed it from my favorites, and so far the dev toolbox is referencing the correct files. I created a support ticket earlier today and will be following up with this information. Thank you for your help. ... View more

Hi @ShaunWalbridge, I've found the problem here, but I'm at a loss as to how to fix it. I may have to create a Tech Support ticket because I would describe it as a bug. Summary:  I have two, separate Python toolboxes with similar file paths and file names on my PC. One is a development toolbox while the other is for staging/production. When I load/run the dev PYT, it is referencing the files (.py, .pagx, .lyrx, etc.) in the prod PYT's folder. This behavior is rather inconsistent. I'm not sure if it's a Python issue or something wrong with ArcGIS Pro folder connection configuration or I'm totally doing something wrong. Sometimes after a restart, the problem goes away but not always. The folder structures are something like this: dev_folder - DevPythonToolbox.pyt - subfolder -- __init__.py -- module.py -- other supporting files prod_folder - ProdPythonToolbox.pyt - subfolder -- __init__.py -- module.py -- other supporting files The relevant code is like this:   # Top of DevPythonToolbox.pyt import arcpy from subfolder import module from importlib import reload # for dev only reload(module) # for dev only ... class Tool(object): def __init__(self): ... def execute(self, parameters, messages): """The source code of the tool.""" from subfolder import module # for dev only from importlib import reload # for dev only reload(module) # for dev only if __name__ == "__main__": module.main(parameters) return     Is there a place where these file paths are cached or indexed? I have already tried deleting Local Caches and Index folders in C:\Users\user\AppData\Local\ESRI. Thanks, Ryan ... View more

Hi @SilasMathes , No, after some exploring I found the .aptx less than ideal for our purposes. It's been long enough that I don't remember the exact issues now. We ended up using a Python toolbox (.pyt) with supporting files (.py, .pagx, SDE connections, .lyrx, etc.) contained in a directory in the same folder as the .pyt. It generally works well, but development hasn't been without it's headaches. ... View more

Hi @Shaun-Walbridge, It's been a while since I posted this, but this is still an ongoing problem.  I also delete my .pyc files but that doesn't seem to help. I'm updating scripts and layouts, but the tool wants to hold onto old versions of the scripts.  My first clue it's using an old version of the script is an arcpy.AddMessage right at the beginning that includes the last update date of the tool.  But, it will bring in versions of layouts and maps that don't include my latest updates. I'm now on Pro 2.9.4 since posting this.  I'm also using git if that could have anything to do with it. Thanks, Ryan ... View more

@RichardHowe, if I follow you correctly I'm doing this in a Python toolbox.  My parameter type is multivalue GPString, and I apply a ValueList type filter.  I then have a parameter.filter.list of strings for the user to choose from. ... View more

I appreciate the follow up @OwenGeo  ... View more

Thanks for the reply @NathanEnge .  I just tested this out, and it looks like if I want to persist the query layer I have to export it to the SQL Server database.  That saves it as a new table not as a view so we're still looking at redundant data.  We generally prefer views so we don't have to repeat geometry over and over. I suppose it's a "view" that can be saved with my .aprx, but as far as I can tell it's not saved anywhere else. ... View more

Thank you for the reply @Borch.  I think your answer is mostly correct, but we clearly can publish SQL Server views as feature services because we have routinely done so for years.  Regardless, I think the documentation you quote explains what Esri really means is that they don't support editable feature services. ... View more

I'll add that I've noticed the consolidation and packaging tools tend to convert f-strings to .format and then assign them to g_ESRI_variables.  No idea why. Generally speaking, I have little problem with f-strings but every so often Pro [2.6] returns an error.  Sometimes it's solved by simply closing the program and re-opening.  It seems really inconsistent. ... View more

This is an old thread, but it led me to believe this wasn't possible for a long time.  After looking over documentation, I was able to use arcpy to set the spatial reference on the map object. Something like this works for me: mapx.spatialReference = arcpy.SpatialReference(prjFile)   where mapx is a map object.  Hope that helps someone. ... View more

This idea is sorely needed and should be voted up higher.  If I rebuild registered tables or views outside of ArcGIS, the metadata contained inside the SDE tables is no longer accurate and those objects might not even be usable inside of ArcGIS.  Basically, I have to be entirely sure that my object is in its final production state before registering. It's hard for me to fathom that I have to delete the object from within ArcGIS to remove all of the references first.  It doesn't seem like it should be huge lift to have a tool that removes all of the references in the SDE tables. ... View more

Update:  Talked the problem over with some Esri folks.  As a result I am going to explore the use of geoprocessing packages (.gpkx) rather than project templates (.aptx).  I will come back to this post to update. ... View more