Create a deal team member

post

/crmRestApi/resources/11.13.18.05/deals/{dealsUniqID}/child/DealResources

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Deal Registrations resource and used to uniquely identify an instance of Deal Registrations. The client should not generate the hash key value. Instead, the client should query on the Deal Registrations collection resource in order to navigate to a specific instance of Deal Registrations to get the hash key.
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Access
    Maximum Length: 30
    The code indicating the access level of the deal team member. For example, View Only,Edit, or Full. A list of valid values is defined in the lookup ORA_MKL_DEAL_ACCESS_LEVEL.
  • The unique identifier of the deal registration.
  • Title: Registration Number
    Maximum Length: 30
    Public Unique Identifier of Deal Registration on the Deal Resource Team
  • The unique identifier of the deal team member.
  • Title: Function
    Maximum Length: 30
    The code indicating the function of a deal team member. For example, Channel Manager, engineering Owner, Executive Sponsor, Primary Salesperson, Product Specialist, Support Account manager, Technical Account Manager, Technical Marketing Manager, or Technical Specialist. A list of valid values is defined in the lookup ZCA_RESOURCE_FUNCTION.
  • Title: Owner
    Indicates whether the deal team member is the owner of the deal registration.
  • The unique identifier of the partner organization.
  • The unique identifier of the employee resource.
  • Title: User Name
    The login username of the deal team member associated with the deal registration.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : deals-DealResources-item-response
Type: object
Show Source
  • Title: Access
    Maximum Length: 30
    The code indicating the access level of the deal team member. For example, View Only,Edit, or Full. A list of valid values is defined in the lookup ORA_MKL_DEAL_ACCESS_LEVEL.
  • Read Only: true
    Maximum Length: 64
    The user who created the deal team member record.
  • Read Only: true
    The date and time when the deal team member record was created.
  • The unique identifier of the deal registration.
  • Title: Registration Number
    Maximum Length: 30
    Public Unique Identifier of Deal Registration on the Deal Resource Team
  • The unique identifier of the deal team member.
  • Title: Email
    Read Only: true
    Maximum Length: 320
    The e-mail address of the deal team member associated with the deal registration.
  • Title: Phone
    Read Only: true
    The phone number of the deal team member associated with the deal registration.
  • Read Only: true
    The date and time when the deal team member record was last updated.
  • Read Only: true
    Maximum Length: 64
    The user who last updated the deal team member record.
  • Read Only: true
    Maximum Length: 32
    The login of the user who last updated the deal team member record.
  • Links
  • Title: Function
    Maximum Length: 30
    The code indicating the function of a deal team member. For example, Channel Manager, engineering Owner, Executive Sponsor, Primary Salesperson, Product Specialist, Support Account manager, Technical Account Manager, Technical Marketing Manager, or Technical Specialist. A list of valid values is defined in the lookup ZCA_RESOURCE_FUNCTION.
  • Title: Owner
    Indicates whether the deal team member is the owner of the deal registration.
  • The unique identifier of the partner organization.
  • The unique identifier of the employee resource.
  • Title: Name
    Read Only: true
    Maximum Length: 360
    The name of the deal team member associated with the deal registration.
  • Title: Resource Number
    Read Only: true
    Maximum Length: 30
    Public Unique Identifier of Resource Party on the Deal Resource Team
  • Title: User Name
    The login username of the deal team member associated with the deal registration.
  • Read Only: true
    Maximum Length: 255
    The login username of the deal team member associated with the deal registration.
Back to Top

Examples

The following example shows how to create a deal team member by submitting a post request on the REST resource using cURL.

cURL Command

curl -u <username:password> \ -X POST -d @example_request_payload.json https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/deals/300100071405733/child/DealResources

Example of Request Body

The following shows an example of the request body in JSON format.

{
   "ResourceId": 100000016934086,
   "AccessLevelCode": "200"
}

Example of Response Body

The following shows an example of the response body in JSON format.

{
  DealResourceId: 300100071405737
  DealId: 300100071405733
  ResourceId: 100000016934086
  AccessLevelCode: "200"
  OwnerFlag: false
  ResourceName: "Anthony Mason"
  ResourceUsername: "AMASON"
  ...
}

Back to Top