Automatically mapping XML elements
The typical procedure is to create the XML elements and then map them to the fields. However, if you are creating a flat mapping, you can combine these steps into this simple process, which automatically maps XML elements:
- Remove the fields that you do not want to map, or remove a mapping (as described in the following procedures).
- Click the Generate Schema button on the Mapping dialog box.
To remove an existing field from the mapping list
- Open the web service in Developer Studio.
- View the mapping table under WSDL Ports > Port > WSDL Operations > Operation.
- In the Form/Field column, highlight the field name you want to remove.
- Press Backspace or Delete to remove the field name.
The corresponding XML element is not removed.
To remove a mapping
- Open the web service in Developer Studio.
- View the mapping table under WSDL Ports > Port > WSDL Operations >Operation.
- In the mapping table, right-click the mapping you want to remove.
Each mapping is represented by a row in the table. - Click Remove Selected.
Compatible data types for field and XML element maps
When mapping an XML element to an AR System field, Developer Studio allows only compatible data types, both for consuming and publishing.
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 |
AR System web services do not support list and union data types. AR System converts list data types IDREFS, ENTITIES, and NMTOKENS to strings.
The following complex AR System fields are treated as exceptions:
- When you retrieve a diary field from 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 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 AR System.
- Each currency and attachment field consists of three parts, and each part needs to be mapped separately (see the following figure).
