DevExtreme jQuery - Errors and Warnings API

This section lists errors and warnings that may occur when using the DevExtreme Data Library.

E4000

Signals that a data-related error occurred in external code with which the DevExtreme data works.

E4001

Occurs when the an unknown aggregating function is specified.

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.

E4002

Occurs when the unsupported OData version in specified for the ODataStore or ODataContext object.

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

E4003

Occurs when an unknown filter operation is used.

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

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

E4004

Occurs when the thenby() method is called before the sortby() method.

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

E4005

Occurs when calling a key-dependent method of a store with an unspecified key property.

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

E4006

Occurs when the value that is set to the data configuration property of the ArrayStore object is not an array.

This property takes on an array only.

E4007

Occurs when an auto-generated key is required for a Data Store with a compound key expression.

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.

E4008

Occurs when items with duplicated keys are inserted.

E4009

Occurs in a store when its byKey(key) function does not return a value.

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

E4010

Occurs when creating the Query object by using the createQuery method of a CustomStore.

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

E4011

Occurs when an unimplemented CustomStore method is called.

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.

E4012

Occurs when a method implemented for a Custom Store returns an unexpected result.

This error is specific to the CustomStore Data Store.

E4013

Occurs when the name property is not specified for a LocalStore instance.

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

E4014

Occurs when an unknown key type is detected.

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

E4015

Occurs when calling the objectLink(entityAlias, key) method and passing an entity alias that is not registered for the given ODataCOntext object.

E4016

Occurs when the compileSetter(expr) method is called with this passed as a parameter.

E4017

Occurs when calling the update(key,values) method to modify a key(s).

This error is specific to ArrayStore Data Stores.

E4018

Occurs when the server returns a non-numeric value after the totalCount method of an ODataStore instance is called.

This error is specific to ODataStore data stores.

E4019

Occurs if a filter expression contains different group operators within a single group.

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

The following example illustrates invalid and valid filter expressions.

JavaScript
//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"]
    ]
]

E4020

Occurs if the store.type property of a DataSource instance holds an unknown store type.

E4021

Occurs if the total count of data records (totalCount) was not obtained when loading data.

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.

jQuery

You can solve the problem by implementing the load method in the following manner.

index.js
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

E4022

Occurs if the count of first-level groups (groupCount) was not obtained when loading data.

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.

jQuery

You can solve the problem by implementing the load method in the following manner.

index.js
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

E4023

Occurs in the XmlaStore if the received data cannot be parsed into XML.

E4024

Occurs in the ODataStore when a string function ("startswith", "endswith", "contains", "notcontains") is used to search or filter a non-string data field.

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

W4000

Occurs when data returned from a server has an incorrect structure.

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

W4001

Occurs in the ODataStore when a single field is assigned both to the keyType and fieldTypes properties. Remove the field's name from one of the properties.

W4002

Produced by the XmlaStore when an error occurs on loading data for certain cells. For details on the error, refer to the XMLA specification.