A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://js.devexpress.com/Vue/Documentation/ApiReference/UI_Components/Errors_and_Warnings/ below:

Vue Errors and Warnings API

This section lists errors and warnings that may occur in UI components.

A DataGrid internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

A DataGrid internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

A DataGrid internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

A DataGrid internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

Occurs if a public method is already registered.

A DataGrid internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

Occurs if a custom template for the text field of an editor UI component misses the TextBox.

Use the TextBox UI component in the template.

Occurs if an item of the List UI component is deleted, while the remove(key) method of the CustomStore used to access data is not implemented.

Pass the function implementing the remove(key) method to the remove property of the CustomStore.

Occurs in the List UI component if the specified value of the itemDeleteMode or menuMode property is not supported.

Make sure that the itemDeleteMode and menuMode properties have valid values.

Occurs in the DataGrid UI component if the data source specified for a lookup column is not valid.

See the lookup.dataSource property's description for details on valid data sources.

Occurs in the DataGrid UI component if the collapseAll(groupIndex) method is called, provided that the UI component uses a remote data source.

Use the collapseAll(groupIndex) method only if the UI component uses an array or locally stored data.

Occurs if a searchMode property holds an invalid value.

Check the validity of the value passed to the searchMode property.

A DateBox internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

Occurs in the Map UI component if an object passed to the markers property is not an array.

Check the validity of the object passed to the markers property.

Occurs in the Map UI component if an object passed to the routes property is not an array.

Check the validity of the object passed to the routes property.

Occurs in the ResponsiveBox UI component if the specified layout cannot be divided into rows and columns.

Simplify the layout configuration.

Occurs in the DataGrid UI component if the summaryType field of an item is set to "custom", provided that the calculateCustomSummary property value is not defined.

Define the calculateCustomSummary property value.

A Scheduler internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

Occurs when an unspecified or an unknown start date is detected in an appointment object of the Scheduler UI component.

Check that the appointment has a start date specified. This is an obligatory field for displaying appointments in the UI component's timetable.

A Scheduler internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

The current browser does not implement an API required for saving files.

This error occurs when your browser version does not implement API for saving files. We recommend that you update your browser to a newer version. Supported browsers are listed here.

Occurs if the editor cannot be created for a Form item because of an internal error.

This error can appear in the following cases:

Occurs if the server returns grouped data that does not match the required format.

The DataGrid UI component can display grouped data if data items have the following structure.

{
    data: [{
        key: "Group 1",
        items: [ ... ],          // subgroups or data objects if there are no further subgroups (check group.isExpanded = true)
                                 // is null if group.isExpanded = false 
        count: 3,                // count of items in this group; required only when items = null
        summary: [30, 20, 40]    // group summary results
    },
    ...
    ], 
    totalCount: 200,              // if requireTotalCount = true
    summary: [170, 20, 20, 1020], // total summary results
    groupCount: 35                // if requireGroupCount = true
}

Occurs when the DataGrid UI component loads or saves a state if the browser does not support local storages for locally opened web pages.

A Scheduler internal error.

To solve the issue, please submit a ticket to our Support Center. Include your UI component configuration, fake data, and the steps needed to reproduce the issue in the ticket.

Occurs when the component data source contains items with non-unique key values.

Occurs if the script specified in the error message is referenced after the DevExtreme scripts or is not referenced at all.

Reference the specified script before the DevExtreme scripts. You can use the following links:

<head>
    <!-- ... -->
    <script src="https://code.jquery.com/jquery-3.5.1.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/babel-polyfill/7.4.0/polyfill.min.js"></script>
    <script src="https://cdn.jsdelivr.net/npm/devextreme-exceljs-fork@4.4.1/dist/dx-exceljs-fork.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/FileSaver.js/2.0.2/FileSaver.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/jspdf/2.0.0/jspdf.umd.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/jspdf-autotable/3.5.9/jspdf.plugin.autotable.min.js"></script>
    <!-- reference the DevExtreme sources here -->
</head>
See Also

Occurs in the DataGrid or TreeList UI component if the key field is not set.

Occurs when the key property of the Store has an incorrect value.

Occurs in the TreeList UI component when the key field specified in the keyExpr property differs from the one specified in the Store.

Occurs in the TreeList UI component if editing takes place without the key property specified in the Store.

Occurs in the DataGrid, TreeList, and Gantt UI components if the key field is not found in at least one data object.

Occurs in the FilterBuilder UI component if the filter expression contains a data field that is not defined in the fields array.

Check that the data field used in the filter expression exists in the fields array.

See Also

Occurs in the FilterBuilder UI component if a condition in the filter expression contains an operation unavailable for the used field.

Check that the field's filterOperations property includes the operation.

