Pop-up Listing All Features in Selection Layer

[Jason_Celeste]

Working in Pro version 3.3.1. When I identify a feature in a selection layer with the explore tool, it lists all features in the selection layer in the top of the pop-up and displays only the top feature no matter which feature you click on. If I turn the selection layer off and ID the same feature in the source layer, the pop-up displays only the feature I clicked on (like it should). A colleague also running 3.3.1 is experiencing the same behavior. I opened the same project on a different computer running 3.2.2 and the pop-up will only display the feature clicked on in the selection layer (like it should). 

My settings are the same on both computers. 

[CodyPatterson]

Hey @Jason_Celeste 

I have version 3.3.1 as well and I am not experiencing the same issue oddly. When I click on a feature that is stacked with another of the same layer, multiple will pop up, but I'm not sure if that's what you're describing. I was curious if your explore settings may be different than mine?

I was wondering if you could check these settings here to see if this may fix your issue.

Cody

[Jason_Celeste]

@CodyPatterson Thanks for the insight. Not quite the same issue I'm having. I'm not stacking any layers. I'm trying to id one feature at a time in a layer I created from selected features in another layer. See video. 

[Robert_LeClair]

This is BUG-000168426 - "In ArcGIS Pro 3.3, when a feature in a (temporary) layer made up of selected features (created by first making a selection of features on a feature layer using Select By Attributes, right-clicking the layer and then clicking Selection and Make Layer From Selected Features) is selected by the Explore tool (by left-click), the corresponding pop-out shows attributes for all the features within the layer and not just for the selected feature."

It's currently under review by tech support.

[BreeMcMurray]

ok, so, it's been 5 months--is there a fix for this or a work around/another way to create that selection layer and get it to act right?  I've been using ArcPro 3.3 for several months and just about 1 month ago this issue popped up (did not happen before that-maybe with an update).  

[Robert_LeClair]

Hi @BreeMcMurray - I took a look at this status page for BUG-000168426 for ArcGIS Pro and it's still currently in review by the ArcGIS Pro Development Team.  I wish I had a better answer for you.

[BreeMcMurray]

I've been trying to update the solution since i posted the question yesterday--i figured it out (with some help) :

from Aug 2024-unresolved issue (multiple users)

I/we figured it out!  A power user in my agency had me try several ways of creating that selection layer and this is what works for me with this issue (he explained a lot about geodatabases that i don't understand, but this seems to work).  I am running 3.3.1, but this was also happening in 3.4 (i had to back track since my agency doesn't support 3.4 currently): 

use the ArcPro 2nd option listed here: Using the Export Data tool  

 How To: Create a New Layer Based on Selected Features 

MODIFICATION of step 4. (ArcPro): In the Export Features- Parameters Box, select input layer, toggle the "use filtered records" button [under input line], and in the 'Filter' drop down menu you can select features. 

EXPLANATION of step 5. (ArcPro), "select output location"-this defaults to a Project Database--i think the database has to be part of your project, not just a selection without a database. 

When i did this, and i use the explore tool to 'identify' a single record/feature in the selection layer, only a single record popped-up (as it should). 

[VenturiRenewable]

An alternative to creating a new layer is to select the original layer in the contents list but not have it visible and then do the identify based on this layer rather than the selected features layer. Not perfect but is a work around while they fix this bug.

[AlexandraTowne]

I'm also having this issue, still. I'm glad to have found an explanation, hopefully it will be resolved in the next update. 

[Robert_LeClair]

@AlexandraTowne - in reviewing this bug, I do see it is fixed in the upcoming ArcGIS Pro 3.6 release later this year.