Links between OData entities are described by a navigation property. Setting navigation properties between OData entities When the IsPublic property for an updatable view is set to TRUE, that view is exposed as a top-level OData entity. OData entities are based on the concept of an updatable view. PropertyInfo.SetValue() for all specified fields in the request.Methods (listed in the order in which they are called) The following table summarizes the validate methods that the OData stack calls implicitly on the corresponding data entity. eq 'usrt'&cross-company=true Validate methods This option will return data from all companies that the user has access to.Įxample: To filter by a particular company that isn't your default company, use the following syntax: To see data from outside the user's default company, specify the ?cross-company=true query option. EnumType is support in $metadata.īy default, OData returns only data that belongs to the user's default company. For more information, see OData batch requests. Batch requestsīatch requests are supported in the OData service. The operators 'has' and 'in' are not supported.įor more information, see OData operators. It has been implemented as a wildcard character. You can also use the Contains option with $filter requests. There are built-in operators for $filter: The OData service supports serving driven paging with a maximum page size of 10,000.įor more information, see: OData actions that are bound to entities. $expand (only first-level expansion is supported).The following are the high-level features that are enabled for the OData service, per the OData specification.ĬRUD support is handled through HTTP verb support for POST, PATCH, PUT, and DELETE. Supported features from the OData specification When working with data entities using OData, all fields in the entity key must be provided to make a successful OData call.Ĭode examples for consuming OData services are available in the Microsoft Dynamics AX Integration GitHub repository. Detailed labs for this feature are on the LCS methodology. It supports complete CRUD (create, retrieve, update, and delete) functionality that users can use to insert and retrieve data from the system. This endpoint exposes all the data entities that are marked as IsPublic in the Application Object Tree (AOT). The navigation from a customer to that customer's reservations data/Customers("")Ī single entity from the entity collection The root service endpoint for OData entities The following table describes the resources and the corresponding URLs in the Fleet Management sample. OData actions added via extensions are currently not supported. The URL for the service root on your system has the following format: /data To see a list of all the entities that are exposed, open the OData service root URL. The public OData service endpoint enables access to data in a consistent manner across a broad range of clients. OData: Data access for the web, the cloud, mobile devices, and more It enables integration by using the HTTP protocol stack.įor more information about OData, see the following webpages.It enables broad integration across products.It provides a simple and uniform way to share data in a discoverable manner.It lets developers interact with data by using RESTful web services.OData applies web technologies such as HTTP and JavaScript Object Notation (JSON) to provide access to information from various programs. The purpose of OData is to provide a protocol that is based on Representational State Transfer (REST) for create, read, update, and delete (CRUD) operations.
OData is a standard protocol for creating and consuming data. This article provides information about Open Data Protocol (OData) and explains how you can use OData V4 to expose updatable views.
0 kommentar(er)
