# Wijmo_Odata.Odatacollectionview ## Content

ODataCollectionView Class

Extends the CollectionView class to support loading and saving data from OData sources.

You can use the ODataCollectionView class to load data from OData services and use it as a data source for Wijmo controls.

In addition to full CRUD support you get all the CollectionView features including sorting, filtering, paging, and grouping. The sorting, filtering, and paging functions may be performed on the server or on the client.

Note : grouping function can also be performed on server but only when OData version should be NET Core 7.0 or later. As OData added aggregation support from OData 7.0.

Refer to example /wijmo/demos/Grid/Data-binding/ODataServerGroup/purejs that loads grouped data from server and shows in FlexGrid.

The code below shows how you can instantiate an ODataCollectionView that selects some fields from the data source and provides sorting on the client. Notice how the 'options' parameter is used to pass in initialization data, which is the same approach used when initializing controls:

import { ODataCollectionView } from '@mescius/wijmo.odata';
const url = 'http://services.odata.org/V4/Northwind/Northwind.svc/';
const categories = new ODataCollectionView(url, 'Categories', {
  fields: ['CategoryID', 'CategoryName', 'Description'],
  sortOnServer: false
});

The example below uses an ODataCollectionView to load data from a NorthWind OData provider service, and shows the result in a FlexGrid control:

Example

Type parameters

Heirarchy

Constructors

Properties

Methods

Events

Constructors

constructor

Properties

aggregates

aggregates: string

Gets or Sets the aggregates query which would parsed by the OData API and returns the aggregates as result.

This property should be set when groupOnServer is set to true with groupDescriptions.

Aggregates query should be in OData specified AggregationMethods format

// ODataCollectionView Instance
let cv = new ODataCollectionView({
    groupOnServer: true,
    aggregates: `Quantity with sum as Quantity,UnitPrice with average as AggPrice`,
    groupDescriptions: ['State','City']
});

calculatedFields

calculatedFields: any

Gets or sets an object where the keys represent calculated fields and the values are expressions (functions or strings).

Calculated fields require proxies. To use them in IE11, you will need a polyfill such as this one: https://www.npmjs.com/package/proxy-polyfill.

Calculated fields can be useful when dealing with external data. For example, you could add a per-capita income field (gnp/pop) or a profit field (revenue-expenses).

Calculated fields are dynamic. If you change the fields used in the calculation, their values are updated automatically. They are also read-only. You may change the value of the properties used to calculate them, but you cannot directly edit the result.

Unlike FlexGrid cellTemplates, calculated fields can be used for sorting, filtering, and grouping. They can also be used with charts and any other Wijmo controls.

Calculated fields can be defined as functions that take a data item as an argument or as strings.

For example, if your data looked like this:

// regular data item
interface IDataItem {
      product: string,
      brand: string,
      unitPrice: number,
      qty: number,
      shipped: boolean
}
function getData(): IDataItem[] {
    return [
        {
            product: 'Banana',
            brand: 'Chiquita',
            unitPrice: 45.95,
            qty: 12,
            discount: .08,
            shipped: true
        }, ...
    ]
}

You could add function-based calculated fields this way:

// add calculated properties to IDataItem
interface ICalcDataItem extends IDataItem {
    fullName: string;
    allCaps: string;
    totalPrice: number,
    tax: number;
}

let cv = new CollectionView<ICalcDataItem>(getData(), {
    calculatedFields: {
        fullName: ($: ICalcDataItem) => [$.brand, $.product].join(' '),
        allCaps: ($: ICalcDataItem) => $.fullName.toUpperCase(),
        totalPrice: ($: ICalcDataItem) => ($.unitPrice * $.qty) * (1 - $.discount),
        tax: ($: ICalcDataItem) => $.totalPrice * 0.12
    }
});

Function-based calculated fields are usually a better choice than string-based calculated fields because:

1) They provide design-time error checking and command completion, 2) They run faster, and 3) They do not have any issues with content-security policy (CSP).

Alternatively, you could add string-based calculated fields:

