Get all partner contact managers

get

/crmRestApi/resources/11.13.18.05/partnersLOV/{partnersLOVUniqID}/child/partnerContactManagersLOV

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Partners resource and used to uniquely identify an instance of Partners. The client should not generate the hash key value. Instead, the client should query on the Partners collection resource in order to navigate to a specific instance of Partners 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>
  • This query parameter is used to fetch resources which are effective dated as of the specified start date. The value of this query parameter is a string having a date in yyyy-MM-dd format
  • 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
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • ManagersLOVFinder: Find all contacts defined as Manager Resources.
      Finder Variables:
      • BindSysEffectiveDate; string; The effective date.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • 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
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • AttachmentEntityName; string; The name of the attachment entity. This attribute is internal.
    • ChildRoleRelateId; integer; The unique identifier of the child role. This attribute is internal.
    • DenormLevel; number; The denormination level. This attribute is internal.
    • DenormMgrId; integer; The denormination manager id. This attribute is internal.
    • EffectiveEndDate; string; The date when the role of the manager ends. This attribute is internal.
    • EffectiveStartDate; string; The date when the role of the manager starts. This attribute is internal.
    • EndDateActive; string; The date when the record ends. This attribute is internal.
    • FndTreeCode; string; The tree code. This attribute is internal.
    • FndTreeStructureCode; string; The tree structure code. This attribute is internal.
    • FndTreeVersionId; string; The unique identifier of the tree version. This attribute is internal.
    • GroupId; integer; The unique identifier of the group. This attribute is internal.
    • GroupMemberId; integer; The unique identifier of the group member.
    • HierarchyType; string; The hierarchy type. This attribute is internal.
    • ImageURL; string; The url of the image. This attribute is internal.
    • ManagerName; string; The name of the manager.
    • Name; string; The name of the partner contact manager. This attribute is internal.
    • ObjectVersionNumber; integer; The object version number. This attribute is internal.
    • OrganizationId; integer; The unique identifier of the organization. This attribute is internal.
    • ParRoleRelateId; integer; The unique identifier of the partner role related. This attribute is internal.
    • ParentOrgId; integer; The unique identifier of the parent organization. This attribute is internal.
    • ParentResourceId; integer; The unique identifier of the parent resource. This attribute is internal.
    • PartyId; integer; The unique identifier of the party associated with the partner contact.
    • PartyName; string; The name of the party associated with the partner contact.
    • PartyType; string; The party type. This attribute is internal.
    • PersonFirstName; string; The first name of the person. This attribute is internal.
    • PersonLastName; string; The last name of the person. This attribute is internal.
    • ResourceId; integer; The unique identifier of the resource. This attribute is internal.
    • ResourceName; string; The resource name. This attribute is internal.
    • RoleCode; string; The code indicating the role of the partner contact.
    • RoleId; integer; The unique identifier of the partner contact role.
    • RoleName; string; The name of the partner contact role.
    • RoleRelateId; integer; The unique identifier of the related role. This attribute is internal.
    • RoleResourceId; integer; The unique identifier of the role resource.This attribute is internal.
    • RoleResourceType; string; The role resource type. This attribute is internal.
    • StartDateActive; string; The date when the record starts. This attribute is internal.
    • SysEffectiveDate; string; The system effective date. This attribute is internal.
    • TreeCode; string; The tree code. This attribute is internal.
    • TreeEffectiveEndDate; string; The effective end date. This attribute is internal.
    • TreeEffectiveStartDate; string; The effective start date. This attribute is internal.
    • TreeStatus; string; The tree status. This attribute is internal.
    • TreeStructureCode; string; The tree structure code. This attribute is internal.
    • TreeVersionId; string; The unique identifier of the tree version.This attribute is internal.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
Header Parameters
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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 : partnersLOV-partnerContactManagersLOV
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : partnersLOV-partnerContactManagersLOV-item-response
Type: object
Show Source
Back to Top