How does CMSImport cope with RelatedLinks data type? For example, we're importing a lot of content (~15,000 items) from a legacy site, this content is then interlinked using a Related Links datatype. Can CMSImport cope with this?
Alternatively, do I need to store the old node id in a document property, then write a DataProvider that looks up the old node id and if found, links to it. If it doesn't find it (because it hasn't been imported yet) then it ignores it. (We then have to run the import process twice with the Update option so it catches these not-found-because-not-imported-yet errors?
I didn’t receive any notifications that you posted the topic. So sorry for not replying. But Related data itself is supported only RelatedLinks datatype not.
Maybe you can use MNTP instead? Then the match will be made on nodename When found the mapping will be created automatically Then you don’t need to use mappings with id’s etc.
Using Related Links and CMSImport
Hi,
How does CMSImport cope with RelatedLinks data type? For example, we're importing a lot of content (~15,000 items) from a legacy site, this content is then interlinked using a Related Links datatype. Can CMSImport cope with this?
Alternatively, do I need to store the old node id in a document property, then write a DataProvider that looks up the old node id and if found, links to it. If it doesn't find it (because it hasn't been imported yet) then it ignores it. (We then have to run the import process twice with the Update option so it catches these not-found-because-not-imported-yet errors?
Thoughts? Many thanks Simon
Bump - anyone? @rsoeteman?
Cheers Simon
I didn’t receive any notifications that you posted the topic. So sorry for not replying. But Related data itself is supported only RelatedLinks datatype not.
Maybe you can use MNTP instead? Then the match will be made on nodename When found the mapping will be created automatically Then you don’t need to use mappings with id’s etc.
is working on a reply...