let cv = new CollectionView<IDataItem>(getData(), {
  calculatedFields: {
    fullName: '[$.brand, $.product].join(" ")',
    allCaps: '$.fullNameStr.toUpperCase()',
    totalPrice: '($.unitPrice * $.qty) * (1 - $.discount)',
    tax: '$.totalPrice * 0.12'
});

String expressions may refer to the current item via the context variable '$', which contains the item's original and calculated values.

String-based calculated fields have advantages over function-based calculated fields that may be important in some scenarios:

1) They are slightly more concise, and 2) They can be stored as data and easily changed at run-time.

canAddNew

canAddNew: boolean

Gets a value that indicates whether a new item can be added to the collection.

canCancelEdit

canCancelEdit: boolean

Gets a value that indicates whether the collection view can discard pending changes and restore the original values of an edited object.

canChangePage

canChangePage: boolean

Gets a value that indicates whether the pageIndex value can change.

canFilter

canFilter: boolean

Gets a value that indicates whether this view supports filtering via the filter property.

This property does not affect the filters property, which are always applied.

canGroup

canGroup: boolean

Gets a value that indicates whether this view supports grouping via the groupDescriptions property.

canRemove

canRemove: boolean

Gets a value that indicates whether items can be removed from the collection.

canSort

canSort: boolean

Gets a value that indicates whether this view supports sorting via the sortDescriptions property.

currentAddItem

currentAddItem: Partial<T> | T

Gets the item that is being added during the current add transaction.

currentEditItem

currentEditItem: T

Gets the item that is being edited during the current edit transaction.

currentItem

currentItem: T | object & any

Gets or sets the current item in the view.

currentPosition

currentPosition: number

Gets the ordinal position of the current item in the view.

dataTypes

dataTypes: any

Gets or sets a JavaScript object to be used as a map for coercing data types when loading the data.

The object keys represent the field names and the values are DataType values that indicate how the data should be coerced.

For example, the code below creates an ODataCollectionView and specifies that 'Freight' values, which are stored as strings in the database, should be converted into numbers; and that three date fields should be converted into dates:

import { ODataCollectionView } from '@mescius/wijmo.odata';
import { DataType } from '@mescius/wijmo';
const url = 'http://services.odata.org/V4/Northwind/Northwind.svc/';
const orders = new ODataCollectionView(url, 'Orders', {
  dataTypes: {
    Freight: DataType.Number
    OrderDate: DataType.Date,
    RequiredDate: DataType.Date,
    ShippedDate: DataType.Date,
  }
});

This property is useful when the database contains data stored in formats that do not conform to common usage.

In most cases you don't have to provide information about the data types, because the inferDataTypes property handles the conversion of Date values automatically.

If you do provide explicit type information, the inferDataTypes property is not applied. Because of this, any data type information that is provided should be complete, including all fields of type Date.

deferCommits

deferCommits: boolean

Gets or sets a value that causes the ODataCollectionView to defer commits back to the database.

The default value for this property is false, which causes any changes to the data to be immediately committed to the database.

If you set this property to true, it will automatically set the trackChanges property to true. After this, any changes to the data (including edits, additions, and removals) will be tracked but not committed to the database until you call the commitChanges method to commit the changes, or the cancelChanges method to discard all pending changes.

For example:

import { ODataCollectionView } from '@mescius/wijmo.odata';

// create data source
let url = 'https://services.odata.org/...';
let view = new ODataCollectionView(url, 'Categories', {
    keys: [ 'ID' ]
});

// defer commits
view.deferCommits = true;

// handle commit/cancel changes buttons
let btnCommit = document.getElementById('btn-commit') as HTMLButtonElement,
    btnCancel = document.getElementById('btn-cancel') as HTMLButtonElement;
btnCommit.addEventListener('click', () => view.commitChanges());
btnCancel.addEventListener('click', () => view.cancelChanges());
view.hasPendingChangesChanged.addHandler((s, e) => {
   btnCommit.disabled = btnCancel.disabled = !view.hasPendingChanges;
});

entityType

entityType: string

Gets or sets a string that represents the entity's data type on the server.

This may be required to update data in some OData services.

For more details, please see http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.html#_Toc365464687.

expand

expand: string

Gets or sets a string that specifies whether related entities should be included in the return data.

This property maps directly to OData's $expand option.

For example, the code below retrieves all the customers and their orders from the database. Each customer entity has an "Orders" field that contains an array of order objects:

