FeatureLayer not using unique value symbol from the REST service

[KevinSchumm]

I have several feature layers that are pointing to layers that have symbols that change based on unique values. The layers only use the default symbol for the feature and seem to be ignoring the attribute that defines what symbol to use.

This is working correctly in ArcMap, and I can see the renderer information coming through the REST service, but the symbol is always the default symbol. I've tried setting the unique attribute as an "out field" on the feature layer, to no avail.

We're using ArcGIS Server 10.

Any suggestions for making the symbols show up based on the unique values I've specified, apart from just manually creating a unique value renderer for each layer?  It seems like it should be able to get the correct symbol from the REST service.

Let me know if you need more clarification. Thanks.

[JenniferNery]

Please check that the attribute used by your renderer match a field name in the layer. It may be because the attribute and field name do not match. This is case-sensitive. Also check that the expected values for each attribute match the renderer expected values (including their type). If the renderer does not find a matching attribute/value pair, it will use the default symbol.

[KevinSchumm]

Jennifer,

I noticed something this evening that I feel might be a bug in either ArcMap 10 or ArcGIS Server 10.

To change the symbology based on a field, we're using a field called SUBTYPECD. The alias for this field was set to SubTypeCD. While experimenting with fixing this issue I was having, I changed the alias to be SUBTYPECD and clicked the publish button in ArcMap and agreed to overwrite the current service in ArcGIS Server. When I view the service in a browser, the field for the unique value renderer is still SubtypeCD, rather than the SUBTYPECD that I specified. I clear my cache. I restart IIS. I even go as far as deleting the service and recreating it with the MXD. All with no luck.

Through further investigation, I've noticed that if I change the symbology in ArcMap to use something other than "unique value", publish the service, then change it back to unique value, and republish, then everything is working fine. The JSON for the service is fixed and is using SUBTYPECD like I specified.

The problem though is that when you change the symbology in ArcMap to something other than "unique value" and then change it back, it wipes out the symbology you specified before. I REALLY don't want to redo all my symbols to get this fixed.

Do you have any suggestions for me? Is this a bug or am I just missing something?

[dotMorten_esri]

The behavior you are is seeing is expected. If the alias is updated in the geodatabase, then the fields shown in the
UVR symbology doesn�??t show the updated field name unless the UVR symbol is reapplied based on the updated field name.