Occurs in the TreeList or DataGrid when filterSyncEnabled is true and the columns[].dataField or columns[].name property is not specified in at least one column that allows filter operations.

Check that all columns that allow filter operations have the dataField or name property specified.

Occurs in the DataGrid or TreeList when trying to check the validationRules of a column that has a third-party editor in its editCellTemplate.

This error is specific to the popup and form editing modes. To correct it, choose a different editing mode or validate the editor's value in the onRowValidating function instead of using the validation rules.

Occurs if the dataSource property is not specified in the UI component.

Occurs in a text editor when its buttons[] property is set to an invalid value.

Set the buttons[] property to an array that contains objects or string values.

Occurs in a text editor when at least one of its buttons does not have a name.

Check that the name property is specified for all the buttons.

Occurs in a text editor when at least one of its buttons has an invalid or non-unique value assigned to the name property.

Check that the name property has a valid and unique value for all the buttons.

Occurs in a text editor when it does not support the button type that you included in the buttons[] array.

Follow to the UI component's buttons[] description and ensure that you use only the types specified in the accepted values.

Occurs in Scheduler when startDayHour is set to a time that is later than endDayHour or at least one of these property values is not an integer.

To remove this error, check that both properties are integers in the [0, 24] range and specify a startDayHour before the endDayHour.

Occurs in a DataGrid or TreeList when at least one of its columns has a non-unique value assigned to the name property.

Check that the name property has a unique value for all the columns.

Occurs in a DataGrid or TreeList when at least one of its editable columns does not have a name.

Check that the name property is specified for all editable columns.

Occurs in Scheduler when offset is set to invalid value.

The offset option must be an integer in the [-1440, 1440] range, divisible by 5 without a remainder.

Occurs when data of an unsupported type was provided to a UI component.

A UI component accepts an array of objects as a data source. If you try to pass anything else, the E2001 error occurs. To see an example of how to provide data for a UI component, refer to the Specify a Data Source help topics.

See Also

Occurs when axis type and data type are incompatible.

By default, data type of arguments and values is determined automatically based on the type of values from the data source. In some cases, specifying the data type explicitly may be required. For this purpose, the argumentAxis.argumentType and valueAxis.valueType properties can be used.

Similarly, the types of argument and value axes are determined automatically based on the data type, or set explicitly using the type property of the argumentAxis or valueAxis object correspondingly.

If data of a specified data type cannot be represented on an axis of a specified axis type, the E2002 error occurs. For example, if you try to represent data of a string type on an axis of a logarithmic type, you will get this error.

See Also

Occurs when one of the data source fields has an unsupported type.

Data source fields must contain values of numeric, string or date-time types only. Otherwise, the E2003 error occurs.

See Also

Occurs when values in a data source field have different types that cannot be cast to one type.

For example, this error takes place when among date-time values of a data source field, a string value occurs, and it cannot be converted into date-time type.

See Also

Occurs in the Funnel UI component when the specified value field is absent in the data source or all its values are negative.

Check that you set the valueField property to a field in the data source containing at least one positive value.

See Also

Occurs in the Sankey UI component when data objects are looped.

Occurs in the Sankey UI component if any of the required fields are not found in at least one data object.

Check that each data item has the following structure:

{ source: String, target: String, weight: Number }
See Also

Occurs in the Sankey UI component if the source or target field has an incorrect data type in at least one data object.

Check that each data item has the following structure:

{ source: String, target: String, weight: Number }
See Also

Occurs in the Sankey UI component if the weight field has an incorrect data type or value in at least one data object.

Check that the weight field in each data object is an integer number greater than 0.

See Also

Occurs when series.type property of Chart or PieChart has an unknown value.

Occurs in Chart when two or more value axes on a single pane have the same name.

When you visualize data using several value axes on a single pane, these axes must have different names. If they do not, the E2102 occurs.

See Also

Occurs if an incorrect value was assigned to a property that accepts callback functions only.

Occurs if the logarithmBase property of Chart or RangeSelector was set to an invalid value.

This error may occur if you have set the logarithmBase property of a logarithmic axis (for Chart) or a logarithmic scale (for RangeSelector) incorrectly. The value assigned to this property must be an integer number greater than 1.

See Also

Occurs if an invalid value was specified for a strip or constant line.

A strip for an axis is specified by the startValue and endValue properties of an object in the strips array. A constant line is specified by the value property of an object in the constantLines array. All these properties accept numeric values. If you try to assign a value of another type to one of these properties, the E2105 error occurs.

See Also

Occurs when the startValue or endValue property of the RangeSelector's scale is not valid.

The startValue and endValue properties accept a numeric or date-time value depending on the scale data type. If anything else is passed, the E2202 error occurs.

