# Scheduler - Refresh Data

The most common reason you would use an ObservableCollection is to make a component (like a grid, treeview, treelist, dropdown) change or react when you change that collection.

When you want to refresh the component data source like that, there are two important framework behaviors you need to be aware of - when ObservableCollection instances fire events, and how to refresh the data of a component when it is not an observable collection.

In this article:

* [Rebind Method](https://www.telerik.com/blazor-ui/documentation/components/scheduler/refresh-data#rebind-method)
* [Observable Data](https://www.telerik.com/blazor-ui/documentation/components/scheduler/refresh-data#observable-data)
* [New Collection Reference](https://www.telerik.com/blazor-ui/documentation/components/scheduler/refresh-data#new-collection-reference)

## Rebind Method

You can refresh the Scheduler data by using the Rebind method exposed to the reference of the TelerikScheduler.

> caption Use the Rebind method to refresh the Scheduler data.

<div class="skip-repl"></div>
<demo metaUrl="client/scheduler/refresh-data/example-1/" height="780"></demo>

## Observable Data

> note Refresh the Scheduler data by creating a [New collection reference](https://www.telerik.com/blazor-ui/documentation/components/scheduler/refresh-data#new-collection-reference).

Databound components can benefit from live updates - when the data source collection changes, the components should update to reflect that change. Most data-bound components in the Telerik UI for Blazor suite implement such functionality.

When the `Data` of the component is a collection that implements the `INotifyCollectionChanged` interface (such as `ObservableCollection`), the Telerik components subscribe to its `CollectionChanged` event to make live update. This means that adding items, removing items, or clearing the collection updates the components (its `.Add()`, `.Remove()` and `.Clear()` methods).

The Observable collections fire the `CollectionChanged` event only when their `Add`, `Remove` and `Clear` methods are called. They do not fire it when you change the value of a field of one of their elements.

## New Collection Reference

In Blazor, the framework will fire the `OnParametersSet` event of a child component (which is how child components can react to outside changes) only when it can detect a change in the object it receives through the corresponding parameter (like `Data` for the data sources of Telerik components). This detection works as follows:

* For strings and [value types](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/builtin-types/value-types), this happens when their value changes.

* For [reference types](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/reference-types) (such as data collections like `List`, or any `IEnumerable`, and application-specific objects), this happens when the object reference changes.

  Thus, you would usually need to create a `new` reference for the view-model field (such as `TreeViewData = new List<MyTreeViewItem>(theUpdatedDataCollection);`) when you want the component to update.

> caption Create new collection reference to refresh the Scheduler data.

<demo metaUrl="client/scheduler/refresh-data/example-2/" height="780"></demo>

## See Also

* [ObservableCollection](https://www.telerik.com/blazor-ui/documentation/common-features/data-binding/observable-data)
* [INotifyCollectionChanged Interface](https://docs.microsoft.com/en-us/dotnet/api/system.collections.specialized.inotifycollectionchanged?view=netframework-4.8)
* [Live Demos](https://demos.telerik.com/blazor-ui)