Question

A developer defines a new alternate key on the Account table combining two columns to support an integration that uses UpsertRequest with that key. Immediately after saving the key definition in the maker portal, the integration begins sending upsert calls, but they fail with an error indicating the alternate key is not usable. What is the most likely cause?

Accepted Answer

Alternate keys require a supporting database index that is created by an asynchronous system job, and the key is not usable until that job completes and the key status becomes Active.

Answer

Alternate keys cannot be composed of more than one column, so the definition is invalid and must be reduced to a single column.

Answer

UpsertRequest does not support alternate keys and only works with the primary GUID, so the integration must be rewritten to query first.

Answer

The columns used in the alternate key must be of type Lookup, and text or number columns cannot participate in an alternate key.