CustomObject1 - CustomObject3
The CustomObject1, CustomObject2, and CustomObject3 services expose the functionality of the CustomObject1 - CustomObject3 objects to external applications.
Parent Objects
Child Components
Account, Attachment, Book, Contact, Opportunity, Portfolio, and Team.
CustomObject1, CustomObject2, and CustomObject3 also have child components for the other CustomObjects as follow:
CustomObject1. CustomObject2 and CustomObject3 child components.
CustomObject2. CustomObject1 and CustomObject3 child components.
CustomObject3. CustomObject1 and CustomObject2 child components.
For information about using attachments with these objects, see Using Attachments with Web Services On Demand
Methods Called
The following table details the methods called by the CustomObject1 service. The methods for CustomObject2 and CustomObject3 follow the same pattern.
Method | Name as Defined in Service |
---|---|
CustomObject1Delete |
|
CustomObject1DeleteChild |
|
CustomObject1Insert |
|
CustomObject1InsertChild |
|
CustomObject1OrUpdate |
|
CustomObject1Page |
|
CustomObject1Update |
|
CustomObject1UpdateChild |
Fields
The following table details the required and read-only fields for the CustomObject1 object. The fields for CustomObject2 and CustomObject3 follow a similar pattern.
Child Component | Field Name | Type |
---|---|---|
CustomObject1 (parent) |
ParentId |
Required |
ParentExternalSystemID |
Required |
|
ParentIntegrationId |
Required |
|
ParentObject1Id |
Read-only |
|
Account |
CObj1AccountCreatedById |
Read-only |
CObj1AccountCreatedDate |
Read-only |
|
CObj1AccountModifiedById |
Read-only |
|
CObj1AccountModifiedDate |
Read-only |
|
Region |
Read-only |
|
AccountType |
Read-only |
|
Attachment |
DisplayFileName |
Required |
FileNameOrURL |
Required |
|
FileDate |
Read-only |
|
FileSize |
Read-only |
|
CustomObjectId |
Read-only |
|
Id |
Read-only |
|
ModId |
Read-only |
|
Read-only |
||
Book |
BookName |
Required |
BookId |
Read-only |
|
SystemAssociateFlag |
Read-only |
|
ModId |
Read-only |
|
Read-only |
||
Contact |
CObj1ContactCreatedById |
Read-only |
CObj1ContactCreatedDate |
Read-only |
|
CObj1ContactModifiedById |
Read-only |
|
CObj1ContactModifiedDate |
Read-only |
|
ContactFirstName |
Read-only |
|
ContactLastName |
Read-only |
|
ContactType |
Read-only |
|
CustomObject2 |
CObj1CustomObject2CreatedById |
Read-only |
CObj1CustomObject2CreatedDate |
Read-only |
|
CObj1CustomObject2ModifiedById |
Read-only |
|
CObj1CustomObject2ModifiedDate |
Read-only |
|
CustomObject2Id |
Read-only |
|
CustomObject3 |
CObj1CustomObject3CreatedById |
Read-only |
CObj1CustomObject3CreatedDate |
Read-only |
|
CObj1CustomObject3ModifiedById |
Read-only |
|
CObj1CustomObject3ModifiedDate |
Read-only |
|
CustomObject3Id |
Read-only |
|
Opportunity |
AccountName |
Read-only |
CObj1OpportunityCreatedById |
Read-only |
|
CObj1OpportunityCreatedDate |
Read-only |
|
CObj1OpportunityModifiedById |
Read-only |
|
CObj1OpportunityModifiedDate |
Read-only |
|
OpportunityName |
Read-only |
|
Revenue |
Read-only |
|
SalesStage |
Read-only |
|
Portfolio |
AccountNumber |
Read-only |
CObj1PortfolioCreatedById |
Read-only |
|
CObj1PortfolioCreatedDate |
Read-only |
|
CObj1PortfolioModifiedById |
Read-only |
|
CObj1PortfolioModifiedDate |
Read-only |
|
Revenue |
Read-only |
|
Team |
CustomObject1TeamId |
Read-only |
UserFirstName |
Read-only |
|
UserLastName |
Read-only |
The following table details the status key for the CustomObject1 object. The status keys for CustomObject2 and CustomObject3 follow a similar pattern.
Child Component | Field Name |
---|---|
CustomObject1 (parent) |
|
CustomObject1Id |
|
ExternalSystemId |
|
IntegrationId |
|
Account |
CustomObject1AccountId |
CObj1AccountCreatedById |
|
CObj1AccountCreatedDate |
|
CObj1AccountModifiedById |
|
CObj1AccountModifiedDate |
|
Attachment |
|
Id |
|
CustomObjectId |
|
Book |
|
BookId |
|
ModId |
|
Contact |
CustomObject1ContactId |
CObj1ContactCreatedById |
|
CObj1ContactCreatedDate |
|
CObj1ContactModifiedById |
|
CObj1ContactModifiedDate |
|
CustomObject2 |
CustomObject2Id |
CObj1CustomObject2CreatedById |
|
CObj1CustomObject2CreatedDate |
|
CObj1CustomObject2ModifiedById |
|
CObj1CustomObject2ModifiedDate |
|
CustomObject3 |
CustomObject3Id |
CObj1CustomObject3CreatedById |
|
CObj1CustomObject3CreatedDate |
|
CObj1CustomObject3ModifiedById |
|
CObj1CustomObject3ModifiedDate |
|
Opportunity |
OpportunityId |
CObj1OpportunityCreatedById |
|
CObj1OpportunityCreatedDate |
|
CObj1OpportunityModifiedById |
|
CObj1OpportunityCreatedDate |
|
Portfolio |
PortfolioId |
CObj1PortfolioCreatedById |
|
CObj1PortfolioCreatedDate |
|
CObj1PortfolioModifedById |
|
CObj1PortfolioModifiedDate |
|
Team |
|
CustomObject1TeamId |
The following table details the pick map fields for the CustomObject1 object. The fields for CustomObject2 and CustomObject3 follow a similar pattern.
Child Component | Pick Map Field | Maps To |
---|---|---|
CustomObject1 (parent) |
AccountExternalId |
AccountId |
AccountIntegrationId |
AccountId |
|
AccountName |
AccountId |
|
ActivityExternalId |
ActivityId |
|
ActivityIntegrationId |
ActivityId |
|
ActivityName |
ActivityId |
|
CampaignExternalId |
CampaignId |
|
CampaignIntegrationId |
CampaignId |
|
CampaignName |
CampaignId |
|
ContactExternalId |
ContactId |
|
ContactFirstName |
ContactId |
|
ContactFullName |
ContactId |
|
ContactIntegrationId |
ContactId |
|
ContactLastName |
ContactId |
|
CustomObject2ExternalId |
CustomObject2Id |
|
CustomObject2IntegrationId |
CustomObject2Id |
|
CustomObject2Name |
CustomObject2Id |
|
CustomObject3ExternalId |
CustomObject3Id |
|
CustomObject3IntegrationId |
CustomObject3Id |
|
CustomObject3Name |
CustomObject3Id |
|
DealerName |
DealerId |
|
HouseholdExternalId |
HouseholdId |
|
HouseholdIntegrationId |
HouseholdId |
|
HouseholdName |
HouseholdId |
|
LeadExternalId |
LeadId |
|
LeadFirstName |
LeadId |
|
LeadFullName |
LeadId |
|
LeadIntegrationId |
LeadId |
|
CustomObject1 (cont.) |
LeadLastName |
LeadId |
Owner |
OwnerId |
|
OpportunityExternalId |
OpportunityId |
|
OpportunityIntegrationId |
OpportunityId |
|
OpportunityName |
OpportunityId |
|
ParentExternalSystemId |
ParentId |
|
ParentIntegrationId |
ParentId |
|
PortfolioAccountNumber |
PortfolioId |
|
ProductExternalId |
ProductId |
|
ProductIntegrationId |
ProductId |
|
ProductName |
ProductId |
|
SolutionExternalId |
SolutionId |
|
SolutionIntegrationId |
SolutionId |
|
SolutionTitle |
SolutionId |
|
ServiceRequestExternalId |
ServiceRequestId |
|
ServiceRequestIntegrationId |
ServiceRequestId |
|
ServiceRequestName |
ServiceRequestId |
|
VIN |
VehicleId |
|
Account |
ExternalSystemId |
AccountId |
IntegrationId |
AccountId |
|
Location |
AccountId |
|
Name |
AccountId |
|
Book |
BookName |
BookId |
Contact |
ExternalSystemId |
ContactId |
IntegrationId |
ContactId |
|
CustomObject2 |
Owner |
OwnerId |
CustomObject3 |
Owner |
OwnerId |
Opportunity |
ExternalSystemId |
OpportunityId |
IntegrationId |
OpportunityId |
|
Portfolio |
ExternalSystemId |
PortfolioId |
IntegrationId |
PortfolioId |
|
Team |
UserExternalSystemId |
UserId |
UserIntegrationId |
UserId |
|
UserEmail |
UserId |
The following table provides a list of the filterable fields for the child components of the CustomObject1 object, and a list of user key combinations for each child component. The fields for CustomObject2 and CustomObject3 follow a similar pattern.
Child Components | Filterable Fields | User Key Field Combinations |
---|---|---|
CustomObject1 (parent) |
All |
CustomObject1Id |
ExternalSystemId |
||
IntegrationId |
||
Account |
AccountId |
CustomObject1AccountId |
AccountType |
ExternalSystemId |
|
CObj1AccountModifiedById |
IntegrationId |
|
CObj1AccountModifiedDate |
||
ExternalSystemId |
||
IntegrationId |
||
Location |
||
Name |
||
Region |
||
Attachment |
None |
Id |
ExternalSystemId |
||
FileNameOrURL and FileExtension |
||
Book |
None |
BookId |
BookName |
||
Contact |
ContactId |
CustomObject1ContactId |
CObj1ContactModifiedById |
ExternalSystemId |
|
CObj1ContactModifiedDate |
IntegrationId |
|
ContactType |
||
ExternalSystemId |
||
IntegrationId |
||
CustomObject2 |
CustomObject2Id |
CustomObject2Id |
CObj1CustomObject2ModifiedById |
ExternalSystemId |
|
CObj1CustomObject2ModifiedDate |
IntegrationId |
|
ExternalSystemId |
||
IntegrationId |
||
Name |
||
Type |
||
CustomObject3 |
CustomObject3Id |
CustomObject3Id |
CObj1CustomObject3ModifiedById |
ExternalSystemId |
|
CObj1CustomObject3ModifiedDate |
IntegrationId |
|
ExternalSystemId |
||
IntegrationId |
||
Name |
||
Type |
||
Opportunity |
CObj1OpportunityModifiedById |
OpportunityId |
CObj1OpportunityModifiedDate |
ExternalSystemId |
|
ExternalSystemId |
IntegrationId |
|
IntegrationId |
||
OpportunityId |
||
Portfolio |
CObj1PortfolioModifiedById |
PortfolioId |
CObj1PortfolioModfiedDate |
ExternalSystemId |
|
ExternalSystemId |
IntegrationId |
|
IntegrationId |
||
PortfolioId |
||
Team |
CustomObject1TeamId |
CustomObject1TeamId |
UserEmail |
UserExternalSystemId |
|
UserExternalSystemId |
UserIntegrationId |
|
UserId |
||
UserIntegrationId |
The following table details the picklists available for the CustomObject1 object. The fields for CustomObject2 and CustomObject3 follow a similar pattern.
Child Component | Field Name |
---|---|
Dealer |
Type |
Household |
Type |
Portfolio |
Type |
Vehicle |
Type |