On 13/07/15 11:53, Patrick Ohly wrote:
> If not, does activesyncd have to go and refetch the entire
> updated object from Exchange?
I think that would be the more realistic solution.
Thanks for the info. I had assumed that merge/change handling was not
an option but thought I would check!
I also wonder whether the server can be told to avoid incremental
updates in the first place.
I will do more investigation. I am not sure whether the behaviour is
new (e.g. a new version of Exchange): I have recently changed the way I
am using syncevolution across my different devices and only actually
noticed the problem because the corrupted events fail to sync with
Owncloud causing the sync operation to fail with an error (note: the EAS
sync where the corruption occurs does not fail or produce any
user-visible errors at all!).
I will look into whether I can find out under what circumstances the
Change is being sent and whether I can avoid it. It only occurs with
very a small number of events (currently 2 out of over 2000 in my
calendar) but I am not sure if it is to do with the event or the type of