Import/Export: column allocation and table assignment

The order of dialogs differs depending on the kind of export or import.

If you export to a text file the Column allocation dialog opens first, then the Table association dialog.
If you export with OLEDB the Table association dialog opens first.

Table assignment

All tables of the selected data source and data target are displayed. Select which tables of the data source are to be imported / exported to which tables of the data target.

Selection: if a column is ticked this table is exported/ imported. You can also use buttons for selection.

Select all Ticks every row.

Invert selection The current selection is inverted, i.e. previously unticked rows are ticked and vice versa.

Select none: removes all check marks from all rows.

Source table/Target table: these columns display the table names of the selected databases. If tables with the same name are found in data target and data source they are automatically assigned.

Column allocation: clicking this column in a table row opens the column allocation window. You determine which columns of a table are to be exported/ imported. If there is only a source table the Column allocation window is automatically opened with the Table association dialog.

There are no character restrictions when importing content into fields from text type

Filter: clicking this column in a table row opens the Filter window. You can define filters for the source table, i.e. only the data records matching the conditions are copied.

Column allocation

In this window, all the columns for the source and target tables are listed. If column names match, source and target column are automatically assigned.

Please note

If data is exported, you will not be able to export column names from the database. When renaming several target columns with a column allocation, this order is not changed and can be reloaded.

You can update existing data by exporting data records into an existing CSV file. You cannot extend a CSV file. Thus, the selected columns from the target file are transferred and cannot be changed.

Functions

To change the allocation of columns, you click the target column field. Using the small arrow on the left, you can open a drop-down list, in which you can select and allocate a field for the target table.
If a new text file was created for export, source column names are entered as target. You can change this by clicking the field and entering a new name.
If the Selection column has been ticked, then this field is exported or imported.
You can change your selection via the button under the column entries.

Source columns display all fields in the data source. The target column displays the data target fields.

Each target column is assigned to a source column. If there is no name in the target column, then you should click the field and select a field in the target file using the small arrow on the right.

If when exporting a new text file was created, then the column allocation was selected automatically and the source column names were entered as the target. You can change this by clicking the field and entering a new name.

If you are exporting to a new text file, then you can define the order of the target columns. Click and hold the column you require and move it to a new position.
You should select a unique field as the Key field, for example, the GGUID field.
GUID is the acronym for Globally Unique Identifier. A GUID consists of a 32 digits combination of numbers and letters (hexadecimal combination). With the GUID, objects in a software environment - especially Microsoft Windows - can be identified distinctively.

GGUID is the acronym for the GUID in CAS genesisWorld, for example, each data record, user account, or database in CAS genesisWorld has been assigned such an identification key.

A GUID is unique in the system that is used. Therefore, GGUIDs for data records are unique in a database of CAS genesisWorld. GUIDs for databases are unique within the used database system and so on.

A Key field will only be available when importing and necessary if you wish to update data records through an import. When exporting, the unique GGUID field is also exported.

If you close the Column allocation window, then you define conflict handling for updating a data record on the Settings page. The key field is used in the process.

It will first be checked whether the specified key field really is unique.

During the import the database is searched for data records that match the specified key field.

When a data record with the same key field is found, the corresponding data is updated along with the imported data.

In case of conflicts, your input for conflict handling is taken into consideration.

If a data record which uses an identical key field is not found, then this data record is created anew.

If the key field is not unique or duplicates of the data record already exist in the database, the data record is not updated.

Using Save allocation and Load allocation you can use a saved allocation as often as you like.
Close Applies the selection and closes the dialog.