Object IDs supported for Load and Save operations

Why use object IDs?

Each Load/Save mapping (both global and child entity level) must identify an object ID attribute because the object ID information is used to uniquely identify records in CRM On Demand. When transacting to CRM On Demand for Load/Save operations, if no record type ID information is provided, or if there is a conflict with the IDs of an existing record, the SOAP request fails, and an error is thrown by the API.

What are the available object IDs?

What type of object IDs does the Connector currently support?

Currently, the connector only supports independent object IDs, so a user cannot configure more than one object ID for a Load/Save entity in the wizard UI - doing so will throw a validation error.