import { ODataCollectionView } from '@mescius/wijmo.odata';
const url = 'http://services.odata.org/V4/Northwind/Northwind.svc/';
const customersOrders = new ODataCollectionView(url, 'Customers', {
  expand: 'Orders'
});

fields

fields: string[]

Gets or sets an array containing the names of the fields to retrieve from the data source.

If this property is set to null or to an empty array, all fields are retrieved.

For example, the code below creates an ODataCollectionView that gets only three fields from the 'Categories' table in the database:

import { ODataCollectionView } from '@mescius/wijmo.odata';
const url = 'http://services.odata.org/V4/Northwind/Northwind.svc/';
const categories = new ODataCollectionView(url, 'Categories', {
  fields: ['CategoryID', 'CategoryName', 'Description']
});

filter

filter: IPredicate | null

Gets or sets a callback used to determine if an item is suitable for inclusion in the view.

The callback should return true if the item passed in as a parameter should be included in the view.

The default value for this property is null, which means the data is not filtered.

filterDefinition

filterDefinition: string

Gets or sets a string containing an OData filter specification to be used for filtering the data on the server.

The filter definition syntax is described in the OData documentation.

For example, the code below causes the server to return records where the 'CompanyName' field starts with 'A' and ends with 'S':

view.filterDefinition = "startswith(CompanyName, 'A') and endswith(CompanyName, 'B')";

Filter definitions can be generated automatically. For example, the FlexGridFilter component detects whether its data source is an ODataCollectionView and automatically updates both the ODataCollectionView.filter and ODataCollectionView.filterDefinition properties.

Note that the ODataCollectionView.filterDefinition property is applied even if the ODataCollectionView.filterOnServer property is set to false. This allows you to apply server and client filters to the same collection, which can be useful in many scenarios.

For example, the code below uses the ODataCollectionView.filterDefinition property to filter on the server and the ODataCollectionView.filter property to further filter on the client. The collection will show items with names that start with 'C' and have unit prices greater than 20:

import { ODataCollectionView } from '@mescius/wijmo.odata';
const url = 'http://services.odata.org/V4/Northwind/Northwind.svc/';
const data = new ODataCollectionView(url, 'Products', {
  oDataVersion: 4,
  filterDefinition: 'startswith(ProductName, \'C\')', // server filter
  filterOnServer: false, // client filter
  filter: function(product) {
    return product.UnitPrice &gt; 20;
  },
});

filterOnServer

filterOnServer: boolean

Gets or sets a value that determines whether filtering should be performed on the server or on the client.

Use the filter property to perform filtering on the client, and use the filterDefinition property to perform filtering on the server.

In some cases it may be desirable to apply independent filters on the client and on the server.

You can achieve this by setting (1) the filterOnServer property to false and the filter property to a filter function (to enable client-side filtering) and (2) the filterDefinition property to a filter string (to enable server-side filtering).

The default value for this property is true.

filters

filters: ObservableArray<IPredicate>

Gets an array of {@link IPredicate} functions used as filters on this CollectionView.

To be included in the view, an item has to pass the predicate in the filter property as well as all predicates in the filters collection.

getError

getError: IGetError | null

Gets or sets a callback that determines whether a specific property of an item contains validation errors.

The method takes as parameters a data item, the property being validated, and a parsing parameter that describes whether the data has already been parsed and applied to the data item (parsing == false), or whether the user was trying to edit the value and entered a value that could not be parsed into the data type expected (parsing == true).

The method returns a string containing an error message, or null if no errors were detected.

For example,

view = new CollectionView(data, {
    getError: (item: any, prop: string, parsing: boolean) => {

        // parsing failed, show message
        if (parsing) {
            if (prop == 'date') {
                return 'Please enter a valid date in the format "MM/dd/yyyy"';
            } else if (prop == 'id') {
                return 'Please enter a positive number';
            }
        }

        // check that stored (parsed) data is valid
        if (prop == 'date' && item.date < minDate) {
            return 'Please enter a date after ' + Globalize.formatDate(minDate, 'd');
        } else if (prop == 'id' && item.id < 0) {
            return 'Please enter a positive number';
        }
    }
});

groupDescriptions

groupDescriptions: ObservableArray<GroupDescription>