See Also

Occurs in the RangeSelector UI component when the selected range is invalid.

Commonly, this error appears when either the value property or the setValue(value) method were used incorrectly. To troubleshoot, check that the range you are trying to select falls between the scale start and end values and that the type of the range values is the same as the scale type.

See Also

Occurs in the Map UI component if the apiKey property value is changed after the UI component is created.

Do not change the apiKey after the UI component is created.

Occurs when you are trying to access an item that does not exist.

Check the validity of the specified item.

Occurs in the List UI component if you try to select an item relating to a group that does not exist.

Check the validity of the specified group.

Occurs in the List UI component if you try to select an item that does not exist within the specified group.

Check the validity of the specified item.

Occurs when data is loaded twice when applying initial filter settings.

When both a value for the Filter Row and text for the Search Panel are set for the grid, data loading will be performed twice. The first load will be performed to learn data types for grid columns, and the second one - to apply filters. To avoid double data loading, set data types for all grid columns.

An error occurred while communicating with the map service. See the map service documentation.

Occurs in the TreeView if a node refers to a parent node that does not exist.

Make sure that the parent node exists, and that the field that provides its ID is identical to the keyExpr.

Occurs in the List UI component when you try to search through data specified using the items property.

Specify data in the dataSource property instead.

Occurs when trying to select all the items in a grouped List with the selectAllMode set to "allPages".

Set the selectAllMode to "page" or use a data source with a plain structure. If you need hierarchical data and the capability to select all items across all pages, transform plain data using the DataSource's group property.

Occurs in the DataGrid UI component if the keyExpr property is specified and the data is not a JavaScript array.

Check that the DataGrid is bound to a JavaScript array.

Occurs if you specify the deprecated message field in the object passed to the custom(options) method.

Use the messageHtml field instead. Messages that contain HTML tags should be encoded. See the link above for an example.

Occurs when a page contains more SpeedDialAction UI components than specified in the maxSpeedDialActionCount property.

Increase the maxSpeedDialActionCount:

jQuery
DevExpress.config({
    floatingActionButtonConfig: {
        maxSpeedDialActionCount: 7
    }
});
// ===== or when using modules =====
import config from "devextreme/core/config";

config({
    floatingActionButtonConfig: {
        maxSpeedDialActionCount: 7
    }
})
Angular
import config from "devextreme/core/config";

config({
    floatingActionButtonConfig: {
        maxSpeedDialActionCount: 7
    }
})
Vue
import config from "devextreme/core/config";

config({
    floatingActionButtonConfig: {
        maxSpeedDialActionCount: 7
    }
})
React
import config from "devextreme/core/config";

config({
    floatingActionButtonConfig: {
        maxSpeedDialActionCount: 7
    }
})

... or remove unnecessary SpeedDialAction UI components.

Occurs if you specify the deprecated formatName and formatValues properties in the items array within the HTML Editor's toolbar property.

Use the name and acceptedValues properties instead:

jQuery
$(function(){
    $("#htmlEditorContainer").dxHtmlEditor({
        toolbar: {
            items: [
            {
                // Before
                // formatName: "size",
                // formatValues: ["8pt", "10pt", "12pt"] 

                // Now
                name: "size",
                acceptedValues: ["8pt", "10pt", "12pt"] 
            },
            ...
            ]
        }
    })
})
Angular
<dx-html-editor>
    <dxo-toolbar>
        <!--Before-->
        <!--
        <dxi-item... 
            formatName="size" 
            [formatValues]="['8pt', '10pt', '12pt']">
        </dxi-item>
        -->

        <!--Now-->
        <dxi-item... 
            name="size" 
            [acceptedValues]="['8pt', '10pt', '12pt']">
        </dxi-item>
        ...
    </dxo-toolbar>
</dx-html-editor>
Vue
<DxHtmlEditor>
    <DxToolbar>
        <!--Before-->
        <!--
        <DxItem...
            format-name="size"
            :format-values="['8pt', '10pt', '12pt']" /> 
        -->

        <!--Now-->
        <DxItem...
             name="size"
            :accepted-values="['8pt', '10pt', '12pt']" />
        ...
    </DxToolbar>
</DxHtmlEditor>
React
<HtmlEditor>
    <Toolbar>
        <!--Before-->
        <!--
        <Item...
            formatName="size"
            formatValues={['8pt', '10pt', '12pt']} />
        -->

        <!--Now-->
        <Item...
            name="size"
            acceptedValues={['8pt', '10pt', '12pt']} />
    </Toolbar>
</HtmlEditor>

Occurs in the DataGrid and TreeList UI components when the key property is not specified for a lookup column's dataSource.

