ArcPro not honoring selection for attribute statistics

[ChristopherJStrong]

All I'm trying to do is get a total value for the Shape.STLength() field for a feature class. I've selected the records I care about, but when I right click on the field and choose statistics, I get the statistics for all records. The attribute table is only showing selected records, and the only filter option is by extent.

What am I missing here?  This should be very simple (and it is in ArcMap, which I am seriously wishing I could just use forever).

Screenshot attached. 

[Robert_LeClair]

@AZendel - so I looked into this briefly and what I've learned is the BUG-000153835 is currently under review by the ArcGIS Pro Dev Team and that the workaround I provided 1/30/23 worked for ArcGIS Pro 3.0.x but no longer works for ArcGIS Pro 3.1.x.  Now the BUG is for SQL Server 2019 rather than Oracle.  I do not have the ability to create a new bug for Oracle and/or add it to the current bug as I work in Training Services but I do recommend you contact Esri Support Services with this report so they're aware of it in this RDMBS too.  Thx!

[Anonymous User]

Still seeing this bug in Pro 3.1.1 and SQL Server sde geodatabase. I'm reaching out to tech support.

[Anonymous User]

Added my case to -

• The statistics field not honoring the selection is a BUG-000153835 that can be reproduced when you try to work with data sources from a SQL Enterprise geodatabase

[CurtisTyler]

There is this thread from 2022 that discusses this issue and within the "solution" it is stated that apparently it's part of a "performance enhancement" introduced in 3.0. The documentation referenced in the linked thread is here.

[alex_friant]

Wow, you're right. There it is right there.

They should add a tool tip when you hover over those options that state this so users aren't thinking it's buggy behavior.

[DanHaasken]

One of our ArcGIS Pro users just reported this issue to me as well and this thread helped me figure it out in less than 5 minutes so thank you all for that. We're using ArcGIS Pro 3.1.4 and it has not yet been fixed in that version. Hard to believe that this would be that difficult of a fix!?

[Robert_LeClair]

So I checked on BUG-000153835 and it's been fixed starting at ArcGIS 3.2.