Data Binding and Syncing

When you have multiple related views (components) on the page you can bind them together or sync their data in order that any changes in one of the views would trigger changes in the bound/synced ones. The main component is called a master one while the bound one is a slave. Master view appears to be the data source for the slave one.

There are 2 main ways to link data:

  • when data in master component changed - slave control gets new data; // syncing
  • when selection in master component changed - slave control gets new data. // binding

In both cases, based on configuration

  • slave can take new data from master component;
  • slave can take new data from server side.

Binding and Syncing - Difference

When you bind data to any component it means that when you select an item from one component, this item will be the data source for another component. Most typically, binding is used with some data-presenting component and a form / htmlform.

When you sync data, it means that all changes in the datastore of one component (such as filtering, sorting. etc.) are reflected in the other component at once.

Data Binding

Data binding is implemented with the help of the bind function that is called from the slave component and has a master component as parameter.


In this case, selection of any list item will result in the form filling with data from the list. Be careful to specify name property for input fields in the form/htmlform. Its values must coincide with template items of the master component (in case of datatable look at column ID-s):

  • component template item = field name in a form;
  • datatable column ID = field name in a form.

Changes in the slave component will affect master one, which means that if you edit the info in the form, then save it (click the Submit button), the list item will have this new data.


Related sample:  Binding to a native HTML form

Slave can as well be unbound from the master by the opposite method:


From now on, list changes cannot affect form data and vice versa.

Adding data to master collection When no item is selected in a master component (here:list), data in the slave one can still be pushed to it.

In other words, if you call save() method for the bound form when no item is selected in the master, a new item will be added to master collection.

The only thing you should do is to remove selection in the master:


Related sample:  Binding to List

Advanced Binding

Data binding features a lot more advanced options to explore:

  • it is subject to customization with the help of additional parameters;
  • it is suitable for binding hierarchical structures;
  • it features event system;
  • it has a native API to set default data for cases when no record is selected in the master control;
  • it utilizes cursor concept to bind to an invisible DataCollection;
  • a lot more..

Study the corresponding article for details.

Syncing Data of Two Components

Data syncing allows making a full or partial copy of data from one data-presenting component and pass it to the other one. Any change in the master component results in the same change in the slave one.

There can be more than one slave component. In this case, all slaves change simultaneously on master component change.

Note that this functionality works with components data stores, that's why data property is used everywhere.

Full Syncing:

The datasets of the two components are absolutely identical.


Partial (Filter-Based) Syncing

Slave view shows only the data items that comply to a certain criterion defined by the function. Here only the films shot after 1994 will be shown.

$$('dview2').data.sync($$('listA'), function(){
        return data.year > 1994;


If the syncing functionality is no longer needed, you can call the unsync command for the component that was previously synced with another one:


Related into on data filtering.

Simultaneous Operations within Synced Components

In case of two and more component synced to one data source (either a visible component or non-visible dataCollection), it seems nice to synchronize user operations as well.

For instance, if an item is selected in one of components, the same item should be selected in the synced one. This is easily done using API.

Let's assume that we have a dataview and datatable both synced with the same dataCollection.

var data = new webix.DataCollection({
    url:"../my_data.json" //load data from an external file

The event system for selection offer the onAfterSelect event. The function that is fired on this event takes the ID of selected item as parameter:

$$("dataview_1").attachEvent("onAfterSelect", function(id){
}); //item ID of dataview coincides with that of datatable  row
$$("datatable_1").attachEvent("onAfterSelect", function(id){
}); //item ID of datatable row coincides with that of dataview item

Related sample:  Data Binding

Data Binding and Syncing with Non-UI objects

One-Time Syncing

One-time syncing allows for synchronizing the data of two components (one of them can be DataCollection) at a chosen time of the application flow without tracking data changes afterwards.

Such syncing presupposes populating one component with the data of another one and is done with importData method:


Note that it's a DataStore method, so it should be called for component data.

Back to top