Create new toolbox from Select Default Toolbox dialog

363
4
04-13-2022 02:03 PM
Status: Open
Labels (1)
rburke
by
Frequent Contributor

When setting the default home folder, geodatabase, and toolbox on a project, it's possible to create a new folder and geodatabase from the dialogs launched by the appropriate options, but not toolboxes.

Currently, it goes:

  1. cancel out
  2. save your options
  3. close the backstage
  4. find catalog view
  5. open catalog view
  6. navigate to the desired location
  7. create the toolbox
  8. close catalog view
  9. reopen the backstage
  10. reopen options
  11. launch the Select Default Toolbox box
  12. re-navigate to the new toolbox
  13. select it and try to save
  14. receive a 'The default toolbox does not exist' error (starting a support case on that now)
  15. cancel and close the application
  16. reopen the project
  17. reopen the backstage
  18. reopen options
  19. relaunch the Select Default Toolbox box
  20. re-navigate to the new toolbox
  21. select it and save.

Update: The error in step 14 cannot be resolved by restarting the application.

My proposed workflow:

  1. navigate to the desired location
  2. create the toolbox and save.

It would be even better if the same context menu available in folders in catalog view/pane were just implemented everywhere for consistency and ease of use.

rburkebsrc_3-1649883571542.png

rburkebsrc_4-1649883663377.png

Tags (1)
4 Comments
JenLangevin

@rburke I'm stuck on step 14 of your list. I have opened and closed ArcPro many times but I still get the "The default toolbox does not exist' error. Have you found a solution for this yet? Many Thanks!

rburke
by

@JenLangevin  you are correct. I had selected something different thinking it was my new one. I am having the same issue you are.

rburke
by

@JenLangevin  this part of it is now logged as BUG-000148962.

KoryKramer

It looks like that error will be resolved in ArcGIS Pro 3.0 when projects' default toolboxes are .atbx anyway. The new toolbox format (atbx) was added in Pro 2.9 to prepare for switching over to them as the default in 3.0. I did a quick test on a development build and do not receive the error described in the bug.