Latest Contributions by AndyEgleton

‎04-14-2023

Hi Vince, Can you describe the Describe process? I've tried in the DB and in ArcGIS and it doesn't pick up the change in metadata. Thanks

‎03-28-2023

Hi Shaun, There is an open case: 03301233. Thanks

‎03-16-2023

I've used arcpy.Describe for LayerFiles now, its just extra lines of code: desc = arcpy.da.Describe( item ) some_detail = desc.get( "shapeType", None ) vs desc = arcpy.Describe( item ) some_detail = None with contextlib.suppress( AttributeError ) some_detail = desc.shapeType I'll raise a bug.

‎03-14-2023

Hi Dan, That works as expected, sorry forgot to type the last bit of code in my example, its when trying to describe a group layer I get a hard crash: arcpy.da.Describe( group_lyr )

‎03-14-2023

Hi, I've encountered an issue in ArcGIS Pro 3, when using arcpy.da.Describe on layers (.lyr/.lyrx) that contain a group layers, it causes a hard crash in ArcGIS Pro 3. If running the same script outside of Pro the script will just terminate. I can't catch the error with try/except either. No issues with layer files containing a single layer. The issue doesn't occur using arcpy.Describe, but that's not as useful as a dictionary. I've modified my code to handle things differently for layers and maps, but thought it worth reporting this error. import arcpy lyr = r"c:\temp\group_layer.lyrx" desc = arcpy.Describe( lyr ) desc.dataElement.name >>> group_layer.lyrx # Hard crash here... desc = arcpy.da.Describe( lyr )

‎02-22-2021

Hi @Anonymous User I also encountered this issue, it seems to be related to the Azure deployment detecting the content of the ESRI experience as being a type of Hugo website and attempting to build it as such. I've opened an issue here to try and resolve that. In the meantime, a quick work around is to place the experience in a subfolder, and include a basic index.html file in the root with a redirect to your app (e.g. Javascript redirect). Redirects work with relative paths so no issues with the Azure urls.

‎06-02-2020

Is there any way to check the available version of Arcade from within an arcade expression (attribute rule)? For example test that $originalFeature is available before trying to use it? (We are using Pro 2.5 but portal 10.7, so different versions of Arcade)

‎05-19-2020

This would enable us to deploy some much more flexible workflows through the web and Collector. Even just the ability to selectively make the geometry on some feature classes within a feature service read only would help.

Online Status	Offline
Date Last Visited	‎11-15-2024 03:13 PM

My Ideas

Latest Contributions by AndyEgleton

Re: Disallow Null Value field in existing data

Re: arcpy.da.Describe on Group Layer causes hard crash on ArcGIS Pro 3

Re: arcpy.da.Describe on Group Layer causes hard crash on ArcGIS Pro 3

Re: arcpy.da.Describe on Group Layer causes hard crash on ArcGIS Pro 3

arcpy.da.Describe on Group Layer causes hard crash on ArcGIS Pro 3

Re: How do I Deploy dev edition Experience as Azure Static Web App?

Check available version of Arcade

Re: Collector on AGOL: Disable editing for geometry but retain addition of related records

Re: arcpy.da.Describe on Group Layer causes hard c...

Re: Collector on AGOL: Disable editing for geometr...