The mock server only supports the JSON format for representing the resources it exposes, such as collections, entries, and links.
The mock server cannot mock more than one service per application.
The following table lists the OData features that are supported by the mock server.
Feature |
Status |
---|---|
CRUD calls |
Supported |
Navigations |
Supported; only single navigations are supported, e.g. "/a()/b/". Further navigation chaining is not supported. |
Query String options: |
|
- Orderby System Query Option ( |
Supported |
- Top System Query Option ( |
Supported |
- Skip System Query Option ( |
Supported |
- Filter System Query Option ( |
Supported; |
- Expand System Query Option ( |
Supported |
- Select System Query Option ( |
Supported |
- Inlinecount System Query Option ( |
Supported |
- Format System Query Option ( |
Supported; only JSON format is allowed |
Batch processing |
Supported |
Multiple services |
Supported; we recommend to create one Mock Server instance per service |
Update via |
Supported |
ETag handling |
Supported |
The following table lists the OData features that are not supported by the mock server.
Feature |
Status |
---|---|
Service operations (function imports) |
Unsupported, but can be extended |
Annotations |
Unsupported |
Getting individual properties of an entity ( |
Unsupported |
|
Unsupported |
|
All dates have to be either before 2017 or after; you cannot use mixed values |
|
Unsupported |
Key of type |
Unsupported |
Key of type |
Unsupported |
|
Unsupported For more information see Addressing Links between Entries and Referencing Requests in a Change Set on http://www.odata.org/. |
Multiple navigation properties |
Unsupported |
Response in byte array format |
Unsupported |
Combination of the system queries |
Unsupported |
Filter query string operator ( |
Does not support input strings ( |
Key values containing a comma |
Unsupported |
System query option |
Unsupported |
Filter query |
Unsupported |