ArcGIS Pro 3.5 seems to use a database that is not the default, nor added to a project, as the destination database for geoprocessing tasks.
If you updated a project with new databases, folders etc, Pro will at times revert to using a removed fgdb as the destination database, even if that destination has never been used in a GP tool inn that project.
As Pro seems to always pick a random location from your past to do something in, this is no surprise. The fact that the destination is not shown in the PG task unless you click on the output FC name, is a pain.
Basic workflow as follows:
- I open Pro with a template project, with an empty fgdb as default (to prevent random temporary bits & pieces all over the place)
- Once open, I add and specify folders & fgdbs to use as default, and remove all other folders/fgdbs.
- I do some work and save the project.
- When re-opened - and you go to execute a new GP task, the orginal template fgdb is shown as destination, not any of the fgdbs added to the project and specifically not the default fgdb.
I've not tested it fully but using a no-template start will see the future project refer to the temporary fgdb Pro created in your tmp folder.
This does not seem to be the behaviour of remembering a previously used destination. It will revert to the wrong fgdb destination when you've never run a GP task in the new project before at all.
Local reseller/support trying tog et their head around it as well.
EDIT:
And to add to this – it will keep using the wrong database even after you’ve run a GP tool multiple times.
I’ve run the pairwise intersect tool multiple times this morning and every time the destination database is the wrong one i.e not any of the databases in the project nor the default one, and not one that I have used a a destination for any task in recent memory.
