Get a lightbox document type

get

/crmRestApi/resources/11.13.18.05/lightboxDocumentTypesLOV/{lightboxDocumentTypesLOVUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Lightbox Document Types resource and used to uniquely identify an instance of Lightbox Document Types. The client should not generate the hash key value. Instead, the client should query on the Lightbox Document Types collection resource in order to navigate to a specific instance of Lightbox Document Types 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 : lightboxDocumentTypesLOV-item-response
Type: object
Show Source
  • Title: Add to Cart
    Read Only: true
    Indicates if the lightbox document type supports cart functions. If True, then the documents using this lightbox document type can be added to cart.
  • Content Types
    Title: Content Types
    Read Only: true
    The list of MIME content types that are allowed for the Sales Lightbox document type.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the record.
  • Title: Creation Date
    Read Only: true
    The date when the record was created.
  • Title: Description
    Read Only: true
    Maximum Length: 240
    The description of the lookup in the application.
  • Title: Last Updated Date
    Read Only: true
    The date and time when the record was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the record.
  • Title: Last Update Login
    Read Only: true
    Maximum Length: 32
    The login associated with the user last updated the record.
  • Title: Lightbox Document Type
    Read Only: true
    Maximum Length: 30
    The unique code for the lightbox document type.
  • Links
  • Title: Type Description
    Read Only: true
    Maximum Length: 80
    The display value for the lookup in the application.
  • Title: Placeholder Image
    Read Only: true
    The path to a placeholder image that is displayed when the document has no thumbnail.
Nested Schema : Content Types
Type: object
Title: Content Types
Read Only: true
The list of MIME content types that are allowed for the Sales Lightbox document type.
Back to Top