Coalesce can only use a single field to uniquely identify a record.

The statement is false. In ServiceNow Transform Maps, the coalesce functionality can be configured to use multiple fields to uniquely identify a record. When more than one field is marked as the coalesce field, the system uses the combination of values from all designated coalesce fields to create a unique key. An incoming record from the source table will update an existing record in the target table only if the values in all of its coalesce fields match the corresponding values in the target record. If no record matches this unique combination, a new record is created.

The option "True" is incorrect because it presents a false limitation of the ServiceNow platform. Relying on a single field for unique identification is often insufficient, especially when integrating data from disparate systems. The platform is designed to handle these complex scenarios by allowing a composite key (multiple fields) for the coalesce operation.

1. ServiceNow Product Documentation - Coalesce fields: "You can coalesce on a single field or on multiple fields. If you select multiple fields for coalescing, all coalesce field values for a staging table row must match the values of an existing record in the target table for a transformation to update that target table record." This statement directly confirms that multiple fields can be used.

2. ServiceNow Product Documentation - Transform Maps: In the section describing the Field Maps related list, the documentation details the "Coalesce" checkbox. It explains its function in matching source and target records, and the platform's behavior when this is applied to one or more fields. This implicitly supports the use of multiple fields by not limiting the function to a single field.