Those two instances can store data under the same key, and no data would be overwritten.ДЇor the data separation to work properly, make sure that each instance of Handsontable has a unique id. For example, if you have two or more instances of Handsontable on one page, data saved by one instance will be inaccessible to the second instance. The main benefit of using persistentState hooks rather than a regular LocalStorage API is that it ensures separation of data stored by multiple Handsontable instances. When persistentState is enabled it exposes hooks listed below: You can set it either during the Handsontable initialization or using the updateSettings method. The persistentState option must be set to true to enable the data storage mechanism. You can save any type of data in local storage to preserve the table state after page reloads. setRequestHeader ( 'Content-type', 'application/x-www-form-urlencoded' ) Д¬lick 'Load' to load data from server # Saving data locally setRequestHeader ( 'X-Requested-With', 'XMLHttpRequest' ) const container = document.querySelector('#example1') Д¬onst exampleConsole = document.querySelector('#example1console') Д¬onst autosave = document.querySelector('#autosave') Д¬onst load = document.querySelector('#load') Д¬onst save = document.querySelector('#save') Д¬onst hot = new Handsontable(container, You need to implement the server-side part by yourself. The HiddenColumns plugin doesn't modify the source data, and doesn't participate in data transformation (the shape of the data returned by the getData () methods stays intact). 'Hiding a column' means that the hidden column doesn't get rendered as a DOM element. Note that this is just a mockup, and nothing is actually saved. The HiddenColumns plugin lets you hide specified columns. In the example below, Ajax is used to load and save the data. Use the afterChange callback to track changes made in the data grid. Those two instances can store data under the same key, and no data would be overwritten.ДЇor the data separation to work properly, make sure that each instance of Handsontable has a unique id.Persistent state storage is particularly useful when running multiple instances of Handsontable on one page as it allows data separation per each instance.

Note that this is just a mockup, and nothing is actually saved. Persistent state storage is particularly useful when running multiple instances of Handsontable on one page as it allows data separation per each instance.

Handsontable getdata