Occurs in the DataGrid when infinite scrolling is used and selection.allowSelectAll is set to true.

To select all rows, the component requires their total number. The component cannot calculate the total number when infinite scrolling is used because rows are loaded dynamically.

To fix this, you can do one of the following:

Occurs if the maximum filter query length exceeds the value specified in the maxFilterQueryLength property of the TagBox.

Increase the maxFilterQueryLength value to meet your requirements.

Occurs if the shading property is true and a hideEvent is specified.

In this case, shading prevents interaction with the shaded area, and the hideEvent property's value is ignored. To remove the warning, assign false to the shading property.

Occurs in the Popup, Popover, Tooltip, and LoadPanel if the container property is set to an invalid value or DOM element that does not exist.

Change the container property value to an existing element or its selector. You can also remove this property: in this case, the container uses the default value described in the API section.

Occurs in the UI component if you try to parse incorrect JSON data.

Check the validity of the specified JSON data.

Occurs in the Agenda view of the Scheduler component if you specify appointments without keys.

Specify keys for the appointment data.

Occurs if the client-side export is enabled but the onExporting function is not implemented.

Implement the onExporting function as described in the following help topic: export.

Occurs if you use virtual or infinite scrolling mode and do not specify the component's height.

Specify the component's height.

Occurs when 'ai' is added to HTML Editor toolbar items, but the aiIntegration property is not specified.

Specify aiIntegration.

Occurs in the HTML Editor when a custom AI command is used but no prompt is defined.

Define the prompt.

Appears when none of the data source objects contain a valid argument or value field.

When providing data for Chart or a chart within RangeSelector, you must specify argument and value fields for chart series. If the chart data source does not contain the specified fields, or none of their values are valid, the UI component places the W2002 warning into the browser console.

See Also

Appears when the specified tick intervals lead Chart or RangeSelector to generating an excessive number of ticks.

When dividing the Chart's axes or RangeSelector's scale, you can specify intervals for major and minor ticks. However, if these intervals appear too small, the UI components will ignore them and divide the axes or scale using default tick intervals. In addition, the W2003 warning will appear.

See Also

Appears if the pane specified by the defaultPane property does not exist.

When a multi-pane chart is used, you can specify the pane to be used by default using the defaultPane property. The name of the pane assigned to this property must be also declared within the panes array. Otherwise, the W2101 warning appears, and the last pane declared in this array is used.

See Also

Appears if a value axis specified for a series does not exist.

Using a multi-axis chart), you should specify a value axis for each series using the series.axis property. These value axes should be declared in the valueAxis array as well. If not, a value axis with the name specified for a series will be created automatically, and the UI component will place the W2102 warning into the browser console.

See Also

Appears when a chart hides its title due to the layout being adapted.

This warning may appear if your scenario allows for the change of the UI component container's size. If so, when the size is reduced down to a minimum, which is specified by the height and width properties of the adaptive layout object, accessory UI component elements will be hidden. The W2103 warning, particularly, appears when the chart hides its title.

See Also

Appears when a chart hides its legend due to the layout being adapted.

This warning may appear if your scenario allows for the change of the UI component container's size. If so, when the size is reduced down to a minimum, which is specified by the height and width properties of the adaptive layout object, accessory UI component elements will be hidden. The W2104 warning, particularly, appears when the chart hides its legend.

See Also

Appears when a chart hides one of its axis titles due to the layout being adapted.

This warning may appear if your scenario allows for the change of the UI component container's size. If so, when the size is reduced down to a minimum, which is specified by the height and width properties of the adaptive layout object, accessory UI component elements will be hidden. The W2105 warning, particularly, appears when the chart hides one of the axis titles.

See Also

Appears when a chart hides labels of one of the axes due to the layout being adapted.

This warning may appear if your scenario allows for the change of the UI component container's size. If so, when the size is reduced down to a minimum, which is specified by the height and width properties of the adaptive layout object, accessory UI component elements will be hidden. The W2106 warning, particularly, appears when the chart hides labels of one of the axes.

See Also

Appears if the export menu was hidden due to the container's size being too small.

Occurs if the browser does not support exporting images to the specified format.

Occurs if the distance between the start and end scale values in a gauge equals zero.

Specify the startValue less than the endValue.

$(function () {
    $("#gaugeContainer").dxLinearGauge({ // or dxCircularGauge
        // ...
        scale: {
            startValue: 0,
            endValue: 50
        }
    });
});

$(function () {
    $("#barGaugeContainer").dxBarGauge({
        // ...
        startValue: 0,
        endValue: 50
    });
});
See Also Feel free to share topic-related thoughts here.
If you have technical questions, please create a support ticket in the DevExpress Support Center.
Thank you for the feedback!

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4