Skip to content

Client-only Entities Limitations

  • The OData version for client-only entities has to be the same as that of the back end.

    Refer to OData Version And Client-only Entity for details.

  • Relationships between client-only entities and back-end entities are not supported.

    Refer to client-only relationship for details.

  • Singleton is not supported for client-only entities.

  • Action is not supported for client-only entities.

    Action defined in the client-only metadata is ignored as it is only supported in the OData server.

  • Function is not supported for client-only entities.

    Function defined in the client-only metadata is ignored as it is only supported in the OData server.

  • Deep update is not supported for client-only entities.

    Deep update is currently not implemented for Offline OData.

  • UploadCatetory is not applicable to client-only entity.

    The UploadCategory feature is designed for requests that are going to be uploaded to the back end and is not applicable to client-only entities.

  • TransactionID is not applicable to client-only entity.

    The TransactionID feature is designed for automatic batching of requests that will be sent to the back end and is not applicable to client-only entities.

  • Change allow_defining_query_removal endpoint configuration is not supported for client-only entities

    The client database should be cleared before changing the allow_defining_query_removal endpoint configuration.

  • Local-draft entity set with media entity or stream property is not supported.

Last update: June 15, 2023