Community
Select to view content in your preferred language

Set Default Option for Explore Tool in Pro

981
1
12-21-2017 12:38 PM
Status: Open
Labels (1)
RichardLittlefield
by
Frequent Contributor

In Pro there is the Explore Tool, that you use to identify, pan and zoom, etc. If you click the drop down arrow on the tool under the Map tab there are some options, Topmost layer, Visible layers, Selectable layers, Selected in Contents, and Candidate Pop-up. The default option is the Topmost layer. For me I'd like to have it on either Visible or Selected in Contents as the default option. So I think there should be a setting or preference that you can change this to the option you want for all Pro Projects on start up per user. I have been unable to find a way to do this currently. I'm always changing it to Visible Layers when trying to identify features.

1 Comment
GIS_Weasel
by
‎08-19-2024 02:30 AM

I've just raised this with Esri support on our corporate account, as it seems mad this configuration option isn't in pro.settingsConfig.

Who is being affected by the lack of the requested feature?

We’re deploying Pro to new users who have been on ArcMap for a number of years. The UI will be new to them, and we’d like to preconfigure this as the default selection (I think it’s ‘selected in Contents’) isn’t immediately obvious.

What is the cost of not having the requested feature? What are the number of extra clicks, time wasted, etc?

We’ll probably have to perform a post-install on the user’s machine. We’ve found changing the setting in a project and saving does seem to set this as the default for the next new project, though this feels flimsy and is undocumented.

This will perhaps add another 2-3 minutes per install for our current user base:

  • open Pro with new Map
  • change identify settings
  • save project
  • close Pro
  • reopen Pro with new project
  • check the setting is now ‘visible layers’

What is the scale of the issue? How many people/projects are being affected?

It’s at install time, so every user will need to have this changed, which is silly considering we’re also deploying pro.settingsConfig. Initial install run of 60 users so (60 x 2 minutes) – quite a lot of time lost.

How often does the missing feature affect their workflows? 

If a user doesn’t have this setting, they’ll be confused. We will obviously send it in a ‘howto’ email, but these often get ignored. We’ll likely have support calls to our team if users aren’t seeing the expected identify result, but we expect calls anyway given Pro is new to them.

How do you envision this benefitting other customers?

More configurability is an obvious benefit. I’m asking for this to be included in a global configuration which by definition is reusable, and potentially useful to anybody deploying Pro in this way.