Gets a collection of GroupDescription objects that describe how the items in the collection are grouped in the view.

groupLazyLoading

groupLazyLoading: boolean

Gets or Sets a value that detemines whether the group data should be loaded on demand or at once.

The default value for this property is false and should be set to true only when groupOnServer is set to true.

groupOnServer

groupOnServer: boolean

Gets or sets a value that determines whether grouping should be performed on the server or on the client. This property should be set to true only when OData API support aggregation using Apply query.

The default value for this property is false.

groups

groups: CollectionViewGroup[]

Gets an array of CollectionViewGroup objects that represents the top-level groups.

hasPendingChanges

hasPendingChanges: boolean

Gets a value that determines whether the ODataCollectionView has pending changes.

See also the deferCommits property and the commitChanges and cancelChanges methods.

inferDataTypes

inferDataTypes: boolean

Gets or sets a value that determines whether fields that contain strings that look like standard date representations should be converted to dates automatically.

This property is set to true by default, because the ODataCollectionView class uses JSON and that format does not support Date objects.

This property has no effect if specific type information is provided using the dataTypes property.

isAddingNew

isAddingNew: boolean

Gets a value that indicates whether an add transaction is in progress.

isEditingItem

isEditingItem: boolean

Gets a value that indicates whether an edit transaction is in progress.

isEmpty

isEmpty: boolean

Gets a value that indicates whether this view contains no items.

isLoading

isLoading: boolean

Gets a value that indicates the ODataCollectionView is currently loading data.

This property can be used to provide progress indicators.

isPageChanging

isPageChanging: boolean

Gets a value that indicates whether the page index is changing.

isUpdating

isUpdating: boolean

Gets a value that indicates whether notifications are currently suspended (see beginUpdate and endUpdate).

itemCount

itemCount: number

Gets the total number of items in the view taking paging into account.

items

items: (T | object)[]

Gets items in the view.

itemsAdded

itemsAdded: ObservableArray<Partial<T> | T>

Gets an ObservableArray containing the records that were added to the collection since trackChanges was enabled.

itemsEdited

itemsEdited: ObservableArray<Partial<T> | T>

Gets an ObservableArray containing the records that were edited in the collection since trackChanges was enabled.

itemsRemoved

itemsRemoved: ObservableArray<Partial<T> | T>

Gets an ObservableArray containing the records that were removed from the collection since trackChanges was enabled.

jsonReviver

jsonReviver: Function

Gets or sets a custom reviver function to use when parsing JSON values returned from the server.

If provided, the function must take two parameters (key and value), and must return the parsed value (which can be the same as the original value).

For details about reviver functions, please refer to the documentation for the JSON.parse method.

keys

keys: string[]

Gets or sets an array containing the names of the key fields.

Key fields are required for update operations (add/remove/delete).

newItemCreator

newItemCreator: IItemCreator<T>

Gets or sets a function that creates new items for the collection.

If the creator function is not supplied, the CollectionView will try to create an uninitialized item of the appropriate type.

If the creator function is supplied, it should be a function that takes no parameters and returns an initialized object of the proper type for the collection.

oDataVersion

oDataVersion: number

Gets or sets the OData version used by the server.

There are currently four versions of OData services, 1.0 through 4.0. Version 4.0 is used by the latest services, but there are many legacy services still in operation.

If you know what version of OData your service implements, set the oDataVersion property to the appropriate value (1 through 4) when creating the ODataCollectionView (see example below).

import { ODataCollectionView } from '@mescius/wijmo.odata';
let url = 'https://services.odata.org/Northwind/Northwind.svc/';
let categories = new ODataCollectionView(url, 'Categories', {
  oDataVersion: 1.0, // legacy OData source
  fields: ['CategoryID', 'CategoryName', 'Description'],
  sortOnServer: false
});

If you do not know what version of OData your service implements (perhaps you are writing an OData explorer application), then do not specify the version. In this case, the ODataCollectionView will get this information from the server. This operation requires an extra request, but only once per service URL, so the overhead is small.

pageCount

pageCount: number

Gets the total number of pages.

pageIndex

pageIndex: number

Gets the zero-based index of the current page.

pageOnServer

pageOnServer: boolean

Gets or sets a value that determines whether paging should be performed on the server or on the client.

