Select Features on Map to View Attributes on Table

Question

Hi,

Very new to Esri products, I'm sure this is a simple question, thanks for your patience!

I've got a layer of structures that are placed on a map.  I have a standalone table of inspections that were performed on the structures in the first layer.

There is one common shared attribute between the two layers.

I would like to select the structures on the map in order to view the associated inspections.  Is this possible, or would I need to map the inspections themselves onto the map to allow this behaviour?  Thanks,

-loren

abaldenweck@blm.gov_BLM_EGIS · Answer

Yes, this is quite doable.

You want to set up a Relate , then open the structures table, hit the hamburger menu, and select "Select related records"

This will automatically select the row(s) related to your structure.

See this gif below, where I do this with an origin point feature class (tstpt) and destination table (tsttbl), related by the points' ObjectID.

As a bonus, you can also see them in the popup after adding the relate

If you need this on a permanent basis, look into doing a relationship class instead of a relate. They do the same thing, but a relate is temporary and only found in your map, while the relationship class will work in any map without you having to set it up again (you would still need to check "select related records" in each map, though).

D_Atkins · Answer

Others may have a more thorough response for you, but to get you started:

I'm assuming you have your Feature Layer (structures) in the Contents Pane of your Map, and that you've Imported your standalone table (which should also appear in your Contents Pane.

From there, it should be straightforward to use the Spatial Join tools; the output is a new Feature Class with the attributes from both your spatial dataset (structures) and your standalone table for inspections.

Of course, the 'join' operation assumes perfect matches between the two datasets; all manner of things can throw this off (for instance, sometimes numbers are stored 'properly' as Integers in a database, but in a standalone table, a single row with a non-numeric character will cause the table-field to import as a 'Text').

Spatial Join (Analysis)—ArcGIS Pro | Documentation

and for importing a standalone table:
Import data—ArcGIS Pro | Documentation