No value means that column value in the hash table was not available.
New value means that the correct value for the column was available.
I tried reproducing that configuration in a new document library but there everything kept working, so the issue had to be with the existing library.
Further analysis, comparison and reflection showed that the problematic library was missing some Taxonomy-related Event Receivers.
This was my scenario: I had created a remote event receiver that was attached to a document library and was supposed to act whenever an item in the list was updated.
This was the method I created: It checks if the property exists at all (it doesn’t if it is an Item Added-event and the property is custom made) and if it differs.By comparing the values in the before Properties with the after Properties I could see if they contained a difference.If it doesn’t, the updating event should not happen again.How I solved it Googleing this helped me not one bit and my first solution was something I would like to hide at the bottom of some server (I don’t want to talk about it, let’s just say it had something to do with counting the seconds since the last update).At your disposal on SPRemote Event Properties you have after Properties and before Properties, found by doing this: And those were the key to the problem: how to act on the firing only when the user changes something and not when it updates itself?