| Author |
Message |
Anders Heick
Guest
|
Posted:
Mon Dec 06, 2004 2:39 am Post subject:
Exchange unique id |
|
|
Reading through the Exchange SDK it is not clear to me what the
difference between the DAV:id and the DAV:uid fields is. Could someone
please clarify.
I'm working on a synchronization utility that will synchronize a
contact list in SQL server with a contacts public folder in Exchange.
Currently I'm using the DAV:uid as the link key but it seems that this
uid is different on each server hosting a replica of the public
folder. Due to fail-over I can't assume that the sync tool always
connects to the same exchange server.
1) Is the DAV:uid (or DAV:id) the correct unique id to use at all for
a replication scenario without public folder replication?
2) Which field should be used when dealing with public folder
replication to idenity a unique contact?
Kind regards,
Anders Heick
|
|
| Back to top |
|
 |
Michael
Guest
|
Posted:
Mon Dec 06, 2004 12:00 pm Post subject:
Re: Exchange unique id |
|
|
DAV:id and DAV:uid represent "unique id". If you move or copy your
item(contact) then these values will be changed.
You can try following properties.Ppermanenturl doesn't change if you move
item.
- http://schemas.microsoft.com/exchange/permanenturl
- http://schemas.microsoft.com/repl/repl-uid
Michael
-------------------------------
If you need WebDAV API for Exchange server,
use our component "WebDAV .NET for Exchange".
Check out http://www.independentsoft.com
"Anders Heick" <Anders.Heick@gmail.com> wrote in message
news:a30de9a6.0412051239.d3bd720@posting.google.com...
| Quote: | Reading through the Exchange SDK it is not clear to me what the
difference between the DAV:id and the DAV:uid fields is. Could someone
please clarify.
I'm working on a synchronization utility that will synchronize a
contact list in SQL server with a contacts public folder in Exchange.
Currently I'm using the DAV:uid as the link key but it seems that this
uid is different on each server hosting a replica of the public
folder. Due to fail-over I can't assume that the sync tool always
connects to the same exchange server.
1) Is the DAV:uid (or DAV:id) the correct unique id to use at all for
a replication scenario without public folder replication?
2) Which field should be used when dealing with public folder
replication to idenity a unique contact?
Kind regards,
Anders Heick |
|
|
| Back to top |
|
 |
AndersH
Guest
|
Posted:
Fri Dec 10, 2004 5:11 pm Post subject:
Re: Exchange unique id |
|
|
Thanks Michael.
This is the answer I got from the Exchange development team:
__________________________________________
Thanks for your interest in the Exchange SDK. DAV:id maps to
PR_INSTANCE_KEY
(http://msdn.microsoft.com/library/en-us/mapi/html/_mapi1book_pr_instance_key.asp)
and DAV:uid maps to PR_RECORD_KEY
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mapi/html/_mapi1book_pr_record_key.asp).
In answer to your first question, neither the DAV:uid property nor the
DAV:id property should be used for replication, since they are
calculated relative to tables and may change when a mailbox/folder/item
is moved/renamed/modified. The
http://schemas.microsoft.com/repl/repl-uid property should be used for
item replication (when public folder replication is not involved).
We've just added information on WebDAV replication to the December
update of the Exchange SDK, which enables clients to synchronize data
from an Exchange server using WebDAV . The December update of the SDK
will be available for browsing/download on
http://msdn.microsoft.com/exchange around the middle of this month. Be
sure to check out the What's New page of the SDK if this interests
you.
In answer to your second question, there is no property that uniquely
identifies a replicated item across public folder hierarchies on
different servers. There are a number of properties that will be
different between two "identical" items replicated in public
folders, including the various IDs, and the items should be considered
different in that regard.
__________________________________________
|
|
| Back to top |
|
 |
|
|
|
|