When running a parent/child import with no start node difined on the child, I get a ton of 'records skipped' which can only be because the child import is not being constrained by the start node on the parent. Is this a bug or by design?
I want to be able to copy the import to use for other start nodes but obviously this is made problematic because of the above
This is by design and is because there need to be a relation to its parent. I know you are using the Umbraco provider so it's difficult to modify but normally modifying the datasource with a default parent was easiest.
Can't you copy the failed items in the source db to a default location?
Thanks Richard - I worked around the issue by creating separate import rules for all the parent nodes than then ran the single child import with no start node which imported all children of those rules.
I still think it would be a good idea if the child imports had an internal reference to their parent rule though. So if no start node was set it would use that of its parent.
They shouldn't be child imports then :-) I get you though, as this is the way its always worked, so fair enough. Marking my workaround as the answer for other's benefit.
Minor niggles aside, CMSImport is an awesome tool for any Umbraco dev's arsenal. So thank you for making and supporting it so well #H5YR
Child import should take its start node from parent
When running a parent/child import with no start node difined on the child, I get a ton of 'records skipped' which can only be because the child import is not being constrained by the start node on the parent. Is this a bug or by design?
I want to be able to copy the import to use for other start nodes but obviously this is made problematic because of the above
Hi Barry,
This is by design and is because there need to be a relation to its parent. I know you are using the Umbraco provider so it's difficult to modify but normally modifying the datasource with a default parent was easiest.
Can't you copy the failed items in the source db to a default location?
Cheers,
Richard
Thanks Richard - I worked around the issue by creating separate import rules for all the parent nodes than then ran the single child import with no start node which imported all children of those rules.
I still think it would be a good idea if the child imports had an internal reference to their parent rule though. So if no start node was set it would use that of its parent.
I agree Barry but that would kill my support inbox with people asking why it's importing in the wrong folder even tho I would report it :-(
They shouldn't be child imports then :-) I get you though, as this is the way its always worked, so fair enough. Marking my workaround as the answer for other's benefit.
Minor niggles aside, CMSImport is an awesome tool for any Umbraco dev's arsenal. So thank you for making and supporting it so well #H5YR
is working on a reply...