Latest Contributions by David_Lindsey

Only in Python, the SQL tables were showing the correct (positive) numbers.  I suspect you'll have better luck with Esri Support because you are on supported versions of everything and still seeing the behavior. I've tracked down your post and am now following it ... View more

@JamesMorrison1- Unfortunately not yet. I worked with Esri on this for a couple of weeks, but I ended up needing to close the ticket. Our agency is a wee bit behind on modernization, lots of really old enterprise database versions on Enterprise 10.8.1 while trying to use modern versions of Pro and its scripting libraries. Esri had us test things by upgrading our enterprise databases from 10.8.1 to 11.2. That didn't solve it. Esri then advised us to upgrade our Enterprise installation and test again. Ha! Like that's something we can do on a whim. That's the roadblock right now. We can't try that until our Data Admin is ready (hopefully later this year). Esri couldn't rule out a compatability issue between Enterprise 10.8.1 and Pro 3.2, but also couldn't rule out some sort of database corruption in the tables since it's only occuring with one database. The fact that I'm getting different results on different versions of Windows Server is a red flag to me as well. Esri didn't have an answer to that. I plan to upgrade to Pro 3.3 today or early next week and will test again. Based on my previous research, it does seem like a bug introduced at Pro 3.2, but maybe that's because Esri is inching the database support further and further from our setup. I'm not sure. Thankfully, the State IDs are working for our needs (as in, the database's versions' State IDs will match when all versions are properly Reconciled and Posted...they'll just show a negative number). What is the setup like on your side? Database version? Enterprise version? My apologies for not being more helpful with news! ... View more

Following up on my own comment: featureLayer.SetDataConnection() will refresh the data connection, refresh the attributes, and refresh the renderer within Pro if already open. If I set the featureLayer's data connection to itself, it refreshes and updates. Here's my template example currently in use, if anybody needs a starting point on this. My script is doing some QC checks, then outputting the error features into an error feature class within the Pro project's default file geodatabase. I then refresh the default geodatabase before isolating the specific feature layer that's open within Pro to have the data connection reset.   // For each item in the file geodatabase... foreach (Item gdb in Project.Current.GetGeodatabases().GetItems()) { // If the project's database path matches the expected default database path... if (gdb.Path == Project.Current.DefaultGeodatabasePath) { // Refreshes the File GDB (it won't auto-refresh within open Pro project) gdb.Refresh(); } } // Create a new map view of the active map in Pro. MapView mapView = MapView.Active; // Check if the map view is valid (i.e. a map is open) if (mapView != null && mapView.Map != null) { // For each layer in the map... foreach (Layer layer in mapView.Map.Layers) { // Check if the layer is a feature layer... if (layer is FeatureLayer featureLayer) { // If the feature layer's underlying feature class path matches the error feature class path... if (System.IO.Path.GetFullPath(featureLayer.GetFeatureClass().GetPath().AbsolutePath) == System.IO.Path.GetFullPath(Project.Current.DefaultGeodatabasePath + "\\" + fc_errors_name)) { // Refresh the feature layer (attributes and renderer) by resetting the data connection to itself again. featureLayer.SetDataConnection((CIMStandardDataConnection)featureLayer.GetDataConnection()); //mapView.Redraw(true); // Redraw disabled. It will update the attribute table, but will not update the feature layer's renderer (as of Pro 3.2.2) } } } }     ... View more

@ChrisUnderwood- Thanks for the info! Unfortunately we don't have access to most of our end-user's SQL Server (nor do most of the end-users for that matter) to find that information. However, we had one of our end user's try accessing the same SDE from ArcMap instead of Pro. The GDB version displayed there, so it is looking more and more like an incompatibility with Pro. One of our end-user's ended up having a 10.6.1 database 😵 . Pro 3.2.x could not recognize that version number: This is why we're auditing our end-users though, to find hidden gems like this that need to be upgraded...🙃 ... View more

@RobertCao- Thanks for providing this. Do you know if that same issue could be impacting other topology-related operations? For example, I'm using the Align Edge tool with a map topology and a sliver gap is getting introduced where there is literally no possibility of one getting generated by the end-user (I've tested this is Pro 3.2.x and now 3.3.0 with the same effect). If you don't have additional info, I am likely going to submit this to Esri Support as an additional bug.   ... View more

I know this is an old thread, but I wanted to attach this thread I posted as it may be related to this issue. The generic Align Edge Failed message appears for the following bug below. Since OP mentions that it will work after a second attempt, this sounds like the issues we have been experiencing too. I hope this helps, for anyone else stumbling across this thread. Defect ID: BUG-000167028 Synopsis: The Align Edge tool fails when features are highlighted outside of the designated snapping tolerance in ArcGIS Pro in contrast to ArcMap where the tool is unaffected by the snapping tolerance. ... View more

So a database in SQL Server is not called a file geodatabase. It's called an enterprise geodatabase. You need to start with the correct tool and go from there (documentation). arcpy.management.CreateEnterpriseGeodatabase()   ... View more

@GavinMcDade- What's your environment setup like? We primarily execute on virtual environments using Windows Server 2016 and 2022. Finally decommissioned Windows Server 2012 because too many oddities were occurring once support got dropped. For troubleshooting, have you already incorporated PAUSE into any of the .bat files (temporarily) to see if any Command Prompt specific messages are being generated for you before the window closes? Sometimes that has helped me diagnose if those .bat files are even being reached during a workflow. ... View more

Update: After talking with Esri Support about this issue, it's been determined to be a bug. Here's the information for anyone who wants to follow the progress: Defect ID: BUG-000167028 Synopsis: The Align Edge tool fails when features are highlighted outside of the designated snapping tolerance in ArcGIS Pro in contrast to ArcMap where the tool is unaffected by the snapping tolerance. ... View more

Late to the party, but I agree, this seems like a great thing to have. I don't like that I am at risk of editing feature layers that I have zero desire to edit. ... View more

"I have already changed the bat file to use propy.bat, but the python scripts still get randomly skipped." This has been an issue for a long time with ArcGIS Pro's python.exe and propy.bat, at least for me. Call the pythonw.exe file instead and you should be okay. It's stable. python.exe and propy.bat will fail to launch my scripts 60-80 percent of the time. I have had zero issues with calling pythonw.exe though. It's been my workaround for a few years now. Edit: Just know that pythonw.exe will hide the Command Prompt window. So if you need user interaction with that window or will rely on output messages within it, you'll have problems with this approach. More info here. ... View more

I am super late to this conversation, but was struggling with the same issue at Pro 3.2.2. Adding this comment here for any future viewers who may need help with this also. The MapView.Active.Redraw(true) fails to update my feature layer's renderer within the map. After some digging around, I found this. I tried the mentioned workaround where I simply re-set the feature layer's data connection back to itself, and my feature layers are now properly redrawing as I would expect.   featureLayer.SetDataConnection((CIMStandardDataConnection)featureLayer.GetDataConnection());     .Redraw() appears to be updating the attribute table correctly, just not the renderer. I'm not sure why that is the case, but using .SetDataConnection() method in tandem with .GetDataConnection() is performing both successfully. ... View more