Use the pageSize property to enable paging.

The default value for this property is true.

pageSize

pageSize: number

Gets or sets the number of items to display on a page.

refreshOnEdit

refreshOnEdit: boolean

Gets or sets a value that determines whether the CollectionView should automatically refresh its results (by applying the sort, filter, and grouping operations) after items are edited.

The default value for this property is true, which ensures the collection is always sorted, filtered, and grouped correctly after any edit operations.

Set it to false if you want updates to be deferred when items are edited. In this case, the collection will not be refreshed until the sorting, filtering, and grouping criteria change or until the refresh method is called (Excel behavior).

requestHeaders

requestHeaders: any

Gets or sets an object containing request headers to be used when sending or requesting data.

The most typical use for this property is in scenarios where authentication is required. For example:

import { ODataCollectionView } from '@mescius/wijmo.odata';
const url = 'http://services.odata.org/V4/Northwind/Northwind.svc/';
const categories = new ODataCollectionView(serviceUrl, 'Categories', {
  fields: ['Category_ID', 'Category_Name'],
  requestHeaders: { Authorization: db.token }
});

showDatesAsGmt

showDatesAsGmt: boolean

Gets or sets a value that determines whether dates should be adjusted to look like GMT rather than local dates.

sortComparer

sortComparer: IComparer<T>

Gets or sets a function used to compare values when sorting.

If provided, the sort comparer function should take as parameters two values of any type, and should return -1, 0, or +1 to indicate whether the first value is smaller than, equal to, or greater than the second. If the sort comparer returns null, the standard built-in comparer is used.

This sortComparer property allows you to use custom comparison algorithms that in some cases result in sorting sequences that are more consistent with user's expectations than plain string comparisons.

For example, see Dave Koele's Alphanum algorithm. It breaks up strings into chunks composed of strings or numbers, then sorts number chunks in value order and string chunks in ASCII order. Dave calls the result a "natural sorting order".

The example below shows a typical use for the sortComparer property:

import { CollectionView, isString } from '@mescius/wijmo';

// create a CollectionView with a custom sort comparer
const view = new CollectionView(data, {
    sortComparer: (a: any, b: any) => {
        return isString(a) && isString(b)
            ? alphanum(a, b) // use custom comparer for strings
            : null; // use default comparer for everything else
    }
});

The example below shows how you can use an Intl.Collator to control the sort order:

import { CollectionView, isString } from '@mescius/wijmo';

// create a CollectionView that uses an Intl.Collator to sort
const collator = window.Intl ? new Intl.Collator() : null;
let view = new CollectionView(data, {
    sortComparer: (a, b) => {
        return isString(a) && isString(b) && collator
            ? collator.compare(a, b) // use collator for strings
            : null; // use default comparer for everything else
    }
});

sortConverter

sortConverter: ISortConverter

Gets or sets a function used to convert values when sorting.

If provided, the function should take as parameters a SortDescription, a data item, and a value to convert, and should return the converted value.

This property provides a way to customize sorting. For example, the FlexGrid control uses it to sort mapped columns by display value instead of by raw value.

For example, the code below causes a CollectionView to sort the 'country' property, which contains country code integers, using the corresponding country names:

const countries = 'US,Germany,UK,Japan,Italy,Greece'.split(',');
view.sortConverter = (sd: SortDescription, item: any, value: any) => {
    return sd.property === 'countryMapped'
        ? countries[value]; // convert country id into name
        : value;
}

The next example combines two values so when sorting by country, the view will break ties by city:

view.sortConverter: (sd: SortDescription, item: any, value: any) => {
    if (sd.property == 'country') {
        value = item.country + '\t' + item.city;
    }
    return value;
}

sortDescriptions

sortDescriptions: ObservableArray<SortDescription>

Gets an array of SortDescription objects that describe how the items in the collection are sorted in the view.

sortNulls

sortNulls: SortNulls

Gets or sets a value that determines how null values should be sorted.

This property is set to SortNulls.Last by default, which causes null values to appear last on the sorted collection, regardless of sort direction. This is also the default behavior in Excel.

sortOnServer

sortOnServer: boolean

Gets or sets a value that determines whether sort operations should be performed on the server or on the client.

Use the sortDescriptions property to specify how the data should be sorted.

