Latest Contributions by ShaunWalbridge

This issue is addressed for toolboxes in Pro 3.2, if you're on 3.2 and seeing this behavior, please provide details on it. ... View more

@FakeName I took a look at this, and I think I've identified what the issue is. If you have any existing resources open that reference the environment directory, it will currently cause a failure. So for example, if you have a command line prompt at the working directory of the environment, that will lock the location and Windows won't be able to delete the folder. There is a second bug which is that the restore doesn't happen in this case either. I have local fixes for these issues and will look to get them into software, for now, here's a workaround: 1. Your environment doesn't get deleted, it is archived first. If you navigate to %LOCALAPPDATA%\Esri\conda\envs, you should see a file called <env name>.tar.bz2. This is a conda-pack archive of your environment, you can extract it with current builds of Windows 11, 7-zip or by using conda pack to restore your old environment from Pro 3.1. 2. Once you have that in hand, from the Package Manager interface of Pro you can add the environment back to the environment list. If you do this, then ensure that no other resources are referencing that environment, the upgrade should work as expected. Sorry for the trouble and will look to fix this soon. Cheers, Shaun ... View more

Based on your description, you should be able to use Symmetrical Difference to remove the updated lines, then merge together this new feature class with the output from the unspilt operation. ... View more

Since this was logged a decade ago, significant work has gone into the help. For many tools, detailed examples are now available, and if you find the examples provided on a particular tool lacking, please provide feedback from within the help system by filling out this form: That feedback goes to the relevant authors and is regularly reviewed. In addition to the improvements in the help itself, since this issue was logged there have been a number of improvements to how code can be generated from tools. For example, if you run a tool and visit the history pane, you can now export the results to many places, including Copy Python Command which will generate a fully formatted snippet of code for that tool and its expanded parameters as they map from the UI into Python. You can also drag and drop those entries into the Python Window or Notebooks to further make moving between the UI experience and Python as simple as possible. If you have specific topics you'd like to see improved, please use the feedback system. If you still believe there are broader systematic issues, please log a new idea which refines this one to specifics we can assess. Thank you for your contribution to the ArcGIS Ideas site! Cheers, Shaun     ... View more

The updated arcpy package has completed its testing and is now available by running `conda install arcpy=3.1` from an affected environment. We will get this into the next available Pro 3.1 patch. ... View more

Thanks for the report, this was overlooked in the patch installation, as cloning will follow the conda metadata and ignore local changes to the files registered against conda. There are a couple of things you can do until this is patched more completely: 1. Locate the <arcgispro-py3>\Lib\site-packages\arcgisscripting\_arcgisscripting.pyd file from the default environment, and copy that into your custom environment. 2. We are currently testing a custom package to also address this. You can install it by first activating your custom environment, then running `conda install esri/label/prerelease::arcpy=3.1`. If the testing on this package looks good, we will promote it and the command will simplify to `conda upgrade arcpy`. ... View more

Are you working with the default arcgispro-py3 environment or a custom environment? Can you open notebooks from a Python Command Prompt session by running `jupyter notebook .` successfully? Unfortunately, there is a variety of possible causes, and these steps will help eliminate some possibilities. ... View more

Thank you for your idea! Broadly speaking, the FieldInfo object isn't as heavily used as some other approaches to achieve this goal. We recommend using arcpy.AlterAliasName on the resulting dataset in order to make the requested change.  This is not as elegant as your suggestion, but it should be effective. ... View more

Thank you for your idea! It is almost exactly a decade old, and I'm sorry we weren't able to address it within the product lifecycle of ArcMap. In ArcGIS Pro, the favorite experience has been entirely redesigned, as discussed in the geoprocessing customization documentation. We support both per-project and always present favorites, and the favorites panel can include folders which expand to include their elements, including toolboxes: If this is insufficient for your needs, please let us know what you'd like to see within the Pro context to further improve your ability to customize the product. ... View more

In ArcGIS Pro, Attribute Rules fill the role previously requiring Attribute Assistant as @KoryKramer mentioned. These can be modified via Python by using the related Geoprocessing tools in a script, by using data reviewer, or by using the newer Arcade support. If there are specific gaps in implementation for attribute rules that you'd like to see addressed, please log an enhancement request, or create a new idea depending on what you think is currently missing. Thanks! ... View more

Are you working with the default arcgispro-py3 environment or a custom environment? Can you open notebooks from a Python Command Prompt session by running `jupyter notebook .` successfully? ... View more

ArcMap has entered mature support and will no longer be receiving new feature development. As Kory mentioned, this can be accomplished by using the CIM access in ArcGIS Pro, and hopefully your current pop-up development needs are solved by the work we've done in the past nine years. If not, please create an issue to describe the specific features in Pro you'd like to see implemented. Thanks! Shaun ... View more

Given where ArcMap and Publisher are within their lifecycles, this issue doesn't look like one we can address directly. VB never quite did disappear however, so it should be possible to continue using the existing solutions based on that for some time. Thanks for your contribution and look forward to your future ideas. Cheers, Shaun ... View more

In ArcGIS Pro, Attribute Rules fill the role previously requiring Attribute Assistant as @KoryKramer previously mentioned. These can be modified via Python by using the related Geoprocessing tools in a script, by using data reviewer, or by using the newer Arcade support. If there are specific gaps in implementation for attribute rules that you'd like to see addressed, please log an enhancement request, or create a new idea depending on what you think is currently missing. Thanks for your time, Shaun ... View more