Attribute setup

Previous  Top  Next

In the Attribute Setup, you can define what data has to be fed back in which column of the destination database table. In the left part of the screen you see the table layout of the destination database. For each column, you can define an action. If additional information is required, you can define this in the right side of the Attribute setup window. Please note that you can resize this window.


Figure 5: Database Feedback Template, Attribute Setup tab

In the upper part of the window, you can see the name of the destination table and the operation type. The operation type shows if you can update information in this table or if you can insert new data into the table. The operation type is set when you add a new destination database.

In the left pane of the layout of the destination table is shown. The pane is divided in three columns.

Use: Check the box if you wish to use this column for database feedback. An i icon is presented next to the checkbox if there is additional information available for the column.
Attribute: The name of the columns in the feedback table
Action: Choose what data has to be placed in the column of the feedback table. The different actions are explained in the next chapters.

Different data types
In the upper part of the right pane you can see the metadata for the column that you have selected in the left pane. For each column you can see the data type. The Metatude software discerns four data types. These are string, number, date and boolean. These data types are an abstraction from the real data types that are present in your database. The actions that you can choose depend on the metadata of the column (such as the data type) and on the operation type.

Database constraints
If additional information is available, such as Primary Key, the not NULL constraint or a default value, it is displayed next to the data type. There are a few situations that require special care:

·	Not NULL constraint, no default value: If the operation type is insert, you will be forced to choose an action.

·	Unique columns: You can only choose to insert a respondent attribute. Other actions will not generate unique values, so they are disabled.

·

Primary keys: You cannot change the primary key of a table when the update operation is used. If the primary key is automatically generated for new rows, you cannot specify an action for the insert operation. If the primary key is not automatically generated, you must choose an action. Since primary keys need to be unique, you can only choose to insert a respondent attribute as the primary key.