The default value for this property is true.

sourceCollection

sourceCollection: (T | object)[]

Gets or sets the underlying (unfiltered and unsorted) collection.

tableName

tableName: string

Gets the name of the table (entity) that this collection is bound to.

totalItemCount

totalItemCount: number

Gets the total number of items in the view before paging is applied. With groupLazyLoading, Gets the total number of available top-level groups count.

trackChanges

trackChanges: boolean

Gets or sets a value that determines whether the control should track changes to the data.

The default value for this property is false, so the CollectionView does not keep track of which data items have changed.

If you set this property to true, the CollectionView will keep track of changes to the data and will expose them through the itemsAdded, itemsRemoved, and itemsEdited collections.

Tracking changes is useful in situations where you need to update the server after the user has confirmed that the modifications are valid.

After committing or cancelling changes, use the clearChanges method to clear the itemsAdded, itemsRemoved, and itemsEdited collections.

The CollectionView only tracks changes made when the proper CollectionView methods are used (editItem/commitEdit, addNew/commitNew, and remove). Changes made directly to the data are not tracked.

useStableSort

useStableSort: boolean

Gets or sets whether to use a stable sort algorithm.

Stable sorting algorithms maintain the relative order of records with equal keys. For example, consider a collection of objects with an "Amount" field. If you sort the collection by "Amount", a stable sort will keep the original order of records with the same Amount value.

The default value for this property is false, which causes the CollectionView to use JavaScript's built-in sort method, which is fast and usually stable.

Chrome provides stable sorting since version 70, and Firefox since version 3. As of ES2019, sort is required to be stable. In ECMAScript 1st edition through ES2018, it was allowed to be unstable.

Setting the useStableSort property to true ensures stable sorts on all browsers (even IE 11), but increases sort times by 30% to 50%.

Methods

addNew

  • addNew(item?: Partial<T> | T, commit?: boolean): Partial<T> | T

  • Adds a new item to the collection.

    Calling this methods without any parameters creates a new item, adds it to the collection, and defers refresh operations until the new item is committed using the commitNew method or canceled using the cancelNew method.

    The code below shows how the addNew method is typically used:

    // create the new item, add it to the collection
var newItem = view.addNew();

// initialize the new item
newItem.id = getFreshId();
newItem.name = 'New Customer';

// commit the new item so the view can be refreshed
view.commitNew();

    You can also add new items by pushing them into the sourceCollection and then calling the refresh method. The main advantage of addNew is in user-interactive scenarios (like adding new items in a data grid), because it gives users the ability to cancel the add operation. It also prevents the new item from being sorted or filtered out of view until the transaction is committed.

    New items are empty objects by default, unless the colletion has calculatedFields, in which case the new items will have properties set to values that depend on their data types (empty strings for string properties, zero for numeric properties, and null for other data types).

    This behavior is convenient since in many cases the calculated fields depend on expressions that rely on strings not being null. But you can customize this behavior by setting the newItemCreator property to a function that creates the new items and initializes them in any way you want.

    Parameters

    • Optional item: Partial<T> | T

      Item to be added to the collection (optional).

    • Optional commit: boolean

      Whether to commit the new item immediately.

    Returns Partial<T> | T

    The item that was added to the collection, or null if the transaction failed.

beginUpdate

  • beginUpdate(): void

cancelChanges

  • cancelChanges(): void

cancelEdit

  • cancelEdit(): void

cancelNew

  • cancelNew(): void

clearChanges

  • clearChanges(): void

commitChanges

  • commitChanges(committed?: Object): void

  • Commits all pending changes to the server.

    Changes are contained in the itemsEdited, itemsAdded, and itemsRemoved collections, and are automatically cleared after they are committed.

    See also the deferCommits property.

    Parameters

    • Optional committed: Object

      Optional callback invoked when the commit operation has been completed. The callback takes an XMLHttpRequest parameter contains information about the request results.

    Returns void

commitEdit

  • commitEdit(): void

commitNew

  • commitNew(): void

contains

  • contains(item: T): boolean

deferUpdate

  • deferUpdate(fn: Function, force?: boolean): void

editItem

  • editItem(item: T): void

endUpdate

  • endUpdate(force?: boolean): void

