https://bugs.kde.org/show_bug.cgi?id=482398
--- Comment #1 from Krzysztof Nowicki <kri...@op.pl> --- Exchange categories contain far less metadata compared to Akonadi tags. On the Exchange side there is only a name and colour. This was the main reason why the EWS resource only does one-way synchronization of tags into categories. It writes the full Akonadi metadata into custom attributes and only sets the category name corresponding to the Akonadi tag name. The problem with reverse synchronization is that on Akonadi side it is perfectly possible to have multiple tags with identical name - they will just have a different internal identifier. In such case the conversion from Exchange (just name) into Akonadi would be ambiguous. It would also be unclear what to do in case an Exchange category is retrieved, that doesn't have an Akonadi tag with a corresponding name. I agree that it would be possible to come up with a set of conversion rules and allow limited reverse sync (Exchange -> Akonadi). -- You are receiving this mail because: You are watching all bug changes.
