Filter by Extent does not work correctly when data frame is rotated.

[Wayne_Rennick]

I have a map frame that I've rotated and when I view the attribute table of a layer and select the "Filter by Extent" it doesn't show all the features that are visible in the data view. It seems to only show those in the middle of the view (the map view is rectangular so the features on either side are not showing in the attribute table). If I remove the rotation of the data frame, the features that are displayed in the view match the ones in the table.

It's pretty obvious that Pro isn't using the extent of the rotated data frame correctly. This tool is really useful when examining data but fails when the frame is rotated. 

I'm using 3.3




Filter data in the table—ArcGIS Pro | Documentation

[Robert_LeClair]

I tested this on ArcGIS Pro 3.4 and am seeing the same thing.  Definitely a BUG in my opinion.  My guess is the spatial extent remains at 0 to 90 degrees and does not rotate with the map view.  Thus the attribute table is not filtering as expected.  I rotated my Map View 90 degrees and zoomed to full extent.  Staying at the same extent, I panned in different directions keeping ALL of the points in the map extent at the same scale.  The attribute table kept on coming back with different numbers instead of ALL of the points.  I would suggest contacting Esri Support Services and log this as a BUG.

[Wayne_Rennick]

Thanks for the feedback. That was my experience too.

[Wayne_Rennick]

Can you raise this as a bug?

[Robert_LeClair]

My recommendation is you contact Esri Support Services to log an ArcGIS bug following the information provided here in the How to document.  I work in Esri Training Services not on the ArcGIS Pro team.

[Wayne_Rennick]

Only one person in an organization get's to contact ESRI. So if your not that person it can be difficult to get a bug submitted.
But you work for ESRI. So it should be easy to submit a bug and maybe even get a reward for finding them.

[Robert_LeClair]

@Wayne_Rennick  - I'm tagging @KoryKramer on the ArcGIS Pro team to raise awareness of this potential bug.

[KoryKramer]

We'll look into this.