Latest Contributions by David_Lindsey

‎05-26-2025

Something to consider: Feature Class to Feature Class conversion has been deprecated for a while. Esri replaced that with the new Export Features tool an iteration or two before your Pro version. Although legacy tools may still be functional, try the new Export Features tool and see if the behavior improves.

‎04-27-2025

Hey @karthik91 , you might be able to track down the old style quicker by following the directions from this Styles info page. It mentions the following: (Assuming your style hasn't been retired that is.)

‎04-27-2025

(Edit: Comment removed. Correct answer provided by Wolf and Uma)

‎04-21-2025

Unless this is you in the comment section of this Reddit post, you may not be the only one experiencing this issue recently. In my experience with minor releases (and given how much symbology-related stuff that Esri touched with the 3.4 release), I wouldn't rule out a bug being introduced. No mention of deprecations related to your issue in the release notes either. I use aprx.save() with my symbology updates as well, but haven't been doing the same workflows that you are doing. It does look like you are running the code while Pro is open though. Do the edits save correctly if you run the script as a standalone while Pro is closed? That test might help you rule out a lock or read-only issue...maybe. Oh, and be sure to save a copy of your project beforehand if you try anything as a standalone. I learned that lesson the hard way. Ha.

‎04-21-2025

OP, what version of Pro did you upgrade from when you jumped to 3.4.3?

‎04-18-2025

This was my thought as well. Looked like the same output was being overwritten each time. I'm also curious about the indentation of the return, whether it was inside the function's for loop or outside of the for loop. If the counter iterated once then stopped, that return could be triggering a premature exit from the for loop and function after the first pass.

‎04-17-2025

Thanks for that head's up, Mike. I'll test this with my own issues soon. I hadn't considered anti-virus software contributing to that.

‎07-25-2024

Disregard. We sorted it out. Turns out Enterprise 10.9.1 did *not* like our .ags connection file for whatever reason. Maybe it was a legacy .ags file created from an older version of ArcMap...? Anyway, I recreated it within ArcGIS Pro 3.3.1 with refreshed credentials, and now it's functioning again as expected. I hope this is helpful to anyone else who encounters the ValueError issue with the .ags connection string.

‎07-25-2024

@AliciaShyu- Did you ever figure out what triggered this? We finally upgraded one of our servers to 10.9.1 and am getting the same issue as you did back in 2022. Our folder paths and file paths are very generic and non-problematic, so we've ruled that out. Our other server is still on 10.8.1 and is not triggering failures using the same scripts. Something with the upgrade to 10.9.1 has caused a change that we haven't identified yet. Thanks for any insight!

‎06-27-2024

@HannesZiegler- What I believe this original posting is asking for is an ArcPy equivalent to right-clicking a folder or file geodatabase within the Catalog pane and clicking Refresh. In many scenarios, I am not needing to load feature class output as layers into the map, so that RefreshLayer() tool would not apply to those scenarios. Example. If A) I'm actively connected to my Pro project's default file geodatabase (ex: Counties.gdb) through the Catalog pane, and if B) I use a geoprocessing tool within my custom Python toolbox that saves the feature class output to my Pro project's default geodatabase, then C) new output will not appear in that file geodatabase until I manually right-click it and Refresh within the Catalog pane. Does that clear things up? It seems like such a trivial piece of ArcPy functionality, and existed in ArcMap as RefreshCatalog(). We'd assume there'd be a RefreshCatalogPane() or something like that.

‎06-24-2024

Esri kinda sorta breezed over the instructions in Step 2 to change the Target Framework. For anyone else who struggled to find/load the Target framework screen in Step 2, go to your project's Solution Explorer and click the "Properties" wrench. That will populate the Application settings tab where you can change the Target framework.

‎06-19-2024

Update: I'm not seeing anything specific regarding this issue in the Pro 3.3.0 release notes, but our negative number problem resolved itself in Python once we upgraded to 3.3.0.

‎06-19-2024

Update: Try upgrading to Pro 3.3.0 and test again. I'm not seeing anything specific regarding this issue in the release notes, but our negative number problem resolved itself in Python once we upgraded to 3.3.0.

‎06-19-2024

Hey everyone, I'm currently running the minor-release-gauntlet with my Python scripts. I've upgraded to Pro 3.3.0 from Pro 3.2.2 in my testing environment and am executing my Python scripts to ensure I haven't missed anything with deprecations since Python jumped from 3.9 to 3.11. I've come across one scenario where it does appear that a feature has been deprecated, and I'm hoping to get some advice and/or clarification on what I should use instead. In this scenario, my script has been uploading a Vector Tile Package to our ArcGIS Online account for a couple of years without issue. I do this by initiating an AGOL session in Python, then proceeding with agol_session.content.add() to upload the VTPK. Code snippet here: # Attempts to add the VTPK file to AGOL, with parameters set. upload_result = agol_session.content.add( item_properties={"title": vtpk_name, "description": "Description Text", "snippet": "Snippet Text", "tags": "OurAgencyName", "overwrite": True}, data=vtpk_path, owner="OwnerName") The upload is successful in Pro 3.3.0, but I now receive this warning message: Attempting to re-run the script (and overwrite the previously uploaded VTPK) results in a new error: The error makes sense, since 'overwrite' parameter has been deprecated. However, I have been unable to find any details about this deprecation. Confusingly, the current item_properties documentation for content.add() still show 'overwrite' as an option: The overwrite parameter would overwrite the file uploaded to AGOL if the name/file already existed. We liked that feature (sometimes we need to re-run the content.add() workflow more than once a day if a quick replacement is needed for the same VTPK). The naming convention of the VTPK upload has been YYYYMMDD_AgencyName_BasemapAffiliatedName. I could start including HHMMSS to help keep the duplication from occurring, but I'd rather just use a parameter that accomplishes an overwrite if a new one was created. Any thoughts or recommendations? Thanks!

‎06-14-2024

@JamesMorrison1is not alone with this issue. I'm also seeing this behavior (link to my original post showing my example).

Online Status	Offline
Date Last Visited	‎07-22-2025 03:56 PM

My Ideas

Latest Contributions by David_Lindsey

Re: Export feature class from ArcMap (or ArcCatalog) to ArcGIS Pro

Re: Issue with annotation feature style after migrating from arcmap to arcgis pro

Re: Change backstage button

Re: A script that used to work before is now behaving strangely.

Re: A script that used to work before is now behaving strangely.

Re: Help with my code.

Re: Task Scheduler for GIS Tasks - Skipping Python Scripts Called from Bat File

Re: Publish geocode service - Create Geocode SD Draft error

Re: Publish geocode service - Create Geocode SD Draft error

Re: ArcPy RefreshCatalog() function for ArcGIS Pro

Re: Unable to compile 3.2 and earlier projects after upgading to 3.3 SDK

Re: Seeking clarity regarding arcpy.ArcSDESQLExecute() results

Re: arcpy.ArcSDESQLExecute() returns a negative value from SDE.CONPRESS_LOG Table on update Python 2.7 to Python 3.0

Upgraded to ArcGIS Pro 3.3.0 from 3.2.2 - content.add() no longer has an 'overwrite' item property

Re: arcpy.ArcSDESQLExecute() returns a negative value from SDE.CONPRESS_LOG Table on update Python 2.7 to Python 3.0

Re: How to refresh layers on map after updating

Re: Seeking clarity regarding arcpy.ArcSDESQLExecu...

Re: arcpy.ArcSDESQLExecute() returns a negative va...

Re: Seeking clarity regarding arcpy.ArcSDESQLExecu...

Re: How to refresh a layer after adding a new feat...