Latest Contributions by DrewFlater

@Jeff-Reinhart only a subset of options are available in the Pro admin settings system, not including the option referenced above. Yes a new ArcGIS Pro Idea would be suitable in this case, and we should be able to prioritize it in the near term with your justification of how your organization will benefit from applying (and potentially locking) that option at the admin level (across many analyst machines for the org). Some of the options are quite logical why an admin would want to set it, but opening the messages seems like something more suitable to the individual user's preference. But I look forward to discussing that further in the new Idea 🙂 ... View more

@HaydeeHY This enhancement Idea is in the development team's Near Term backlog. A new tool for KML conversion, KML To Geodatabase, will be released in ArcGIS Pro 3.6 for enhanced attribute handling. Any enhancements like this one that were logged for KML To Layer will only be developed for the new tool going forward.  ... View more

@RTPL_AU @paleo78 just to reinforce, this is not normal behavior and is a bug. This documentation is being added in Pro 3.6 to the Find a geoprocessing tool topic: "The first time you access a tool or any interface that uses geoprocessing, the geoprocessing cache is automatically created. The cache is used by search and is created once per software release. Creating the geoprocessing cache typically completes in a few seconds on a machine that meets the ArcGIS Pro system requirements. If you have a language pack or Semantic Search installed, creating the cache may take longer, but it should still finish within one minute." I am going to explore the impact of Xtools on cache creation. If they are injecting additional system and custom project tools, that will increase the time, and if it is failing in some way to generate a full cache, that may be attempted repeatedly for each Pro session. ... View more

@RTPL_AU @paleo78 What is described is a defect, as the Geoprocessing Cache is meant to be generated once per release (updating from Pro 3.5 to 3.6 for example), NOT each time you start Pro. The amount of time is also quite high and should complete in a few seconds under normal conditions with a system that matches requirements. Please report a BUG with Esri Support to describe your situation and debug the problem. https://support.esri.com/en-us/knowledge-base/log-an-arcgis-bug-000034294 A few pieces of information I am curious about that will also help in your communication with Esri Support, 1. Do you have ArcGIS Pro language packs installed?  2. When installing Pro, do you set the Optional Features to install the feature AI Models>Semantic Search? When semantic search is installed, additional caching needs to happen which impacts cache generation performance. Semantic search also has system requirements for a CPU that supports the AVX2 instruction set. https://pro.arcgis.com/en/pro-app/latest/get-started/arcgis-pro-system-requirements.htm#:~:text=A%20processor%20supporting%20the%20AVX2%20instruction%20set .  3. Do you install ArcGIS Pro per user or per machine? Related to this, the geoprocessing cache is generated in the folder C:\Users\<username>\AppData\Local\ESRI\Local Caches. You can delete the g*.cache files in this folder and restart Pro. Confirm the generation of g0, g1, g3, g4 files after you restart Pro. You could try renaming the whole ESRI folder and restart Pro to see if the problem is related to user profile files previously created. The ESRI folder will be recreated on restart.  4. Do you have a custom cloned Python environment activated? Can you import arcpy in the Python window?  ... View more

@swiss_parks_network_nbernhard Hi The export dialog will only be used for exporting the selection set produced by the tool, not "all data".  ... View more

An Export Selection button is added to the Select By Attributes and Select By Location dialogs in the Pro 3.6 Beta. This button enables after using the Apply button to perform the selection. Clicking Export Selection opens a content browser window to define the location where the selected records should be written to a new feature class/table.   ... View more

We cannot change default behaviors of geoprocessing tools and parameters from release to release. A script that didn't explicitly define the output path would create an xls in previous releases, and while many people might prefer the modern xlsx format, we can't change the default output since someone might be counting on continuing to output xls. Cross release compatibility for every tool and parameter is critical to maintain. ... View more

Geoprocessing environments provide an output coordinate system that many geoprocessing tools will honor and use as default.  You can also specify tool parameter overrides if there is a specific coordinate system you want to be the default every time you open Project or other tools. https://www.esri.com/arcgis-blog/products/arcgis-pro/analytics/tool-parameter-overrides-in-arcgis-pro-3-3 ... View more

Notification sounds are available in ArcGIS Pro 3.5. https://pro.arcgis.com/en/pro-app/latest/get-started/user-interface-options.htm#ESRI_SECTION1_6FAA3128F0664D92817715A462FF30AE ... View more

@wayfaringrob an easter egg for an Honored Contributor: you can hold down right-shift keyboard key when clicking to open a tool, and it will open the floating tool dialog box. Running the tool in this mode also uses the foreground thread execution with blocking progress dialog, similar to ArcMap.  @SH_DH we received more feedback than the 2 kudos above that it was desired for the back button to return to the previous active pane used to open the tool. But based on your feedback we may need an option for the user to choose which behavior they prefer. Since this is the implemented idea related to navigating back to the previous non-Geoprocessing pane, it would be good for you to make a new ArcGIS Pro Idea about this option to change the behavior.  Also consider this: the Geoprocessing pane has a Recent section at the bottom with access to previously run tools, and the little menu will help you see the messages and reopen tools with parameter populated that were used previously. Internally I call this the Geoprocessing pane mini-history.    Also, rather than switching to the Catalog pane to access project toolboxes/tools, the same toolboxes are available in the Toolboxes tab of the Geoprocessing pane.    The Geoprocessing pane Recent (mini-history) and project Toolboxes were both added to keep you from needing to pane-switch as much, which would both help in the case you use the Back button since it would stay in the Geoprocessing pane.     ... View more

Closing the issue as it will not be implemented as described in the title.  A different idea could be logged with the Geodatabase label for Pro's text file workspace to support a specific column header row.  ... View more