The Attribute Editor - Transfer Data

This function enables you to transfer data from one attribute to another. It is necessary that both attributes are located in the same object (e.g. in the document). Basically, any data type can be taken over, e.g. from a multi-lingual attribute to a text attribute or vice versa, or from a date, saved as text, to a DateTime attribute.

The data type of an attribute can be changed using an intermediate step, namely by copying the data to a temporary attribute first. 

Carry out a data backup first and test the result afterwards!

Example:

The Attribute GEPRUFT_DAT is available as a text attribute (VARCHAR). The test date will be entered into this attribute during a test step. This attribute is now to be transferred to a data attribute (DATETIME).

Step 1 • Step 2 • Step 3 • Step 4 • Step 5

Step 1: Create a temporary attribute of the same type

1. Click New function to create a new attribute.
2. Select the Document (Index) class.
3. Assign a name, e.g. TEMP.
4. Select the data type VARCHAR.
5. Specify a length, e.g. 80.
6. Save the data with OK.

The creation of the new attribute is now completed.

Step 2: Copy the data from GEPRUFT_DAT to the new attribute

1. Mark the new attribute TEMP, so that its values are displayed in the attribute description.
2. Click Transfer data. The Apply attribute value dialogue will be displayed. The previously marked attribute TEMP is entered as target.
3. To select a source, click on the " ... " button on the right. A selection list of possible source attributes will be displayed.
4. Select the required source attribute. In our example, it is the attribute GEPRUFT_DAT.

GEPRUFT_DAT will be entered as source attribute. You can now enter the options and the protocol for the planned transfer.

5. Activate the checkbox if you want a log file to be created. The file name will appear to the right of the box.
6. Click on the " ... " button to select another file. An Open dialogue window will be displayed.

Use the Transfer null values option to transfer non-allocated source values. Source values which have not been allocated are referred to as "null" in the database language, e.g. mask field of null values are empty. If you select this option, the target value will be set to null if the source value is null. This option is useful if the target value does include values, but has to be equalised with the source attribute completely. If this option is not selected, existing values of the destination attribute will not be overwritten with null values of the source attribute. The combination of several attributes is a good example for a useful deactivation.

In our example this option will be deactivated, as the new attribute has null default values. This is always the case if an attribute has been newly created. You only need to take over default values. In some cases the transfer speed will be increased as well.

Two different ways are provided for the data transfer. One way uses the formatting functions of the HELiOS attribute management and will be selected by deactivating the Copy unformatted option. Most data types can be transferred, using the HELiOS formatting function. This way is very complex (longer duration) and prone to errors (complex transformation steps). For most transfers, however, it is the only possibility and offers a greater security as HELiOS checks the values.

If this option is deactivated, the values will be copied on a database level. This process is essentially faster, but requires a deeper internal comprehension concerning the database types used by HELiOS. In order to provide a safe and compatible operation, this option can only be selected if an identical HELiOS data type has been selected for both attributes. In our example, the latter is the case, therefore this option has been chosen.

In this example, specify the settings as follows:

• Activate the Log checkbox.
• Deactivate the Transfer null values checkbox.
• Activate the Copy unformatted checkbox.

7. Start the process with Execute. Please note that you cannot stop the process once it has started. Upon completion of the process you will receive a confirmation or an error message. Confirm the confirmation/error message with OK and close the window with End.

Step 3: Delete the attribute GEPRUFT_DAT

The attribute GEPRUFT_DAT can now be deleted.

1. Mark the entry GEPRUFT_DAT in the Attribute Editor.
2. Click Delete and confirm with OK.

Step 4: Create a new attribute GEPRUFT_DAT

Now create a new attribute GEPRUFT_DAT with the data type DATETIME.

1. Click New.
2. Select the object class Document (Index) and the name GEPRUFT_DAT.
3. Select DATETIMEas the data type.
4. Check the Display format. It has to correspond to the source attribute and can be checked using the Test button next to the Display format. In our example, the source values are formatted as follows: DD.MM.YYYY (D for day, M for month and Y for year), e.g. 15.08.2011. This is the default formatting.

The advantage of DATETIME attributes is that the date will be saved independent of the formatting. Therefore, the display format can also be changed subsequently, if there are no reasons not to do so. It is also used for the taking over data for the interpretation of source data. After data transfer the display format can be changed.

Step 5: Transfer values from TEMP to GEPRUFT_DAT

Now transfer the data from TEMP to the attribute GEPRUFT_DAT. During this process, the data type will be changed. The display format has been adjusted in Step 3 already.

1. Mark the attribute entry GEPRUFT_DAT in the Attribute Editor.
2. Click the Transfer data button.
3. Specify TEMP as the source attribute.
4. Deactivate the Transfer null values checkbox.
5. Activate the Log checkbox and click Execute.

You can delete the TEMP attribute after successful transfer. As a precaution, however, you should test the result. If required, the protocol showing the source values which have not been transferred may give you a hint.

The Attribute Editor • General Information on HELiOS