OData version 2 is supported for the offline OData feature, with several
Android, iOS, and Windows supports a mix of OData 2.0 and 4.0 metadata annotations for
defining additional characteristics or capabilities of a metadata element, such as a
service, entity type, property, function, action, or parameter. For example, you can
now define a valid range of values for a particular property. Windows supports 2.0.
For details, see the Native OData API documentation for your platform, which is
installed with the SDK.
- There is no support for these OData concepts:
- Function imports.
- ETags when using the if-match/if-none-match headers when performing
- Modifying properties or complex type properties by addressing them in
- Metadata annotations are not populated in the Metadata object.
- The Offline OData feature has the following limitations:
- The maximum length (MaxLength) of Edm.String key properties is 10922 characters and
MaxLength needs to be present in the metadata.
- The maximum length (MaxLength) of Edm.Binary key properties is 32768 bytes and MaxLength
needs to be present in the metadata.
- The Android and Windows offline store does not support mutual authentication using
X509Certificates loaded from the System KeyStore/KeyChain. It does
support X509Certificates which are provided from a secure file store.
The secure file store may be an SAP component, or 3rd party component,
so long as the X509Certificate is supplied to the X509KeyManager when
- The navigation property used for the deep insert must refer to at most
- Media resources can not be read in a batch request.
- The Offline OData SDK for Windows does not support using client
certificates to perform mutual authentication with the server.