getAggregate

  • getAggregate(aggType: Aggregate, binding: string, currentPage?: boolean): any

  • Calculates an aggregate value for the items in this collection.

    Parameters

    • aggType: Aggregate

      Type of aggregate to calculate.

    • binding: string

      Property to aggregate on.

    • Optional currentPage: boolean

      Whether to include only items on the current page.

    Returns any

    The aggregate value.

getGroupAggregate

  • Returns server-calculated aggregate value for a specified property and CollectionViewGroup.

    The aggregates property should be defined to get the server-calculated aggregate. If aggregates property is not defined, it will return empty value ''.

    Parameters

    Returns any

    The calculated aggregate value.

implementsInterface

  • implementsInterface(interfaceName: string): boolean

lazyLoadGroup

load

  • load(): void

  • Loads or re-loads the data from the OData source.

    Returns void

moveCurrentTo

  • moveCurrentTo(item: Partial<T> | T): boolean

  • Sets the specified item to be the current item in the view.

    Parameters

    • item: Partial<T> | T

      Item that will become current.

    Returns boolean

moveCurrentToFirst

  • moveCurrentToFirst(): boolean

moveCurrentToLast

  • moveCurrentToLast(): boolean

moveCurrentToNext

  • moveCurrentToNext(): boolean

moveCurrentToPosition

  • moveCurrentToPosition(index: number): boolean

moveCurrentToPrevious

  • moveCurrentToPrevious(): boolean

moveToFirstPage

  • moveToFirstPage(): boolean

moveToLastPage

  • moveToLastPage(): boolean

moveToNextPage

  • moveToNextPage(): boolean

moveToPage

  • moveToPage(index: number): boolean

moveToPreviousPage

  • moveToPreviousPage(): boolean

onCollectionChanged

onCurrentChanged

onCurrentChanging

onError

onHasPendingChangesChanged

  • onHasPendingChangesChanged(e?: EventArgs): void

onLoaded

onLoading

onPageChanged

onPageChanging

onSourceCollectionChanged

  • onSourceCollectionChanged(e?: EventArgs): void

onSourceCollectionChanging

refresh

  • refresh(): void

remove

  • remove(item: any): void

  • Override remove to remove the item from the database.

    Parameters

    • item: any

      Item to be removed from the database.

    Returns void

removeAt

  • removeAt(index: number): void

  • Removes the item at the specified index from the collection.

    Parameters

    • index: number

      Index of the item to be removed from the collection. The index is relative to the view, not to the source collection.

    Returns void

updateFilterDefinition

  • updateFilterDefinition(filterProvider: any): void

  • Updates the filter definition based on a known filter provider such as the FlexGridFilter.

    Parameters

    • filterProvider: any

      Known filter provider, typically an instance of a FlexGridFilter.

    Returns void

Events

collectionChanged

collectionChanged: Event<ICollectionView<T>, NotifyCollectionChangedEventArgs<T>>

Occurs when the collection changes.

currentChanged

currentChanged: Event<ICollectionView<T>, EventArgs>

Occurs after the current item changes.

currentChanging

currentChanging: Event<ICollectionView<T>, CancelEventArgs>

Occurs before the current item changes.

error

error: Event<ODataCollectionView, RequestErrorEventArgs>

Occurs when there is an error reading or writing data.

hasPendingChangesChanged

hasPendingChangesChanged: Event<ODataCollectionView, EventArgs>

Occurs when the value of the hasPendingChanges property changes.

See also the deferCommits property.

loaded

loaded: Event<ODataCollectionView, EventArgs>

Occurs when the ODataCollectionView finishes loading data.

loading

loading: Event<ODataCollectionView, EventArgs>

Occurs when the ODataCollectionView starts loading data.

pageChanged

pageChanged: Event<IPagedCollectionView, EventArgs>

Occurs after the page index changes.

pageChanging

pageChanging: Event<IPagedCollectionView, PageChangingEventArgs>

Occurs before the page index changes.

sourceCollectionChanged

sourceCollectionChanged: Event<ICollectionView<T>, EventArgs>

Occurs after the value of the sourceCollection property changes.

sourceCollectionChanging

sourceCollectionChanging: Event<ICollectionView<T>, CancelEventArgs>

Occurs before the value of the sourceCollection property changes.