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?
- The Oracle Web Services On Demand Guide provides a list of Object IDs (user keys) available for the core objects of CRM On Demand.
- One object ID on its own can act as a user key, depending on whether the field can identify the record as unique. The basic object ID is the single attribute “<entity-id>Id” (Web Services v2.0) or “<entity-id><record-type>Id” (Web Services v1.0); for example, for the Account record type – crmodAccountId or crmodAccountAccountId is an object ID.
- Every record type in CRM On Demand has at least the following independent object ID:
- Id or <record-type>Id
- ExternalSystemId
- In addition, there are various field combination for different objects that can also be used to define the object ID.
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.