Oracle CRM On Demand REST API Developer's Guide > Using the Oracle CRM On Demand REST API > Querying a Collection Resource >

Supported Query Characters


A query expression must not contain null values. Table 15 contains the query characters supported for Oracle CRM On Demand REST API.

Table 15. Supported Query Characters
Query Character
Description

" " or

' '

The quotation marks are used to define literals. Literals can be enclosed in either single quotation marks or in double quotation marks.

;

The semi-colon is used to separate multiple expressions. It must not be used at the end of an expression, if there are no further expressions.

\

The backslash is used to escape a special character.

*

The asterisk indicates a wildcard character.

Special Search Fields

Some field names are prefixed with CI_ to denote that they are special fields that provide better search functionality. CI_ fields have all upper case values and can be used for searching.

In the example below, AccountName is returned with capitalization:

/Rest/latest/Accounts/1QA2-22FKWR?fields=Id,CI_AccountName

LOVLanguageMode Querying

The Oracle CRM On Demand REST API supports using the LOVLanguageMode input argument to query the Oracle CRM On Demand Server. The LOVLanguageMode input argument determines whether query processing for picklist fields occurs using language independent codes (LIC) or language dependent codes (LDC). LIC is the default value.

LOVLanguageMode values are specified in the REST API request as a header field. For more information about supported HTTP and Oracle header fields, see Supported HTTP and Oracle CRM On Demand Header Fields.

If LIC is specified in the REST API request header field, then any values specified in the query must be language independent values. These values are used in the processing of the query and any values returned in the response are language independent values that can be used regardless of a user's language. If LDC is specified, then Oracle CRM On Demand converts any values that are specified in the query to LIC values before performing the query, and any values returned in the response are in the user's language.

For example, you have a custom picklist field where the English value is: One. In French, the value is: Un. The language independent value is: 'Option 1'. The following REST API request includes an LOVLanguageMode argument specifying a LIC return value for the custom picklist field:

  • URL: https://<host>/OnDemand/user/Rest/latest/Accounts/1QA2-22RT5M?fields=CustomPickList0
  • HTTP Method: GET
  • Content-Type: application/vnd.oracle.adf.resource+json
  • Accept-Language: fr
  • LOVLanguageMode: LIC
  • Request body: None

The following are the details for the response that returns the LIC value for the custom picklist:

  • HTTP Code: 200
  • Content-Type: application/vnd.oracle.adf.resource+json
  • Response body:

{
  "Accounts":[
  {
    "CustomPickList0": "Option1",
  ]
}

The following REST API request includes an LOVLanguageMode argument specifying a French LDC return value for the custom picklist:

  • URL: https://<host>/OnDemand/user/Rest/latest/Accounts/1QA2-22RT5M?fields=CustomPickList0
  • HTTP Method: GET
  • Content-Type: application/vnd.oracle.adf.resource+json
  • Accept-Language: fr
  • LOVLanguageMode: LDC
  • Request body: None

The following are the details for the response that returns a LDC value for the custom picklist:

  • HTTP Code: 200
  • Content-Type: application/vnd.oracle.adf.resource+json
  • Response body:

{
  "Accounts":[
  {
    "CustomPickList0": "Un",
  ]
}

Oracle CRM On Demand REST API Developer's Guide, Release 32 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices.