Latest Contributions by LanceCole

We upgraded to ArcGIS Pro 3.3 to fix several issues that were resolved in the newer version and found another.  We have multiple scripts that download data from ArcGIS Server and Portal sites for processing using FeatureLayer(url).query.  These scripts and services have been in place for some time and working; however, we are receiving error messages on these scripts when run form ArcGIS Pro 3.3. ERROR 001558: Error parsing json file '<filename>.json'. A row with this OID already exists. We have confirmed the source file does not contain duplicate OIDs and the script does work from ArcGIS Pro 3.2. Any suggestions or notable changes between 3.2 and 3.3 that would cause this issue?   from arcgis.features import FeatureLayer url = "https://<FQDN>/server/rest/services/Hosted/<feature>/FeatureServer/0" FeatureLayer(url).query(return_true_curves=False).save("memory", "temp")     ... View more

I am attempting to run Delete Identical on a feature hosted on an enterprise geodatabase and keep receiving the Error 000224: Cannot insert features.  This occurs when running from a standalone Python script and running the tool directly in ArcGIS Pro.  I have tried both a user with appropriate permissions and the geodata owner.  If I export the data to a local GDB everything runs great. Error 000224 is typically related to mismatched field definitions between incoming features and the output feature class. But this tool modifies the existing feature class, so they should be the same. This is similar to the issue reported by @MulfordnSons  in arcpy.DeleteIdentical_management does not delete identicals in ESRI sqlite database. However, this was to have been resolved in ArGIS Pro 3.0.  Currently running ArcGIS Pro 3.2.1, the database is hosted on an MS SQL Server as an 11.2 version enterprise database. Any ideas? I did submit a support ticket, but it will be Monday or Tuesday before they get back to me. ... View more

About three weeks ago, we updated to ArcGIS Enterprise 11.2.  Last weekend, we updated our enterprise database from 10.8 to 11.2.  In ArcGIS Pro 3.2, we are noting issues with all feature classes that utilize a SQL Where clause for labeling based upon the field Shape.STLength().  When labeling is on, hundreds of drawing alerts are produced for any of these features.  The message states that an "Error parsing the WHERE clause. One or more fields could not be found." This has worked without issue since moving to ArcGIS Pro some time ago.  I created a straightforward linear feature on our enterprise database and drew a handful of lines.  Once I set a SQL Where clause to use the Shape.STLength() field drawing alerts began to appear.  We typically use this field to label features differently based upon the length.  Any ideas? The data is accessed directly to the database using an SDE connection string and the systems are using Microsoft ODBC Driver v18.3.1.1.     ... View more