# Perspective dataset / table row limit

**URL:** <https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [April 28, 2022, 7:13am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970 "2022-04-28T07:13:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul.M](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@Paul.M](https://forum.inductiveautomation.com/u/Paul.M)\
**Post date:** [April 28, 2022, 7:13am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/1 "2022-04-28T07:13:07Z")

</div>

Hello,

I have a SQL db. with 300 + rows (max. 500) and I try to show data to a perspective table but I have a row limitation at 235.

**named queries** - I get all my data from SQL but it stop shows at 235.  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/4/14d58231d34afbead1bd4a9e94bcac54bed3b5c1.png)

**runQuerry** - I get all rows but the same thing, it stop show at row 235  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/a/da90e08c3cf4241ae32dd0ded6575dc2132e47ea.png)

\*I can analyze all my data correctly so Perspective have my data somewhere on back-end but I’m not able to view it, it’s some kind on ‘visual limitation on 235 rows’. On perspective component ‘table’ I have ‘virtualized’ on false. This behavior it is also on tags, custom variable, named query, query binding etc.

From where I can deactivate row limitation on Perspective?

Thanks,

Paul

---

<div class="post-metadata">

**Author:** ![Arnaud\_Declerck](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/arnaud_declerck/32/44872_2.png) [@Arnaud\_Declerck](https://forum.inductiveautomation.com/u/Arnaud_Declerck)\
**Post date:** [April 28, 2022, 7:25am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/2 "2022-04-28T07:25:58Z")

</div>

Hi @Paul.M,

What version to you have ?  
in 8.1.16 i've no issue with a dataset of 1000 rows and 10 collumns

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/6/7654f01395f5db2ecbceeb33a2ec19c347e303ef.png)

Regards

---

<div class="post-metadata">

**Author:** ![Paul.M](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@Paul.M](https://forum.inductiveautomation.com/u/Paul.M)\
**Post date:** [April 28, 2022, 7:57am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/3 "2022-04-28T07:57:45Z")

</div>

Hi @Arnaud_Declerck

I have Dev Version  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/9/59b43646be1e8fcbbdbed7b52dc769e5baa44569.png)

---

<div class="post-metadata">

**Author:** ![Arnaud\_Declerck](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/arnaud_declerck/32/44872_2.png) [@Arnaud\_Declerck](https://forum.inductiveautomation.com/u/Arnaud_Declerck)\
**Post date:** [April 28, 2022, 8:01am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/4 "2022-04-28T08:01:51Z")

</div>

If you go to the gateway webpage, under status--\> overview  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/e/fe77a6d8031a3198c6448573060b239f59eacf85.png)  
You will there find the version and build number  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/0/902b8d20b0c95d40ef06be6dbfd23d5a357ec76e.png)

---

<div class="post-metadata">

**Author:** ![Paul.M](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@Paul.M](https://forum.inductiveautomation.com/u/Paul.M)\
**Post date:** [April 28, 2022, 8:06am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/5 "2022-04-28T08:06:51Z")

</div>

I will download now 8.1.17 (RC1) from site and try to downgrade or upgrade (don’t know if my version it’s smaller or higher)  
This is what I have on gateway - overview

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/6/56a0c9d379822f3e95a78881b699ebcca0627f95.png)

---

<div class="post-metadata">

**Author:** ![Arnaud\_Declerck](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/arnaud_declerck/32/44872_2.png) [@Arnaud\_Declerck](https://forum.inductiveautomation.com/u/Arnaud_Declerck)\
**Post date:** [April 28, 2022, 8:09am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/6 "2022-04-28T08:09:13Z")

</div>

Better to try with 8.1.16 first. 8.1.17 is not officially released yet.

---

<div class="post-metadata">

**Author:** ![Paul.M](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@Paul.M](https://forum.inductiveautomation.com/u/Paul.M)\
**Post date:** [April 28, 2022, 9:31am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/7 "2022-04-28T09:31:53Z")

</div>

Unfortunately I have the same problem also with 8.1.16

---

<div class="post-metadata">

**Author:** ![Arnaud\_Declerck](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/arnaud_declerck/32/44872_2.png) [@Arnaud\_Declerck](https://forum.inductiveautomation.com/u/Arnaud_Declerck)\
**Post date:** [April 28, 2022, 9:42am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/8 "2022-04-28T09:42:29Z")

</div>

That's very stange.  
Could you reinstall or install a clean version of Ignition (Maybe on a virtual machine). And then test it again.

I've you try to take a new table componnent and redo the binding on this new component.

Regards

---

<div class="post-metadata">

**Author:** ![Paul.M](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@Paul.M](https://forum.inductiveautomation.com/u/Paul.M)\
**Post date:** [April 28, 2022, 10:12am UTC](https://forum.inductiveautomation.com/t/perspective-dataset-table-row-limit/58970/9 "2022-04-28T10:12:33Z")

</div>

Problem solved, I tested with another SQL db. and worked fine.

So a fast solving… Create a new db.

Thanks for tips @Arnaud_Declerck
