Syniti Migrate

Dataset and Mapping Import

When you upgrade from an older version of Migrate (formerly Concento) to the latest version of Syniti Migrate, the active data from the old system can be imported into Migrate. Users extract the mappings for each table from an older version into an Excel spreadsheet of standard fields named DATASET_AND_MAPPING_IMPORT_TEMPLATE.xlsx. Users can extract and save each active mapping to import into Syniti Migrate. This process only imports files with Excel extensions (.xls and .xlsx) and fails if the user attempts to import files with other extensions (e.g., txt or csv).

NOTE: UTF-8 double-byte characters, for example Japanese or Korean languages, load using Excel Import.

This page contains the following sections:

Prerequisites

Prior to importing datasets and mappings metadata from a prior version of Migrate, you must:

Dataset and Mapping Import Template Spreadsheet

During the initial setup of a new project, there may be a need to import the datasets and mappings used in prior projects. For the import to work, the downloaded spreadsheet template that you use for this purpose must remain in its original form; the column order cannot be changed and the first two rows cannot be changed.

The Dataset and Mapping Import Template spreadsheet contains column headers for:

  • DATASET_NAME

  • TARGET_INDEX

  • DATASET_DATASOURCE

  • DATASET_TABLE

  • TARGET_DESCRIPTION

  • DATA_ELEMENT_INDEX

  • DATA_ELEMENT_NAME

  • DATA_ELEMENT_DEFINITION

  • DATA_TYPE

  • FIELD_LENGTH

  • DECIMAL_VALUE

  • CHECK_TABLE

  • KEY_FIELD_FLAG

  • BUSINESS_PURPOSE

  • COMMENTS

  • DATA_ELEMENT_ACTIVE

  • LOAD_SEGMENT

  • LOAD_FIELD

  • MIGRATION_FLAG

  • SUBJECT_AREA

  • PROJECT_NAME

  • RELEASE_NAME

  • SOURCE_DATASOURCE

  • PRIMARY_TABLE

  • ACTION

  • SOURCE_TABLE

  • SOURCE_FIELD

  • MAPPING_RULE

  • MAPPING_COMMENT

  • RULE_SQL

  • XREF_TABLE

Download the Dataset and Mapping Import Template

To produce a local copy of the Dataset and Mapping Import Template:

  1. Select Administer > Imports > Dataset and Mapping Import from the Migrate menu.

  2. Click the Download Template button.

    NOTE: A local copy of the Excel spreadsheet used to store the rows of data for Mapping and Dataset Import is downloaded.

  3. Complete the spreadsheet following the instructions in the header rows and save it once the dataset and mapping data to import has been added.

Import the Template Spreadsheet

To import the template spreadsheet with the dataset and mapping data:

  1. Select Administer > Imports > Dataset and Mapping Import from the Migrate menu.

  2. Click the Choose File button.

  3. Select the appropriate file.

  4. Click Open.

    The Dataset and Mapping Import Template spreadsheet contains two rows of notes and instructions at the top, and the value in Header Start Row defaults to 3.

    The preview lists the first ten rows of data and the count of rows is provided within the Import File section in Number of Records Detected.

    In this example, the template columns are displaying as expected. This file displays on the page and the buttons for Clear Field and Import Data are active for use.

    NOTE: The import process warns about fields that are marked as Data Element inactive because they are not mappings for import. The Migrate fields such as ZDEPLOY, ZACTIVE, or Zfieldname are set to Data Element inactive and the Migration Flag is set to active, so these fields import as expected.

  5. Click the Import Mappings button to initiate the import of data to the assigned objects in Syniti Migrate.

NOTE: If the data already exists in Migrate, a warning message displays. Click one of the options:

  • Cancel—Stop the import action and do not overwrite any datasets or mappings.

  • Append—Append the new data on to an existing object

  • Truncate—Truncate the tables and add the data as the only data for the object

If you click the Append button or the Truncate button, the import process starts.The page indicates that the job is running. It updates to Status: Import Finished once complete.

If the job fails, click the View Diagnostics button to open the Debug Log page to display the job queue.

Job Queues Steps for Each Import

The resulting job is entered as a Job Queue with each import of mapping data set as a step.

Job Queue: Import Mappings

Errors During Import of Datasets and Mapping Data

If the import of spreadsheet data fails, a message displays to provide details.

Issue details are stored in the Debug Log (Monitor > Debug Log). Click OK to the error message and the page resets to the main page.

If you attempt to import a spreadsheet that is not formatted correctly, the system provides the Preview of Imported Data values, however, error messages display in the Import File section of the page to provide details of issues with the current spreadsheet.