Skip to content
Data Source component for JS apps using Kendo
JavaScript
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
LICENSE.md Commit with version 0.0.1 Mar 9, 2018
README.md Commit with version 0.0.1 Mar 9, 2018
kendo.data.kinvey.js
kendo.data.kinvey.min.js Commit with version 0.0.1 Mar 9, 2018

README.md

Kinvey Kendo UI DataSource

The Kinvey flavor of the Kendo UI DataSource component (named kinvey) allows you to bind to data stored in your Kinvey apps' collections. It supports filtering, sorting, paging, and CRUD operations.

Content at a glance:

Sourcing the Component

You can choose between several ways of sourcing the Kinvey flavor of Kendo UI DataSoruce, including downloading a local copy or directly referencing an online copy.

GitHub Repository

The source code of the component can be accessed in the following GitHub repository. You can download a ZIP archive containing the source code from the Releases folder.

Adding References

It is important to reference the Kinvey flavor of Kendo UI DataSource in your code after referencing Kendo UI and the Kinvey JavaScript SDK flavor that you chose.

<!-- Other framework scripts (cordova.js, etc.)  -->

<!-- Kendo UI Core / Kendo UI Professional -->
<script src="kendo.all.min.js"></script>

<!-- Kinvey JS SDK (HTML, PhoneGap, etc.) -->
<script src="...."></script>

<!-- Kinvey Kendo UI Data Source -->
<script src="kendo.data.kinvey.js"></script>

Initializing

To use the kinvey data source dialect, initialize the global Kinvey object first. You can connect the Kinvey flavor of Kendo UI DataSoruce to the backend either by specifying a collection name or by passing an instance of the Kinvey data store object.

Before initializing the Kendo UI Data Source instance, ensure you have reviewed the Kinvey Data Store Guide and that you are familiar with how the DataStore types in Kinvey work.

Initialize with Collection Name

You can connect a Kendo UI Data Source instance directly to a given Kinvey collection by supplying the name of that collection to the transport.typeName setting.

When initialized in that way, the Kendo UI Data Source uses a Kinvey Data Store of type Network internally.

var collectionName = "books";

var dataSourceOptions = {
    type: "kinvey",
    transport: {
        typeName: collectionName
    },
    schema: {
        model: {
            id: "_id"
        }
    },
    error: function(err) {
        alert(JSON.stringify(err));
    }
};

var dataSource = new kendo.data.DataSource(dataSourceOptions);

Initialize with a Data Store Instance

For advanced scenarios like data caching or offline data synchronization you need to handle a Kinvey data store of type Cache or Sync. You can explicitly instruct the Kendo UI DataSource instance to work with a Kinvey data store instance of any of these types.

When initializing Kendo UI DataSource in this way, you need to manage yourself the state of the store and to push, pull, and sync the entities to/from the server in a suitable place of your application. Kendo UI DataSource only fetches items that are available locally on the device.

// initialize the Kinvey data store
var booksSyncStore = Kinvey.DataStore.collection(collectionName, Kinvey.DataStoreType.Sync);
 
// pull and push items to/from the server in a suitable place in your code

// initialize DataSource with the dataStore option
var dataSourceOptions = {
    type: "kinvey",
    transport: {
        dataStore: booksSyncStore
    },
    schema: {
        model: {
            id: "_id"
        }
    },
    error: function(err) {
        alert(JSON.stringify(err));
    }
};

var dataSource = new kendo.data.DataSource(dataSourceOptions);

With a Kinvey data store of type Cache, the Kendo UI DataSource instance calls the server directly without consulting the local cache.

Filtering

Filtering is enabled setting the serverFiltering configuration option to true and passing a filter object to the filter option.

var dataSourceOptions ={
    type: 'kinvey',
    // ommitted for brevity
    serverFiltering: true,
    filter: { field: 'author', operator: 'eq', value: 'Lee' }
}

The Kinvey dialect supports a selected subset of the Kendo UI DataSource filter operators, namely:

  • eq
  • neq
  • isnull
  • isnotnull
  • lt
  • gt
  • lte
  • gte
  • startswith
  • endswith

In addition to the standard Kendo UI Data Source filtering operatiors, the Kinvey dialect adds support for the following Kinvey-specific operators:

  • isin—value is an array of possible matches. Example: { field: 'author', operator: 'isin', value: ["Author1", "Author2", "Author3"] }
  • isnotin—an inversion of the isin logic returning all matches that are not in the specified array, including those entities that do not contain the specified field.
{
    field: "author",
    operator: "isin",
    value: ["John Steinbeck", "Leo Tolstoy", "Gore Vidal"]
}

Sorting

Sorting is enabled by setting the serverSorting configuration option to true and passing a sort object to the sort option. The Kinvey dialect supports all Kendo UI DataSource sorting configuration options.

var dataSourceOptions = {
    type: 'kinvey',
    // ommitted for brevity
    serverSorting: true,
    sort: { field: 'author', dir: 'asc' }
}

Paging

Paging is enabled by passing true to the serverPaging configuration option.

Setting the pageSize configuration option is sufficient for most uses. You can also set the page option to request a specific page. The Kinvey dialect supports all DataSource paging configuration options.

var dataSourceOptions = {
    type: 'kinvey',
    // ommitted for brevity
    serverPaging: true,
    pageSize: 20
};

When serverPaging is enabled, a separate request to determine the count of the entities on the server is made before each request for the respective page of entities.

Unsupported Configuration and Operations

The following configuration options of the DataSource component are not supported for server execution by Kinvey.

  • Standard Kendo UI DataSource filter operators for server filtering:
    • contains
    • doesnotcontain
    • isempty
    • isnotempty
  • Specifying a subset of fields to be returned.
  • Sending additional headers with the request.
  • schemaschema.aggregates and schema.groups are not supported. The component already takes care of schema.data, schema.total, and schema.type for you so you do not need to set them explicitly.
  • batch
  • serverGrouping—you can use client-side grouping instead.
  • serverAggregates——you can use client-side aggregation instead or request the data from the _group Kinvey endpoint.
  • transport.parameterMap
  • inPlaceSort—use the serverSorting option instead.
  • offlineStorage—instead initialize and work with a Kinvey DataStore of type SYNC.
  • type—only the kinvey value is supported.

License

See LICENSE for details.

You can’t perform that action at this time.