This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Compatible data types for field and XML element maps

When mapping an XML element to a BMC Remedy AR System field, Developer Studio allows only compatible data types, both for consuming and publishing.

BMC Remedy AR System data types

XML schema data types

Character

string, duration, anyURI, QName, NOTATION, normalizedString, token, language, NMTOKEN, Name, NCName, ID, IDREF, ENTITY, integer, positiveInteger, nonPositiveInteger, negativeInteger, nonNegativeInteger

Status History

string

Diary

string

Date/Time

dateTime

Date

date, gYearMonth, gYear, gMonthDay, gDay, gMonth Defaults: YEAR - 1000 (leap year), month - 01, day - 01

Time

time

Currency (value)

decimal

Currency (code)

string

Currency (conversion date)

dateTime

Integer

int, long, unsignedLong, unsignedInt, boolean, short, byte, unsignedShort, unsignedByte

Real

double, float

Decimal

decimal

Drop-Down, Radio, Check Box

string

Attachment (name)

string

Attachment (data)

base64Binary

Attachment (original size)

int, long, unsignedLong, unsignedInt, boolean, short, byte, unsignedShort, unsignedByte

Note

BMC Remedy AR System web services do not support list and union data types. BMC Remedy AR System converts list data types IDREFS, ENTITIES, and NMTOKENS to strings.

The following complex BMC Remedy AR System fields are treated as exceptions:

  • When you retrieve a diary field from BMC Remedy AR System, the diary field is treated as a long character field containing all the historical diary entries separated by a special separator character. When you send a diary field to BMC Remedy AR System, you send only the current entry.
  • The Status History field is treated similarly to a diary field, but you cannot send a status history entry to BMC Remedy AR System.
  • Each currency and attachment field consists of three parts, and each part needs to be mapped separately (see the following figure).

    Mapping currency and attachment fields
    (Click the image to expand it.)

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments