Aligning two or more grids means columns will be kept aligned in all grids. In other words, column changes to one grid (column width, column order, column visibility etc) are reflected in the other grid. This is useful if you have two grids, one above the other such that their columns are vertically aligned, and you want to keep the columns aligned.
To have one (the first) grid reflect column changes in another (the second), place the
first grid's options in
alignedGrids property of the second grids.
Below shows two grids, both aligned with the other (so any column change to one will be reflected in the other). The following should be noted:
The events which are fired as part of the grid alignment relationship are as follows:
The pivot functionality does not work with aligned grids. This is because pivoting data changes the columns, which would make the aligned grids incompatible, as they are no longer sharing the same set of columns.
So why would you want to align grids like this? It's great for aligning grids that have different data but similar columns. Maybe you want to include a footer grid with 'summary' data. Maybe you have two sets of data, but one is aggregated differently to the other.
This example is a bit more useful. In the bottom grid, we show a summary row. Also note the following:
suppressHorizontalScrolldoes not work with the browser Edge. If you are targeting Edge, then there is no way to hide the scrollbar. Currently there is no known way to hide a scroll bar in Edge. The technique ag-Grid uses is to set the CSS overflow property to 'hidden' (rather than 'auto'). In all other browsers, this technique works, however in Edge it does not. The problem with Edge is demonstrated in the following Plunker.
It is possible that you have column groups that are split because of pinning or the order of the columns. The grid below has only two groups that are split, displayed as many split groups. The column aligning also works here in that a change to a split group will open / close all the instances of that group in both tables.
When a grid fires an event, it will be processed to all registered aligned grids. However if a grid is processing such an event, it will not fire an event to other aligned grids. For example, consider the grids A, B and C where B is aligned to A and C is aligned to B (ie A -> B -> C). If A gets a column resized, it will fire the event to B, but B will not fire the event to C. If C is also dependent on A, it needs to be set up directly. This stops cyclic dependencies between grids causing infinite firing of events if two grids are aligned to each other.