Syntax
|
int sdq_set_dedup_candidates (int session_id, SSchar* parameterList, SSchar* xmlRecordSet)
|
Parameters
|
- session_id: The session ID obtained by initializing the session.
|
|
|
|
NOTE: The parameterList parameter is set to NULL as all required parameters are already set at the session level.
|
|
|
|
- For incremental data matching batch jobs: As more candidate records are queried from the Siebel database and sent to the vendor software, the driver records must be marked so that the vendor software knows which records must return duplicate records:
<Data> <DriverRecord> <Account.Id>2-24-E</Account.Id> <Account.Name>Siebel</Account.Name> <Account.Location>Somewhere</Account.Location> </DriverRecord> <CandidateRecord> <Account.Id>1-E-9E</Account.Id> <Account.Name>Siebel</Account.Name> <Account.Location>Somewhere else</Account.Location> </CandidateRecord> <DriverRecord> <Account.Id>1-E-2E</Account.Id> <Account.Name>Siebel</Account.Name> <Account.Location>Somewhere else</Account.Location> </DriverRecord> <CandidateRecord> <Account.Id>1-12-2H</Account.Id> <Account.Name>Siebel</Account.Name> <Account.Location>Somewhere else</Account.Location> </CandidateRecord> <DriverRecord> <Account.Id>2-34-F</Account.Id> <Account.Name>Siebel</Account.Name> <Account.Location>Someplace</Account.Location> </DriverRecord> </Data>
|
|
NOTE: The order of the driver records and candidate records is not significant. If a candidate has already been sent, it is not necessary to send it again even though it is a candidates associated with multiple driver records.
|
|
|
Return Value
|
A return value of 0 indicates successful execution. Any other value is a vendor error code. The error message details from the vendor are obtained by calling the sdq_get_error_message function. |