Generic REST Data Sources

The REST data source does not support the consuming of service metadata or a schema and you have to manually add and configure all fields and properties.

Getting Started

When you add or edit fields, you have to specify their name, label and type, and based on the selected type to choose the right editor for your filed.

To define the supported data source actions, click Data Source Actions to display an expandable list of the Create, Destroy, Read, and Update actions. For all actions you can specify their:

  • Type—Selects the REST verb for the action. For example, the default verb for the Create action is POST.
  • URL—Enters the URI for the action object that is relative to the Base URI which is specified for the data provider.

Editing Generic REST Data Source

Setting the Fields

The REST data source provides specific settings which are helpful when the endpoint returns or expects the data in a different way:

  • Id Field—Selects a data source field that functions as a primary key to the data source by using the drop-down list.
  • Data Field—Represents a field in the server response that returns one or more rows to the data source.
  • Total Field—Represents a field in the server response that contains the total number of rows which are returned in the response.
  • Client-side processing—Indicates whether the application will retrieve all or paged data from the endpoint. If the server-side operations are used, the data source uses the value which is returned by the Total field to manage the paging of data on the server.
In this article
Not finding the help you need?

Unite UX direction is evolving!

Dear friends, after gaining plenty of great experience and feedback through working with you, our direction evolves to better serve your needs. Our mission to bridge the design to development gap remains unchanged. The way to solve it, though is new. Visit our webpage to meet the new Unite UX: The collaborative design to development UI components builder.

Explore the New Unite UX