...
| Panel | ||
|---|---|---|
| ||
|
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.
...
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:
- Replace: Erase existing data then add the new data.
- MergeAppend: Import Adds 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.
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.
Given the example above, replace would result in the following:
...
Merge
Imports new data without modifying existing data.
Given the example above, merge would result in the following:
...
Update
Updates matching records with new data and creates new records as needed.
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.
Given the example above, overwrite would result in the following:
...
- records without first erasing the existing data.
| Anchor | ||||
|---|---|---|---|---|
|
...