Internally AdaptableBlotter.JS using Redux to manage its state - this provides a unidirectional store for all the objects used in the grid.
If you are also using Redux in your own application then you should continue to use your own Store and not merge the 2 Stores. This is the Best Practice advice.
You can use the Adaptable Blotter perfectly normally without ever needing directly to access or, indeed, have any knowledge of the store.
The recommended way to access the Store is via the Blotter API which provides you with full programmatic read / write access to all our objects in a clean way.
The Blotter API is actually a simple wrapper around our Redux store with basic read / write access and some additional error handling, logging and other features.
We strongly recommend that you use the Blotter API to access the Store (both for reading and writing).
However, if you want, you are able to access our store directly through your code. You can subscribe to data changes and then react accordingly.
The recommended way to listen to changes in the Store is by subscribing to the onAuditStateChanged audit event in the auditEventsApi section of Blotter API. This event can be set to fire through the Audit Log - which gives you the option of listening to User State changes, Internal State changes or both. There is an option to set whether this Audit Message is fired as an event.
Read how to set the Audit Log to fire this event in Audit Log.
If you want, you are able to access our store directly through your code. You can subscribe to data changes and then react accordingly.
The Adaptable Blotter object that you create when you instantiate the Adaptable Blotter has an adaptableBlotterStore property. You can listen to changes in this store by subscribing to it and monitoring the changes that you are interested in.
While you can do this we would strongly recommend that you access the Adaptable Blotter state through the safer Blotter API.