Key Properties

Properties of keys vary with the objects that use them and the operations they perform.

Property Description
Name The name of the key.
Type The datatype of the key, one of:
  • string
  • int
  • double
  • decimal
    Note: NaN (not a number) values are not supported.
  • bool
  • DateTime
    Note: Null values in the DateTime type are not supported for BlackBerry 5 devices.
  • list: can be bound to relationships or to nothing. Keys of other types cannot be bound to relationships. List type keys can also be bound to MBO object query results, which returns multiple objects. List type keys have one or more child keys to which they are bound.
Sent by server Enables the key to be sent by the server as specified in the Input Data Binding properties below. By default, the key is sent by the device instead.
Mobile business object The MBO associated with the key (for example, an MBO referenced in an object query in the application).
Input Data Binding The data that is bound to the key. One of:
  • Mobile business object attribute – name of an attribute defined in the MBO.

    Optionally (if available), convert the attribute value to UTC.

  • Mobile business object relationship – relationship currently defined for the MBO (list type keys only).
  • Mobile business object query results – result of an MBO object query.
  • Hard-coded value – fixed value for the message sent from the server to the client.

    When the message is sent by the server to the client, rather than getting the value of the key from a source like an MBO attribute, it uses the fixed value you enter here.

    Note: You can return hard-coded key values only from server-initiated starting points, not from online requests.
  • User-defined – data that the user provides in the current control.
  • Extraction rule – name of a defined extraction rule.