Answered by:
How to dynamically skip changes using SimpleSyncProvider

Question
-
It doesn't seem possible?Friday, April 23, 2010 11:45 PM
Answers
-
That makes sense. Even though these are not error conditions for you it sounds like the recoverable error mechanism is what you want to use. You'll need to skip the changes every time since the file sync provider has no concept of skiping folders but this should work. Alternatively you could use your simple provider on both sides and simply not include folders as part of your change detection. But if you want to stick with the FSP here then recoverable errors are the way to go.
Cheers,
-Mike
- Marked as answer by Michael Clark [MSFT]Microsoft employee Tuesday, April 27, 2010 3:56 PM
Tuesday, April 27, 2010 3:55 PM
All replies
-
Maybe I don't understand your question yet but look at the information about recoverable errors. For instance in managed code, try calling RecoverableErrorReportingContext.RecordRecoverableErrorForChange(new RecoverableErrorData(...)) for any of the items that interact with items like UpdateItem, LoadChangeData, etc.
Cheers,
-Mike
- Proposed as answer by Michael Clark [MSFT]Microsoft employee Monday, April 26, 2010 3:10 PM
Monday, April 26, 2010 3:10 PM -
The scenario I talked about was not an error condition, but a deliberate skip. Let me explain my scenario – I’m using a simple provider to work with a windows file provider. My provider doesn’t care about folders so when I sync from windows file provider to my provider, I want to skip all folders. I can filter out folders by static filter of windows file provider, because doing so will filter out all files under the folders as well. So I’m thinking to skip the folders dynamically.
Monday, April 26, 2010 5:11 PM -
That makes sense. Even though these are not error conditions for you it sounds like the recoverable error mechanism is what you want to use. You'll need to skip the changes every time since the file sync provider has no concept of skiping folders but this should work. Alternatively you could use your simple provider on both sides and simply not include folders as part of your change detection. But if you want to stick with the FSP here then recoverable errors are the way to go.
Cheers,
-Mike
- Marked as answer by Michael Clark [MSFT]Microsoft employee Tuesday, April 27, 2010 3:56 PM
Tuesday, April 27, 2010 3:55 PM