It was deemed that the issue is not a bug, rather an enhancement request so the bug was marked as a duplicate of the enhancement as shown in your screenshot and here https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEwNDMxNg== [ENH-000135498: Better display of symbol preview or legend when conflicting visuals happens either through visual variables, scale based sizing, or attribute driven symbology.]
The issue has been reviewed by the development team. It has not been prioritized into a release plan and will be monitored to determine its overall impact. Factors that are considered in the prioritization process include the number of users requesting the functionality, business impact, whether an alternative workflow exists, among others.
I hope that explanation helps. Thank you.
I think this is still very much needed.
I was so excited to find this feature, however not being able to carry the attribute-driven symbology over into the legend defeats the whole purpose of having attribute-driven symbology. It fails the cartography 101; have an appropriate legend.
@KoryKramer If this is not currently prioritised by the development team, are you able to advise on workarounds?
Agreed with @Sveouu. This is yet another half-way executed effort by ESRI. Symbology on the map must match symbology in the legend! If there's anyone at ESRI who states otherwise, perhaps they're secretly working for your competitor and actively working against your best interest.
Hi @delongtime As noted below, we have an enhancement request open for this [ENH-000135498: Better display of symbol preview or legend when conflicting visuals happens either through visual variables, scale based sizing, or attribute driven symbology.] While you could call technical support to be added to the request, perhaps an easier thing for you to do would be to submit an idea in the Pro idea exchange that demonstrates the type of attribute-driven symbology you're using in your maps and explains what you would expect to see in the legend given that the symbology can vary per feature. Adding specific examples about the way you're working with attribute-driven symbology and your expectations for what you would like to control and visualize in the Contents pane/legend will be very helpful.
Once you submit the idea, we can associate that with the existing Enhancement Request on the backend so that we're tracking this feedback together.
Thank you for the willingness to provide constructive feedback!