...

The right panel displays the record types and fields for a group. Any record types or fields that match existing data repository records will be marked with the (matching) label.

• Data Set Import options apply to the data sets listed in the left panel. They are described in Understanding Data Set Import Options.
• Record Import options apply to the record types shown in the right panel. They are described in Understanding Record Import Options.
• Record Types tree modification options are described in Modifying Record Type and Field Names and Mappings and Specifying Record Identities from the Wizard.

Inferring Constraints

If you are using CTP, you can also choose an option for inferring constraints. Constraints are additional properties associated with the data that enable you to create models and generate test data (see Data Modeling). For example, data can be constrained to strings, numbers, dates, or Booleans.

Image Added

• Choose None if you do not want constraints to be defined.
• Choose Data if you want to automatically set constraints based on the data. You will have the option to populate metadata from the data into the data repository. For example, if the data set contains U.S. phone numbers, the following constraints may be set:

Constraint:String

Pattern:(###) ###-####

Char map:0123456789

See Inferring Data Constraints for additional information.

• Choose Definition if you want the constraints to be defined according to a service definition file (WSDL/schema). This option is disabled if you did not provide a definition file was not specified in the traffic wizard.

...

Existing constraints will be overwritten if you select an existing repository in the traffic wizard. You can view and modify in the constraints in CTP. See Data Modeling.

Understanding Record Identities

...

You can choose among the following options to control how new data from the traffic file will extend and/or update existing repository data sets:

SOAtest Options

• Replace: Erase existing data then add the new data.
• Append: Adds new records without first erasing the existing data.

Virtualize Options

• Replace: Erase existing data then add the new data.
• Merge: Import new data without modifying existing data.
• Update: Update matching records with new data and create new records as needed.
• Overwrite: Update matching records (with matching keys) with new data, do not create any additional records.
  
  

Image Added

For a concrete example of how each strategy operates, assume that you have the following existing data set (where CustomerID is the key column):

Also assume that you have new traffic that contains the following data:

Replace

Erases existing data then add the new data.

Image Added

Given the example above, replace would result in the following:

Merge

Imports new data without modifying existing data.

Image Added

Given the example above, merge would result in the following:

Update

Updates matching records with new data and creates new records as needed.

Image Added

Given the example above, update would result in the following:

Overwrite

Updates matching records (with matching keys) with new data, does not create any additional records.

If you import traffic into a new data set, new records will be created even though there are no matching keys.

Image Added

Given the example above, overwrite would result in the following:

Anchor
Understanding Record Import Options Understanding Record Import Options

Understanding Record Import Options

...