Team
The team object stores information on the team that is assigned to a particular record type. In this way, a team of employees can, for example, be dedicated to an account or contact, ensuring that the activities, service requests, leads, and opportunities surrounding that account or contact are always kept up-to-date and are attended to regularly.
Parent Object
Account, Accreditation, Application, Business Plan, Certification, Contact, Course, CustomObject, Deal Registration, Event, Exam, Financial Account, Financial Plan, Household, Lead, MDF Request, Objective, Opportunity, Order, Partner, Portfolio, Sample Request, Service Request, Special Pricing Request.
Fields
The following table details the required and read-only fields for the team child object.
Field Name | Type |
---|---|
record_typeAccess |
Required |
UserId |
Required |
LoginName |
Read-only |
UserFirstName |
Read-only |
The following table details the pick map fields for the team child object.
Pick Map Field | Maps To |
---|---|
UserLastName |
UserFirstName |
record_typeAccess |
record_typeAccessId |
UserAlias |
UserId |
UserEmail |
UserId |
UserExternalSystemId |
UserId |
FullName |
UserId |
The following table provides a list of the user key combinations for the team child object.
User Key Field Combinations |
---|
UserId |
UserExternalSystemId |
UserEmail |
UserAlias |
The following table details the picklists available for the team child object.
Field Name |
---|
TeamRole |