| |||||||||||
|
|
Export Changes as XML
This option
gives a programmer the most flexibility to process the changes using custom
built code – as all edits and merges are listed in an XML file and can be
processed according to your needs and limitations. The program would need to read in the file
and execute the Merges and Edits in the order they are listed in the file. This is an
example of the output you get from this file:
There are two key XML elements in this file: 1) <Edit> This describes a
single field being updated within a single record. Edits can be independent, or nested as part
of a Merge within its corresponding <Merge></Merge> tags. For example:
This Edit is
updating the field FirstName to
“Kevin” where the primary key is 2895. 2) <Merge> This involves the
deleting of the slave record which was confirmed by the user as being a
duplicate of the master record. For
Example:
Often fields in the
master record need to be updated with data in the slave to prevent data
loss. In this example, the merge is
deleting the record 3546 and as part of that merge is updating record 1361 with
a new ‘TotalSales’ value along with a new ‘CustomerStatus’ value. Related Topics | ||||||||||
|
Duplicate Record Remover
Copyright (c) 2009 Precision Data, All Rights Reserved. | |||||||||||