Configure Your App Data Provider

The Telerik Platform Views service(formerly Screen Builder) lets you use your own data content by connecting to a data provider. You can use the data content for the corresponding data-bound view types in your app.

This article describes how to add and use a data provider in the Telerik Platform Views service.

Add a Data Provider

To add your data provider, you need to go to the Data Providers tab and click the Add Provider button.

  • For Telerik Backend Services, you need to complete the following fields:
Field Description Comments
App Choose your Telerik Platform app that holds your data. After adding an app you need to add data in it. For more information, please, read this help article how to store data in the cloud with Backend Services.
Provider Name Give your data provider a custom name for your convenience and quick identification.
Enable offline mode Enable your Telerik Backend Services project to work in offline mode and synchronize when the device with your mobile app is online. Note: When you build your app with AppBuilder, you need to enable the Network Information Apache Cordova plugin in order to use the offline support. For more information please refer to the reference link below for using Core Apache Cordova Plugins with AppBuilder.
  • For Progress Sitefinity, you need to complete the following fields:

Currently, this option is only available when you build a hybrid mobile app.

Field Description Comments
Provider Name Give your data provider a custom name that will be used to create the data objects in the app code.
Provider Title Give your data provider a custom title that will be displayed when you reference it from the view types.
Sitefinity Url Set this to the address of your Sitefinity frontend via a secure protocol (https:) and add /api/default at the end. For example: https://www.mywebsite.com/api/default Verify that you are running Sitefinity 9.1 or later.
  • For Progress Data Service, you need to complete the following fields:

Currently, this option is only available when you build a hybrid mobile app.

Field Description Comments
Provider Name Give your data provider a custom name that will be used to create the data objects in the app code. The Name can only be letters and numbers. No spaces are allowed.
Provider Title Give your data provider a custom title that will be displayed when you reference it from the view types.
Service URI Set this to your remote data service. It's the URI of the Web application that hosts the remote data service to which you want to connect your user login sessions. E.g. http://Your-IP-Address:8980/MyMobileWebAppl
Catalog URI Specify one Progress Data Service Catalog pathname that describes the Mobile service provided by the remote data service.
Catalog File Get the Progress Data Service's Catalog JSON file by specifying its URI or by uploading the file. After reading this file, the Telerik Platform Views service creates drop-down lists with the available options for the Resources and Fields of your Progress Data Service data provider. You can select the Resource and the Fields from these drop-downs instead of entering them manually. Uploading the Catalog file from a URI works only if the URI is secure link (https://). If your catalog is served via a normal link (http://), you need to manually upload the file. For security reasons it is not possible to download a catalog directly from an insecure source. If the Progress Data Service data provider requires authentication, you need to provide your credentials before uploading the Catalog file from URI.
Authentication model Should be set to either: "Anonymous", "Basic", or "Form". It specifies the type of authentication that the Progress backend server requires. If you select "Basic" or "Form", the users of the app will have to authenticate before reading data from the Progress data server, and the Telerik Platform Views service will offer you to add an Authentication view for you by checking a check-box. When you check it the Views service will add the necessary view and will load its property grid for you. Open the "Sign In screen -> Redirect" section and specify the view which should be loaded on successful sign-in. If the view is not available, create it first and then return to the Authentication view.

If your Service and Catalog URIs are HTTP, you have to open the simulator in a new window in order to see data from them in the simulator.

  • For JSON via REST, you need to complete the following fields:

Currently, this option is only available when you build a hybrid mobile app.

Field Description Comments
Provider Name Give your data provider a custom name that will be used to create the data objects in the app code. The Name can only be letters and numbers (No spaces are allowed).
Provider Title Give your data provider a custom title that will be displayed when you reference it from the view types.
Data Url Enter your endpoint URL. Note: We recommend using the HTTPS protocol to access your endpoint. Displaying your data in the App simulator requires HTTPS.
  • For OData via REST, you need to complete the following fields:

Currently, this option is only available when you build a hybrid mobile app.

Field Description Comments
Provider Name Give your data provider a custom name that will be used to create the data objects in the app code. The Name can only be letters and numbers (No spaces are allowed).
Provider Title Give your data provider a custom title that will be displayed when you reference it from the view types.
Data Url Enter your endpoint URL. Note: We recommend using the HTTPS protocol to access your endpoint. Displaying your data in the App simulator requires HTTPS.

Use Your Data Provider

After configuring your data provider, you need to add views and bind them to the data provider, its content types and their fields. This will let you automatically show data from the data provider in your app. To learn which view types can be data-bound, check the Types of Views section in Working with Views.

In data bound views, specifying a data provider and content types to which to bind your view is mandatory.

Based on your data provider, you need to keep in mind the following Views service specifics:

Progress Sitefinity

  • If your Sitefinity backend is configured to require authentication, you need to be authenticated with the Sitefinity backend (for example, http://www.website.com/sitefinity) in the current browser session. Otherwise, the Views service will not be able to access your Sitefinity content types and will not be able to generate a list of Progress Sitefinity-based views.
  • To be able to view data from your Sitefinity in the device simulator, you need to create and configure an Authentication view. In this Authentication view, you need to provide frontend credentials for Sitefinity (for example, http://www.mywebsite.com).
  • If a content type has multiple data providers when you have a multi-site Sitefinity setup, you might need to configure Source for the content type to which you are trying to bind your view. If needed, the Views service will prompt you to select Source when you configure the data binding for your views.

Progress Data Service

  • When prompted to specify which Content Type you want to use, you need to provide the name of the resource (found in a Progress Data Service's Catalog file) for which the underlying data provider instance is created.

JSON

  • When you add a Master Detail view, you can specify the Source path property. This property makes it easier for you to enter the Fields names in the data list when you have arrays of objects in your data provider and want to use them. You have to enter the source path to the array and then just type the objects names when adding the master detail list fields. Otherwise, you need to type the entire path every time you enter a new object from this array as a master detail field.

See Also

Start a free trial Request a demo
Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.