[GH-ISSUE #342] Some phone numbers not deleted correctly in Outlook #797

New issue

Closed

opened 2026-03-01 17:41:37 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 17:41:37 +03:00

Owner

Originally created by @feinidev on GitHub (Feb 14, 2022).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/342

Hello,

we are syncing contacts from a CardDAV-Server (SOGo) to Outlook via "Outlook <- Server (Replicate)" and noticed that some phone numbers are not deleted in Outlook although they were deleted on the CardDAV server.

Steps to reproduce:

Contact on CardDAV server has a phone number of type "Pager" or (none)
After sync the contact's number appears as expected in Outlook
Delete the number on CardDAV server
Sync again
The number still exists on the contact in Outlook
we expected the number to be deleted in Outlook aswell.

We figured out that in ContactEntityMapper > MapTelephoneNumber2To1() the "main" numbers are set to string.Empty, but others like PagerNumber and OtherTelephoneNumber are not.

When adding these lines our described scenario works as expected.
Are these phone types intentionally left out for other cases of synchronization or are they really missing?

CalDav Synchronizer 4.1.0.0 (same in 4.0.0.0)

Originally created by @feinidev on GitHub (Feb 14, 2022). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/342 Hello, we are syncing contacts from a CardDAV-Server (SOGo) to Outlook via "Outlook <- Server (Replicate)" and noticed that some phone numbers are not deleted in Outlook although they were deleted on the CardDAV server. Steps to reproduce: 1. Contact on CardDAV server has a phone number of type "Pager" or (none) 2. After sync the contact's number appears as expected in Outlook 3. Delete the number on CardDAV server 4. Sync again 5. The number still exists on the contact in Outlook we expected the number to be deleted in Outlook aswell. We figured out that in `ContactEntityMapper` > `MapTelephoneNumber2To1()` the "main" numbers are set to string.Empty, but others like PagerNumber and OtherTelephoneNumber are not. ![2022-02-14_MapTelephoneNumber2To1](https://user-images.githubusercontent.com/38004296/153844548-d4222c56-fa74-4133-acaa-9bde3d77a9d0.png) When adding these lines our described scenario works as expected. Are these phone types intentionally left out for other cases of synchronization or are they really missing? CalDav Synchronizer 4.1.0.0 (same in 4.0.0.0)

kerem closed this issue

2026-03-01 17:41:37 +03:00

kerem commented

2026-03-01 17:41:37 +03:00

Author

Owner

@aluxnimm commented on GitHub (Feb 14, 2022):

Thx for the report, you are right, those are missing. Will be added in the next release.

@aluxnimm commented on GitHub (Feb 14, 2022): Thx for the report, you are right, those are missing. Will be added in the next release.