FeatureLayer doesn't honor RendererTakesPrecedence

[HemingZhu]

I have the FeatureLayer from the Map service. We are using UniqueValue Render on one of field. It is a polygon Feature class. In the REST service endpoint, It stated clearly the UniqueValue Render is used. I also explicitly stated using FeatureLayer.RendererTakesPrecedence=true; However on the may, it displayed using default symbols with one color accross the board.

I had this issue before. FeatureLayer.RendererTakesPrecedence=true did the trick. But this, It doesn't work. Any ideas will be highly appreciated!

[DominiqueBroux]

I have the FeatureLayer from the Map service. We are using UniqueValue Render on one of field. It is a polygon Feature class. In the REST service endpoint, It stated clearly the UniqueValue Render is used. I also explicitly stated using FeatureLayer.RendererTakesPrecedence=true; However on the may, it displayed using default symbols with one color accross the board.

I had this issue before. FeatureLayer.RendererTakesPrecedence=true did the trick. But this, It doesn't work. Any ideas will be highly appreciated!

May be because you don't grab the fields the unique renderer is based on. Try with OutFields="*" or be sure all unqiue value renderer fileds are included in OutFields.

[HemingZhu]

May be because you don't grab the fields the unique renderer is based on. Try with OutFields="*" or be sure all unqiue value renderer fileds are included in OutFields.

Sorry that is not the case here. I have setup  the OutFields. using the following code

ESRI.ArcGIS.Client.Tasks.OutFields outFields = new ESRI.ArcGIS.Client.Tasks.OutFields();
outFields.Add("*");
projectLayer.OutFields = outFields;

But You have a good point. Actually we caught this isues before by including all the fields. But this is not the case unfortunatley.

Thanks for your help anyway!

[DominiqueBroux]

Humm strange!

If you could share a repro case, that would be very helpful.

Thanks

[HemingZhu]

Humm strange!

If you could share a repro case, that would be very helpful.

Thanks

Yes, very strange indeed! Unforunately The service is secured and internal so can't really share. I just opened a ticket with ESRI. I will post here once the issue is found.