Does Upsert Mapping require a Salesforce Id to determine whether to update or create a record in the target Domain Object?

Does Upsert Mapping require a Salesforce Id to determine whether to update or create a record in the target Domain Object?

• A. True
• B. False
• C. Depends on configuration
• D. Only for external objects

Answer: (B)

Upsert mapping determines whether to update an existing record or create a new one by using a key on the target object, typically an external ID field. You provide the value for that external ID, and the system searches for a matching record. If a match is found, it updates; if not, it creates a new record. The Salesforce Id is not required for this process, and explicitly using the Id isn’t how upsert is normally driven. If you do have a Salesforce Id and want to update a specific record, you’d perform a straight update rather than upsert.

Upsert mapping determines whether to update an existing record or create a new one by using a key on the target object, typically an external ID field. You provide the value for that external ID, and the system searches for a matching record. If a match is found, it updates; if not, it creates a new record. The Salesforce Id is not required for this process, and explicitly using the Id isn’t how upsert is normally driven. If you do have a Salesforce Id and want to update a specific record, you’d perform a straight update rather than upsert.