So I have had this project that has a geodatabase along with a toolbox holding quite a few models.
When I left the project done quite a few months ago, everything was running fine. The models all worked as expected and outputs were being added to the geodatabase.
Today, I opened the project to re-run the models again with some new data (data structure is all the same so it's not the data), the model will start and go through the motions and complete successfully, however, when I refresh the geodatabase, the outputs are not there.
The model runs without errors so I'm not sure what has changed.
I was running the project from a onedrive folder on my computer (I use 2 different PCs so it was nice to have access to the latest version) but also moved it to a dedicated hard drive folder and I get the same results.
Hopefully this is a simple fix as I have put many hours creating this project and models as there is a lot of repetitive work to be done and the models help immensely.
Solved! Go to Solution.
I too have found Pro to be a bit stubborn with the caching of the Catalog pane. Usually though, right clicking on the GDB and selecting refresh is enough to make it show any new datasets.
Maybe something else to consider - at the end of your models, include the "Collect Values" tool. Set your output dataset as the input to "Collect Values" and set the output from "Collect Values" as a parameter. When you run your model, it should then add the output dataset/s to your map display automatically.
Doing this may even force the GDB to auto refresh, but I'm not sure.
From
Frequently asked questions—ArcGIS Pro | Documentation
Can I store my ArcGIS Pro project in Microsoft OneDrive or Google Drive?
Storing projects in OneDrive or Google Drive is not supported. See ArcGIS Pro and Cloud Storage Services for more information.
hopefully the original computer has the original project and data structure, try running it without any onedrive linkages
Have you done any software updates in the intervening period? We've found models don't behave the same after updates (sometimes) due to tweaks in the architecture. One thing to check would be to see if any of the outputs have somehow changes to "Intermediate Data" and are getting wiped after the tool is finished. (Tip - run in Edit mode to diagnose this and it won't wipe the intermediate data).
There has been a new version rolled out. This project (models and geodatabase) were done almost 8 months ago and I do notice I have a couple of patches I need to install. I tried recreating the geodatabase from scratch and oddly, some of the models work, while others say they completed successfully, the outputs don't show up in the geodatabase. I'm not sure how to check if delete intermediate data is turned on or is being deleted. I was in edit mode and still didn't work. One thing I did notice was that when I was editing or opened a model, there was a yellow bar across the bottom of the properties dialog saying that the model changes wouldn't take place until it was saved and I clearly saved the model. I am getting IT to install my patches and hopefully this fixes things up - otherwise I'm at a loss.
I did notice that in some of the models that did run, the outputs wouldn't show up in the geodatabase until a few refreshes or even exiting out of the project and going back in. Very odd behavior.
So I updated ArcGIS Pro with the latest patches.
Odd thing is occurring
1. I re-built the model hardwiring the feature classes used in the operations. Again, the model indicates it ran successfully, but when I refresh the geodatabase inside the project, nothing shows up in the Feature Dataset. It isn't until I go to the map, add data, go to the geodatabase and the Feature Data Set and click refresh that the data shows up. I then go back to catalog pane and refresh the geodatabase and it finally shows up. Very odd.
I too have found Pro to be a bit stubborn with the caching of the Catalog pane. Usually though, right clicking on the GDB and selecting refresh is enough to make it show any new datasets.
Maybe something else to consider - at the end of your models, include the "Collect Values" tool. Set your output dataset as the input to "Collect Values" and set the output from "Collect Values" as a parameter. When you run your model, it should then add the output dataset/s to your map display automatically.
Doing this may even force the GDB to auto refresh, but I'm not sure.
The catalog pane is very finicky when trying to update feature datasets from a model. Sometimes it works, sometimes it doesn't.
I realized that even after refreshing the geodatabase a bunch of times to no avail, just dragging the whole feature dataset into the map view will show the results. Definitely a bug IMO.