With in ArcMap in the Search window (panel) you have the capability to connect to databases and folders to also search those. This functionality is super handy, not only for people who may not know the database well but in other scenarios too. For instance, I have connect to a folder where we store all our georeferenced asbuilts. Each asbuilt has an image ID in it's file name so I can use the Search window to search on that image ID (that I get from identifying a feature) and immediately pull it into my map. I love this functionality.
Does Pro have anything like this? You can search within a Project but even when I have a connection to the database and a folder connection to certain folders, the search only seems to return maps and layouts. Am I missing something?
Accepted Solutions
Heather, your image looks like your connection is to an enterprise geodatabase. The contents of enterprise geodatabases aren't indexed by default in ArcGIS Pro. To enable indexing, go to the Settings page (click Project tab in a project), click Options on the left, and click the Indexing option. In the Options dialog box, uncheck the box that says Skip enterprise database connections. Same thing for network folders--except you have to check the box to index them. Index project items
It works for me in the Catalog pane (ArcGIS Pro), even for folders that are not added as folder connection.
It won't search for folders, though. You need to use Windows Explorer for that. But the files that ArcGIS Pro can read/detect, it should display.
Heather, your image looks like your connection is to an enterprise geodatabase. The contents of enterprise geodatabases aren't indexed by default in ArcGIS Pro. To enable indexing, go to the Settings page (click Project tab in a project), click Options on the left, and click the Indexing option. In the Options dialog box, uncheck the box that says Skip enterprise database connections. Same thing for network folders--except you have to check the box to index them. Index project items
Hi Mark, sorry I didn't see this till now. To index the enterprise gdb, you have to do three things:
- Check the indexing box for enterprise geodatabases. (You did this.)
- Check the indexing box for the location where the egdb connection file is located--which could be either a local disk or a network drive. (You did this since you checked all three boxes.)
- Add the enterprise geodatabase that you want to index to a project. For instance:
I think the reason for that last requirement is to make sure you only indexing enterprise geodatabases that you really want to index--because you might have some connection files hanging around to egdbs that you never use and it's time consuming to indexing them. I don't think this requirement is documented currently, which is a real pitfall, but it will be documented at version 3.6. Anyway, I'm not sure this is the solution--there might be some other cause like the indexer running out of memory--but give it a try. I'm going to be out for a couple of weeks, but I'll forward this thread to some other people here to keep an eye on.
