Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Rick Mather 42 posts 124 karma points
    Mar 28, 2011 @ 13:08
    Rick Mather

    Hierarchical import

    Hi, i'm aware that 'structured import' is coming in CMSImport 2, so apologies if i'm requesting something that you're already planning, but I was wondering if it would be capable of doing something like this:

    I'm currently importing nodes from a client's existing in-house CMS into Umbraco and it's going really well. I'm  having to do it one section at a time but the database schema i'm importing from looks like this:

    * MenuID
    * ParentID
    * Name
    * Content, etc

    What i'd love to see, if this is possible, is a facility allowing me to set up a hierarchical import where I can select which property is the nodes primary key, and which one is the parent ID. CMSImport could then run through each node, creating the the appropriate site structure as it goes along.

    I can see a few potential issues (such as trying to import a child node before its parent has been created), but I think this would be a very useful addition if it could be done.

    Thanks for an excellent product!

  • Jan Skovgaard 11257 posts 23497 karma points MVP 7x admin c-trib
    Mar 28, 2011 @ 13:34
    Jan Skovgaard

    Hi Rick

    Maybe this demo video of 2.0 answers some of your questions?


  • Richard Soeteman 3807 posts 11786 karma points MVP
    Mar 28, 2011 @ 16:21
    Richard Soeteman

    Hi Rick,

    The situation you describe will be in CMSIMport 2.0. It's not in the screencast Jan is mentioning, but it is already working in the current code base. In the example below I'm importing the structure form the Microsoft AdventureWorksLT database (Same as in the video).

    Basically the structure is (ProductCategory is Hierarchical ):

    - ProductCategory



    When you create the definition to import productcategories you can specify enable recursive imports. Then you can specify the foreign key, basically what you mentioned.

    Then when you import it will maintain the structure of the datasource. No need to worrie about import a child earlier than it's parent since the recursive structure happens after an import is finished.

    Below the completed import for productcategories and products, the folders are the categories.

    Hope this answers your question. And please let me knwo if you have additional questions




Please Sign in or register to post replies

Write your reply to: