Unique value counts won't refresh correctly after changing layer's data source

[BrettGoodwin]

First off, I'm happy to see the ability to sort by value count in the symbology pane for a layer in Pro.  Unfortunately, after changing the data source for a layer, the value counts don't refresh properly and sorting by count stops working. Value counts that should now be zero are denoted with a question mark, but because the sorting option doesn't work I still have to manually select these values to remove them.

The picture below shows some of the resulting values after changing data sources, refreshing the count, and then sorting by count ascending.

[DanielMatranga]

Basically what you have found seems to be a #bug to me

That being said, I would try adding the new data source fresh, as in click Add Data > browse to the layer you want to add. Next, I would re-symbolize based on values.

When using Pro, if I try to change the data source without adding it again like I mentioned above, Pro usually just crashes and exits without warning. So do save often.

[BrettGoodwin]

Daniel, I agree that this seems like a bug.

Unfortunately re-symbolizing after adding a new layer will change the color/value assignments that I'm trying to maintain across numerous layers. 

[DanPatterson_Retired]

save to a layer file, if you need to maintain symbology

[BrettGoodwin]

I'll still have the same issue as the original post, value counts won't refresh correctly.

[JeremyWright]

Brett,

Please report this issue to Esri Support, so they can get this assigned to the appropriate dev team.

regards,

Jeremy W.

[RichardHowe]

This bug still persists in 2.2 as far as I can tell. Why is their even the functionality for Pro to display a question mark in the count? It is surely an explicit numeric value! Either it is present or not?!

[BrettGoodwin]

Yep, the bug is still there. I spoke with ESRI at the last UC and then opened a case regarding the "?"s. They identified it as a bug, so hopefully we'll see it fixed soon! 

[RichardHowe]

Brett, good to hear that they're addressing it. Nice work!

[BrettGoodwin]

Good news, as of Pro 2.3.1 this bug has been fixed. You can symbolize a layer by a unique value, change the data source or add a definition query to the layer, update the value counts to show the new counts, and sort them ascending or descending.