I am using your absolutely amazing uSync, right now in the free edition.
Quick question:
I want to import a bunch of content items, document type items etc., and some of the import items already exist in the target database.
All items which exist in both the source and the target database have matching aliases, most items also have matching Guid's, but some items (i.e. template items) have matching aliases but different Guids.
How is uSync handling this right now, when I import those items?
uSync should import them and then update the guid key value on the site to match the value in the file.
using will first look for items by Key (GUID) and when it can't find an item by the key will look for it by the alias, and then it will match the alias and carry on the update.
as part of the update it will then update the key (GUID) value to match that in the file.
this works for most 'settings' items, as the aliases are unique, it doesn't do it this way for content / media because the alias can be shared (e.g you can have to contact pages in diffrent places on a site) - so for them it also looks for the "path" of an item to try and locate it in the correct place within the site.
Import with matching alias but different Guid
Hi Kevin,
I am using your absolutely amazing uSync, right now in the free edition.
Quick question:
I want to import a bunch of content items, document type items etc., and some of the import items already exist in the target database.
All items which exist in both the source and the target database have matching aliases, most items also have matching Guid's, but some items (i.e. template items) have matching aliases but different Guids.
How is uSync handling this right now, when I import those items?
Thank you for a comment on this!
Best regards, Mikael
Hi Mikael,
uSync should import them and then update the guid key value on the site to match the value in the file.
using will first look for items by Key (GUID) and when it can't find an item by the key will look for it by the alias, and then it will match the alias and carry on the update.
as part of the update it will then update the key (GUID) value to match that in the file.
this works for most 'settings' items, as the aliases are unique, it doesn't do it this way for content / media because the alias can be shared (e.g you can have to contact pages in diffrent places on a site) - so for them it also looks for the "path" of an item to try and locate it in the correct place within the site.
Hi Kevin,
thank you for the super-quick clarification. Greatly appreciated.
Mikael
is working on a reply...