Aborting sync with an exception throw
-
Tuesday, February 26, 2013 12:26 PM
Sorry - I asked this question in the SyncFrameworkToolkit forum as well. This forum seems to be more active.
Hi,
I would like to be able to Abort a sync operation based on a number of factors determined server side.
For example, if the sync user has not authenticated or has been 'disabled' (from syncing), or if the sync scope is 'down for maintenance'.
I have played around with the SyncRequestInterceptor to throw an exception to successfully abort the sync operation, however I cannot see a way of getting any meaningful information about why the sync was aborted back to the client.
I have found this post: http://social.msdn.microsoft.com/Forums/uk-UA/synclab/thread/9678137b-914a-4b26-8ce6-bac5df662f60 asking a similar question a few years ago.
Apologies if this has been answered, or if I have missed something obvious. (I am quite new to this!)
Thanks for any help.
All Replies
-
Tuesday, February 26, 2013 12:43 PMModerator
have you tried setting UseVerboseErrors to true?
as a side note, why dont you just make a separate call outside of the sync to check if the sync should be allowed or not? (i.e, write a separate service method to call from the client)
-
Wednesday, February 27, 2013 12:56 PM
Hi JuneT, many thanks for your suggestions.
Yes I already have UseVerboseErrors set to true.
Yes, we did consider that approach of using another service call to allow/disallow the sync, so that may be an appropriate solution for us. It just would have been nice if it could have been handled in the interceptors also.
-
Thursday, February 28, 2013 11:13 AMModeratorhandling it via interceptors would have been a more expensive operation as by then Sync Fx would have fired unnecessary queries for metadata...

