Example - Importing a culture version of a page using the Kentico Import Toolkit

✖
Copy to clipboard

The following example demonstrates how to import a new culture version of a page.

Important: When using the import toolkit to add language versions to an existing page (node in the content tree), your source data must contain a column with appropriate NodeAliasPath or NodeID values. These values are required for the import to match data records to corresponding content tree nodes (for more information, see Page database structure).

This example imports an Article page from one Kentico database to another.

  1. Run the utility from Windows Start -> All Programs -> Kentico <version> -> Utilities -> Kentico Import Toolkit.
  2. Choose Start new import session.
  3. Click Next.

Step 1

  1. Choose the folder of the target project into which the data will be imported.
  2. Backup your data and confirm that you know the risks associated with importing.
  3. Click Next.

Step 2

  1. Choose Pages from the Select data type to import drop-down list.

  2. Select a site where you want to import the page in the Import data to site drop-down list.

  3. Select the Article page type from the Import as drop-down list.

  4. Select Import new and overwrite existing pages from the Import options.

    Configure the settings for importing language versions of documents

  5. Click Next.

Step 3

  1. Provide the source MS SQL database information and the authentication information.
  2. Click Next.

Step 4

  1. Select the SQL query option.

  2. Enter an SQL query selecting the culture version of pages that you want to insert. For example, the following SQL query selects pages of the DancingGoat.Article page type in the es-ES culture:

    


 SELECT View_CMS_Tree_Joined.*, DancingGoat_Article.* FROM View_CMS_Tree_Joined INNER JOIN DancingGoat_Article ON View_CMS_Tree_Joined.DocumentForeignKeyValue = DancingGoat_Article.ArticleID
 WHERE ClassName = 'DancingGoat.Article' AND DocumentCulture = 'es-ES'

    Select the News documents form the source database

  3. Click Next.

Step 5

Confirm your data selection and click Next.

Step 6

  1. Enable the Show advanced columns option.

    • If the advanced column fields are not filled in automatically, click Back once and Next again to refresh the view.

  2. Check whether the NodeAliasPath target field is mapped to the NodeAliasPath source field.

  3. Erase the NodeAlias field. It must remain blank in order to import a new culture version of the same page.

  4. Type the parent path of the pages into the text field below the data grid (you can use macros).

    Adjust the column mappings for importing language versions of pages

  5. Click Next.

Step 7

Click Import data.

Step 8

After a successful import of multilingual pages, you should see the number of items that were created in the target database. Close the dialog.