# Splitting one dataset structure into several Table components, is it possible?

**URL:** <https://forum.inductiveautomation.com/t/splitting-one-dataset-structure-into-several-table-components-is-it-possible/72631>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [April 19, 2023, 8:56am UTC](https://forum.inductiveautomation.com/t/splitting-one-dataset-structure-into-several-table-components-is-it-possible/72631 "2023-04-19T08:56:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michal\_Goralczyk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michal_goralczyk/32/55564_2.png) [@Michal\_Goralczyk](https://forum.inductiveautomation.com/u/Michal_Goralczyk)\
**Post date:** [April 19, 2023, 8:56am UTC](https://forum.inductiveautomation.com/t/splitting-one-dataset-structure-into-several-table-components-is-it-possible/72631/1 "2023-04-19T08:56:38Z")

</div>

Hello,

for better visualization of dataset in my Ignition interface I need to separate one dataset structure into several table components placed one after another. My dataset is large but the amount of information is very narrow so I would like to put it in several tables placed side by side. Additionally, it would be great if it would be possible to fit and sort them and interact these components with each other. Does anyone know a way to do this or is it at all possible?

I would like to split the example dataset as below. However, I would not like to split this dataset for visualization of my idea I simply split the dataset in the component.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/c/ace82dd7c9a319430beab5ea945dd64dafc35a0f.png)

I would like it to be something along the lines of the one above. Any ideas?

Best regards,  
Michał

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [April 19, 2023, 9:14am UTC](https://forum.inductiveautomation.com/t/splitting-one-dataset-structure-into-several-table-components-is-it-possible/72631/2 "2023-04-19T09:14:16Z")

</div>

![Synchronised table views](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/f/9fc67c413cbb3cc46877f2ee1f51b51484f99158.gif)  
_Figure 1: Table and Table\_0._

I did this by creating an expression binding on the Table\_0 `pager.activePage`:  
`{../Table.props.pager.activePage} + 1`

I restricted the table to 10 rows for this but that might be a problem with flexible layout. You'd need to try to allow paging on the second table to  
change the first.  
Oddly, disabling both `pager.top` and `pager.bottom` on the second table (to hide the pager buttons there) caused the paging to stop working completely on that table.

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [April 19, 2023, 3:15pm UTC](https://forum.inductiveautomation.com/t/splitting-one-dataset-structure-into-several-table-components-is-it-possible/72631/3 "2023-04-19T15:15:26Z")

</div>

Clever trick.

I'd probably just hide the 'slave' tables pagers with css (not the grey footer, for consistency between tables).  
Maybe leave the page number for clarity, though...