Using a UniqueValueRenderer. How do you tell it to update when you know the value has changed?

Question

I'm using a UniqueValueRenderer with a function for the field.  There are times in my program when I know that the value returned by this function will have updated for some of the features.  But they don't update on the map.

Is there a way to tell the feature layer to rerender itself?

quooston · Answer

I fixed it...

PEBKAC! I was triggering the main update after the one I care about as well. Not sure why that would do anything with the attribute I care about (it updates the coordinates) but it must have been nullifying my attribute update straight away, making it override the change I had just made. I guess if I set the attribute to what it currently is again it might work that way. But, I don't need to... so all good.

quooston · Answer

Hey @KristianEkenes ,

I thought I would share one more detail here.

I have a number of ajax requests hitting various APIs on intervals, the results of which usually have some kind of impact on the displayed map. I found that if I update the attribute I care about for the main API poll, it works... but for the one I care about for this particular feature, it doesn't. Super weird especially given that they share the same code for doing the actual update to the map through applyEdits.

I will still try to put something together to replicate the issue, but I thought I would share that in case it gets you thinking of something. Could there be some kind of race condition for updating the attributes of the features on the map? Is there a check I can perform when applying edits to ensure that there is no conflict or something?

Thanks again.

quooston · Answer

Ok sure, I will put something together.

Thanks