Understand Web service mobile business object (MBO) limitations.
This section describes known limitations when binding an MBO to Web service data sources.
Unsupported types
These Web service types are currently unsupported:
- Recursive definitions of element types.
-
Soapenc encoded arrays.
-
Derived types using List/Union constructs.
-
anyType
- gDay, gYear, gMonth, gYearMonth
-
HexBinary datatypes are not supported, instead use base64Binary.
- Unsupported datatypes are either ignored or recognized as a String.
Unsupported derived or complex types
These complex datatype scenarios are currently unsupported for Web service MBOs:
Unsupported schema constructs
- Schema used as element data (i.e. an element is a schema).
Unsupported Web service operations
MBO Mapping restrictions
MBO attribute to Web service column mapping restrictions include:
- If an attribute maps to a table column and is intended to be an alternate key, specify a smaller maxlength value for it as compared to any other non-key attribute (try to match the actual length to the enterprise information system (EIS) column to which it maps). This is a client-side implementation requirement, because when the row size (addition of all column sizes(maxlengths)) exceeds the page size, the client converts columns with higher maxlengths to long varchar. This creates a run-time exception if the client creates an index on each column which is or part of an alternate key.
- Do not define alternate keys on columns that are long varchar/binary datatypes since device databases (Ultralite) do not support it.