DevExtreme React - Errors and Warnings API

This error may occur in UI components that include the "summary" feature. For example, if you specify a not-valid summaryType for the DataGrid UI component, this error will occur.

Acceptable OData versions are the following: 2, 3, 4.

The available operators are: "!", "=", "<>", ">", ">=", "<", "<=", "startswith", "endswith", "contains", "notcontains".

For more information on filtering syntax, see the Filtering topic.

The thenby() method can only follow the sortBy(getter), sortBy(getter, desc), thenBy(getter, desc), or another thenBy(getter) method.

Specify the store's key property. For the ODataStore, specify the keyType property as well.

This property takes on an array only.

This error is specific for the LocalStore and ArrayStore Data Stores. You can specify a compound key expression for these Data Stores by assigning an array to the key configuration property. If a key is undefined, it will be generated automatically based on the specified key expression. However, a key cannot be generated for a compound key expression. So, make sure keys are specified for data with compound key expressions.

Ensure that a value can be found for any key passed to the byKey(key) function.

This error is specific to the CustomStore Data Store, because this type of a DevExtreme Store does not support the creation of queries.

CustomStore requires that you implement its methods manually. To resolve the issue in question, implement the method specified in the error message you see in the browser console. See the CustomStore API reference for code examples.

This error is specific to the CustomStore Data Store.

When creating a LocalStore instance, specify the name configuration property, which is required for identifying the data within the storage.

This error is specific for the ODataStore and ODataContext objects. The keyType property accepts the following values: String, Int32, Int64, and Guid.

This error is specific to ArrayStore Data Stores.

This error is specific to ODataStore data stores.

Specify a filter expression that does not contain different group operators in a single group.

The following example illustrates invalid and valid filter expressions.

//Invalid filter expression
var filterExpression = [
    [ "name", "contains", "A"],
    "and",
    ["team", "=", "Accounting"],
    "or",
    ["team", "=", "Management"]
]

//Valid filter expression
var filterExpression = [
    [ "name", "contains", "A"],
    "and",
    [
        ["team", "=", "Accounting"],
        "or",
        ["team", "=", "Management"]
    ]
]

This error is specific to the CustomStore Data Store.

This error occurs if the load method has resolved the Promise with an unspecified or empty totalCount, or if the totalCount method was not defined.

var store = new DevExpress.data.CustomStore({
    // . . .
    load: function (loadOptions) {
        var deferred = $.Deferred();
        $.get('url/to/the/resource', loadOptions).done(function (response) {
                deferred.resolve({ data: response.data, totalCount: response.totalCount });
        });
        return deferred.promise();
    }
});

See Also

• DataGrid - Custom Sources

This error is specific to the CustomStore Data Store.

This error occurs if the load method has resolved the Promise with an unspecified or empty groupCount.

var store = new DevExpress.data.CustomStore({
    // . . .
    load: function (loadOptions) {
        var deferred = $.Deferred();
        $.get('url/to/the/resource', loadOptions)
            .done(function (response) {
                deferred.resolve({ data: response.data, groupCount: response.groupCount });
            });
        return deferred.promise();
    }
});

See Also

Custom Sources - Load Data

To avoid this error, disable the search and filter functions for non-string data fields.

The server should return an array or an object with the data field holding an array.