Web Service Mobile Business Object Limitations

This section describes known limitations when binding an MBO to Web service data sources.

Unsupported types

These Web service types are currently unsupported:

These complex datatype scenarios are currently unsupported for Web service MBOs:

This structure is not supported:

Structure A[]: 
x of type struct B[]. 
(y of type struct C[])

but does support:

Struct A[]: 
< scalar type > x, 
y of type Struct B[]

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.
For WSDL and SOAP Web service data sources , if an Update operation that uses the Apply results to the cache cache update policy does not have an XSLT, an error message displays:
```
The ''UPDATE'' operation 'Customer- > updateStudent()' 
with ''Apply results to the cache'' cache update policy does not 
have XSLT. 
```