Versions Compared

Version Old Version 8 New Version Current
Changes made by

Christian Gradolf

Christian Gradolf

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

With UTI version 9.22, the file format was changed to XML. The advantages of this format compared to the old "fixed" data export are:

  • Checks for correct data

  • Generally also import with different product versions between export and import system

  • Readable format

The old version of this tool can be called up via the menu function "Goto" → "Up-Download in old

  • format

".

Allows up- and download of ProNovia product definitions.

...

Info

When option Replace completely (delete) is selected, the predefined partial quantity will not be regarded. All data sets which are in the partial quantity but not in the file will be deleted.

...

Field

Description

Solution / free ID variant

Export settings are selected by solution ID (or any free ID) and variant. Data to be exported can be maintained in the respective variant. Push button "Customizing" will directly start the configuration.

Codepage (Unicode)

Generally not used.
Only necessary if the unicode handling for the related function is erroneous. Then the correct code page can be entered.

The following actions are available:

Action

Description

Import data

Data will be imported, using previously exported data. Before data is posted in the data base, all actions will be displayed consolidated. The data will be up-dated after saving.
Importing data has several options:

  • Add new
    Non existing data sets will be created. No data sets will be overwritten or deleted

  • Add new / replace
    Non existing data sets will be created, existing data sets will be overwritten. No data sets will be deleted

  • Replace completely
    Non existing data sets will be created, existing data sets will be overwritten. All data sets which are not in the file as defined for the partial quantity in the variant will be deleted.

Note

Make sure to select the correct variant, else the wrong data may be deleted. A plausibility check is highly recommended before final update, especially of deleted data sets.

Checks

The data is handled field by field from the XML file in the target. The following checks are made:

  • Can the file content be transferred without loss? A loss is possible, for example, if text fields have been extended on the target source system in a newer product version and these lengths are also used in the data.

    • Loss on a key field or a field in a unique index prevents the data from being saved (error).

    • Losses on other fields are displayed as warnings.

  • Conversion error, i.e. a value from the XML file cannot be included in the target format. This could be possible if, for example, the data types are different.

    • Conversion errors prevent the data from being saved (error).

Export data

All tables and data partial quantities according the variants will be exported. For each table a file will be created. All data is output in a structured XML file.

Write transport order

All tables and data partial quantities according the variant will be written to a transport request.

...