Get a deal team member

get

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

Request

Path Parameters
  • The unique identifier of the deal team member.
  • 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.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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 get a deal team member by submitting a get request on the REST resource using cURL.

cURL Command

curl -u <username:password> \ -X GET https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/deals/300100071405733/child/DealResources/300100071405734

Example of Response Body

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

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

Back to Top