stssyncprovider Work Item Rss Feed

Commented Issue: Problem with Implementing Calendar [5199]

PaulLinton — Thu, 17 Dec 2009 05:58:09 GMT

Hello. I m trying creating calendar and I have issue when I try to synch outlook with database.
Outlook get to 79 present and then stack up like it goes to endless loop . Do you have any idea
What can be wrong outlook doesn’t shows any error it just keep working .
Thank you

Created Issue: Problem with Implementing Calendar [5199]

deng2 — Mon, 12 Oct 2009 09:32:08 GMT

Commented Issue: Updating a value in the source DB doesn't get synced to Outlook

tfsjohan — Fri, 15 May 2009 19:27:46 GMT

The vti_versionhistory value needs to be incremented. Currently this functionality is not implemented, but is a Pri-1 issue.
Comments: ** Comment from web user: tfsjohan **

Have you found any solution to this yet? I'd really like som help with this.

Commented Issue: Updating a value in the source DB doesn't get synced to Outlook

pcreehan — Mon, 08 Sep 2008 18:06:11 GMT

The vti_versionhistory value needs to be incremented. Currently this functionality is not implemented, but is a Pri-1 issue.
Comments: ** Comment from web user: pcreehan **

I'm open to ideas on this. Here some ideas I have:
1. Rely on the provider to do this. I don't necessarily like this option because the idea was that the provider just deals with data they know about and doesn't have to worry about things like vti_versionhistory updates.
2. Update the versionhistory when Outlook does an update (that way it's already updated next time). The problem with this is that if there ARE no updates and Outlook requests updates, it will get this one.
3. Update it when the provider returns it in a getupdates call. Again, i'd have to update the item inside the getitems call which will skew the modify time info.
4. Store this information myself and just return it on updates.

Created Issue: Updating a value in the source DB doesn't get synced to Outlook

pcreehan — Wed, 23 Jul 2008 13:09:30 GMT

The vti_versionhistory value needs to be incremented. Currently this functionality is not implemented, but is a Pri-1 issue.