Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Disable / Confirm deletions" Option for each direction #1548

Open
19michi98 opened this issue Oct 17, 2022 · 4 comments
Open

"Disable / Confirm deletions" Option for each direction #1548

19michi98 opened this issue Oct 17, 2022 · 4 comments
Labels

Comments

@19michi98
Copy link

I am using the Sync tool to synchronize my Work Kalendar (Outlook) with my Private one (google)(both ways).

I would love it if I could choose "Confirm deletions" for O->G and "Disable deletions" for G->O,
as I don't want the Tool to mess with my existing Outlook entries.

@19michi98 19michi98 added the enhancement New feature label Oct 17, 2022
@19michi98 19michi98 changed the title "Confirm deletions"/ Option for each direction "Disable / Confirm deletions" Option for each direction Oct 17, 2022
@phw198
Copy link
Owner

phw198 commented Nov 24, 2022

This should be achievable using the latest alpha to configure two one-way Profiles, each with the differing deletion options.

@19michi98
Copy link
Author

Thank you for the Information.
I am using Hotfix #1480 now and testing if it will sync both ways correctly.

@19michi98
Copy link
Author

I have the Problem now that when syncing back Google to outlook it overwrites my outlook entries by changing their property to private. I have "Merge with existing entries" disabled in order to not touch my original outlook entries...

@phw198 phw198 added the low label Dec 18, 2022
@phw198
Copy link
Owner

phw198 commented Aug 24, 2023

To follow up on this, in which situation are you getting deletions in G->O? It's sounding like they are unwanted/unexpected deletions, so it would be good to understand why they are happening in the first place...

Note, there is a hotfix available on #1691 that might help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants