# Pager Options for Table Perspective to show ALL data

**URL:** <https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 14, 2025, 9:09am UTC](https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684 "2025-03-14T09:09:36Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielps1818](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@danielps1818](https://forum.inductiveautomation.com/u/danielps1818)\
**Post date:** [March 14, 2025, 9:09am UTC](https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684/1 "2025-03-14T09:09:36Z")

</div>

Hello everyone!

Is there any way of having an option that shows all the data in a perspective table?  
Our current approach is 1000 as a starting option.

Thanks in advance!

---

<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:** [March 14, 2025, 9:56am UTC](https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684/2 "2025-03-14T09:56:35Z")

</div>

Try  
`pager.top : false`  
`pager.bottom : false`

---

<div class="post-metadata">

**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\
**Post date:** [March 14, 2025, 2:02pm UTC](https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684/3 "2025-03-14T14:02:09Z")

</div>

I haven't done it yet, but I'm wanting to implement the ability for the user to pick from either a specific number of rows, or showing all of them, which doesn't exist when using the pager. My plan is to embed the table in a Coordinate container so that I can overlay my own dropdown of options bound to the value of `pager.activeOption`.

(Only very recently did they deprecate the `pager.initialOption` in favor of a new `pager.activeOption` that plays well with bindings, so my users can finally rely on their selection sticking the next time they view a table.)

---

<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:** [March 14, 2025, 3:15pm UTC](https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684/4 "2025-03-14T15:15:36Z")

</div>

I think I would skip the coordinate container and overlay and just add a "Show All" checkbox above the table.

- Make a bidirectional property binding from that to a view property `custom.tableShowAll`.
- Bind `pager.bottom` to the custom property using an expression binding, `!{view.custom.tableShowAll}`. (Note the `!` NOT operator at the start of the expression.)

---

<div class="post-metadata">

**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\
**Post date:** [March 14, 2025, 3:37pm UTC](https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684/5 "2025-03-14T15:37:34Z")

</div>

I try to avoid using extra screen real estate if I don't have to, and most of my tables already have overlays on top of the pager bar for things like "Export to Excel" buttons. But your solution is certainly easier to implement, and would collapse the entire pager bar, making extra space for the rows. I would recommend using toggle buttons over single checkboxes.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [March 16, 2025, 12:13am UTC](https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684/6 "2025-03-16T00:13:11Z")

</div>

> [@Ryan\_Deardorff](#):
>
> My plan is to embed the table in a Coordinate container

This is one instance where I would add the table to a flex and add your other components into the flex with `style.position: absolute` and then set the position of it in styles. Otherwise your components will be at the mercy of coord sizing and will likely end up covering things or being overly tiny or large at other resolutions

Eg

> [@Useful CSS Stuff](https://forum.inductiveautomation.com/t/useful-css-stuff/95414/27):
>
> You can use style.position: absolute to take a component out of a flex container and position it anywhere within the flex. For example to move it to the bottom, offset by 2px from the bot left and set its width to the width of the containing flex minus 4px to give a 2px offset from the flex side bounds: style. position: absolute left: 2px bottom: 2px width: calc(100% - 4px) height: 4px In some cases this is preferable to using a coord container. For example I use this to put icons (n…

---

<div class="post-metadata">

**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\
**Post date:** [March 17, 2025, 5:37pm UTC](https://forum.inductiveautomation.com/t/pager-options-for-table-perspective-to-show-all-data/103684/7 "2025-03-17T17:37:59Z")

</div>

The way I do it does allow for varying screen sizes. I set the coordinate container to percentage, then place a flex container at 0, 0 that spans 100% of its width. I make it only a couple pixels tall so it doesn't overlap the table's navigation, set its overflow to "visible" and then that way I can place components in it at a position relative to the right side of the table (I suppress the "Jump to" input with CSS).
