Which checkbox helps prevent a DataRaptor Load from creating duplicate records?

Which checkbox helps prevent a DataRaptor Load from creating duplicate records?

• A. Upsert Key
• B. Is Disabled
• C. Is Lookup
• D. Is Required For Upsert

Answer: (A)

Upsert Key is what tells DataRaptor Load how to match incoming data with existing records. By selecting a field as the Upsert Key (commonly an external ID or another unique field), the load looks for a record that already has that same value. If it finds a match, it updates that record instead of creating a new one; if no match exists, it creates a new record. This matching behavior is what prevents duplicates, since duplicates would have to share the same identifying key to be treated as the same record. The other options don’t perform this matching: disabling would skip the run, a lookup flag relates to relationship fields, and making a field required for upsert only enforces presence, not how to detect existing records.

Upsert Key is what tells DataRaptor Load how to match incoming data with existing records. By selecting a field as the Upsert Key (commonly an external ID or another unique field), the load looks for a record that already has that same value. If it finds a match, it updates that record instead of creating a new one; if no match exists, it creates a new record. This matching behavior is what prevents duplicates, since duplicates would have to share the same identifying key to be treated as the same record. The other options don’t perform this matching: disabling would skip the run, a lookup flag relates to relationship fields, and making a field required for upsert only enforces presence, not how to detect existing records.