ArcGIS Pro Contents panel and Layout Legend not Displaying Layer Symbology correctly

Question

Good day

I am busy experimenting on layer symbology in preparation for future work requests. For this experiment i have added point data, displayed using the Circle 6 Symbol. I then successfully updated the displayed symbology using linked symbol property connections (Attribute driven symbology) for the point data layer, allowing me to display 2 different attributes of my point layer file.

However, i have an issue, while the data displays on the map correctly, the layer symbology in the contents panel, Symbology Panel and in the Legend in the layout, does not reflect the correct symbology (see below). Any advice or assistance on how i might correct this would be greatly appreciated.

DanPatterson · Answer

Is your csv converted to a locally stored geodatabase table?

Dont' rely on the csv, make sure it is a gdb table first

Eugene_Adkins · Answer

One other idea, if possible, is to try creating a join between the data and table once the table is added, and then adjusting your symbology based on the joined fields. I know this possibly defeats the idea of linked symbology, but it could create a clear distinction in behavior in case something buggy is going on.

I’m not in front of my computer to attempt your workflow; it’ll be several hours before I get a chance to do so.

Eugene_Adkins · Answer

Ok. Maybe it has to do with your symbology settings being driven by an outside table? If that’s the process you’re using, that is.

Perhaps try to add the table to your map (which you may have already done). Also you may want to provide the version of Pro you’re using incase someone else chimes in.

One other obvious test is, if you’re using a table to generate the symbology, if possible try to generate the symbology using the unique values option based on the actual fields of the data in the map. This could create a clear distinction between the symbology behavior of one option versus the other. Not an ideal resolution if different results happen, but at least it’s a part of reliable troubleshooting.