Specify how the data is stored in the One Identity Manager database.
Select the target table into which to import the data.
Columns and their values are displayed.
|
TIP: Use the |
|
TIP: Use the assignment wizard to select the target system columns to insert the data into. |
To assign target columns and keys with the wizard
Icon | Meaning |
---|---|
< | Moves to previous column. |
> | Moves to next column. |
Automatic assignment of target column. Assigns a column if one is found in the target table whose name matches the name in the source column. It is strongly recommended that you check the assignment afterward. | |
Inserts a column. A column is inserted with a fixed value. | |
Deletes a column. Deletes a column with a fixed value. |
|
TIP: Use the option Show caption to swap between the display name and the technical column name. |
|
TIP: You can see a preview of the values in the section "Data preview". |
Property | Description | ||
---|---|---|---|
Use as key column |
Specifies whether the column is used as a key column. More than one key columns can be defined. | ||
Conversion script |
Use the conversion script to modify source column values to match the permitted value of the target column. This is required, for example, if a list of permitted values is defined for the target columns. Write the conversion script in VB.Net syntax. You access the values with the variable value. Use dollar notation to access the source columns. | ||
Target columns |
Select the target columns to be imported into the data. All columns from the target table are displayed with their data type. Following applies:
|
After completing your assignments, close the wizard by click on a point outside the wizard.
You can also add additional columns with fixed values to the import data and import it to a defined column.
To insert columns with fixed values
- OR -
Enter a conversion script if the value should be taken from the source column.
If an import contains inter-dependent data, you must ensure that the reference targets are handled before the reference sources.
For example, child departments (Department.UID_Department) are imported after parent departments (Department.UID_ParentDepartment).
|
NOTE: Sorting data in a hierarchical structure can take up a lot of memory. Therefore, only use this procedure for imports with small amounts of data. |
To sort data hierarchically
|
NOTE: Sort the data in the import files accordingly beforehand, to resolve object dependencies in larger CSV imports. For larger imports from external data sources, use the "ORDER BY" clause to sort the data. |
Specify how new and existing data sets are handling when they are imported. During import, the source data sets (case C) are compared with the entries in the database (case A).
You can restrict the number of relevant database entries by using the Condition for target objects (case B). The condition is tested when importing begins. There is a wizard available though the button next to the input field, to help you formulate your condition.
The import needs to take several cases into account and react accordingly to each one:
|
IMPORTANT: If the option Insert new data set is set, the entries that are in the source data but are not in the range of relevant database entries due to the Condition for target objects, are treated as a new data set and are inserted into the database (case G). This can lead to errors (double data sets). |
Figure 57: Example for Handling Data Sets
Case | Description |
---|---|
A | All objects in the database. |
B | Database set restricted by condition. |
C | Entry in source data. |
D | All entries in the database and in the source data. Typical action: update all entries in the database. |
E | Entries that are only in the source data but not in the database. Typical action: add new entry in the database. |
F | Entries that are in the database but not in the source data. Typical action: clean up entries in the database. |
G | Entries that are in the source data but no in range selected in the database. These entries are treated as in case E although adding entries may cause conflicts in certain circumstances. |
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy