Internall uSync is uing the UDI and key values of all the properties/Content items - it will only uses IDs locally for when the UI is telling the backoffice code what you have requested to be published, almost straight away, those IDs are converted to the UDI values, and that is what is used for the syncing. it is always syncing with Key/UDI values between sites.
because uSync can also be installed on existing sites, it will fall back to look for things by alias or path, but only when it can't find the keys to sync between.
if you have some internal/3rd party property editors that are storing ID values for content then you might need value mappers so uSync knows how to get those IDs into Key values, but most known property editors already store things in GUID/Udi values so mostly thats not an issue.
Can uSync Complete be set to use UUID instead of Id when publishing?
Hey,
When comparing environments, can uSync Complete be set to use UUID instead of Id?
// Michael
Hi Michael,
Where do is it you think uSync needs use UUDI?
Internall uSync is uing the UDI and key values of all the properties/Content items - it will only uses IDs locally for when the UI is telling the backoffice code what you have requested to be published, almost straight away, those IDs are converted to the UDI values, and that is what is used for the syncing. it is always syncing with Key/UDI values between sites.
because uSync can also be installed on existing sites, it will fall back to look for things by alias or path, but only when it can't find the keys to sync between.
if you have some internal/3rd party property editors that are storing ID values for content then you might need value mappers so uSync knows how to get those IDs into Key values, but most known property editors already store things in GUID/Udi values so mostly thats not an issue.
is working on a reply...