# \[BUG-13855\]Perspective Table Rows not showing on PopUp

**URL:** <https://forum.inductiveautomation.com/t/bug-13855-perspective-table-rows-not-showing-on-popup/29607>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [November 1, 2019, 7:59pm UTC](https://forum.inductiveautomation.com/t/bug-13855-perspective-table-rows-not-showing-on-popup/29607 "2019-11-01T19:59:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mmurphy](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmurphy/32/11430_2.png) [@mmurphy](https://forum.inductiveautomation.com/u/mmurphy)\
**Post date:** [November 1, 2019, 7:59pm UTC](https://forum.inductiveautomation.com/t/bug-13855-perspective-table-rows-not-showing-on-popup/29607/1 "2019-11-01T19:59:37Z")

</div>

I created a view on Perspective that I intend to use as a popup. All it is is two labels (title and description) and a table.

The table’s “data” prop is bound to a named query. There is no error on the binding and the rows populate in Preview Mode, as a component of another view in Run Mode, and in the “Launch URL” page for the view. However, if I open the view using a button configured to open a popup, the rows on the table don’t show (though it seems like the data is fetched because the column names and pager populate).

**Table working as component in a view…**

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

**Table not working as popup…**

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/00fac6b30147191df049506882dba9e35f626909.png)

**Popup button config…**

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/4/465d6a3d4c600c869cee70a024c087fad3e3f750.png)

What am I overlooking?

M Murphy

---

<div class="post-metadata">

**Author:** ![osolorzano](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/osolorzano/32/6432_2.png) [@osolorzano](https://forum.inductiveautomation.com/u/osolorzano)\
**Post date:** [November 1, 2019, 10:26pm UTC](https://forum.inductiveautomation.com/t/bug-13855-perspective-table-rows-not-showing-on-popup/29607/2 "2019-11-01T22:26:55Z")

</div>

On the table component itself, there’s a property call virtualized. If you disable that property does it start to work?

---

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [November 1, 2019, 11:33pm UTC](https://forum.inductiveautomation.com/t/bug-13855-perspective-table-rows-not-showing-on-popup/29607/3 "2019-11-01T23:33:33Z")

</div>

I’ve seen this issue sometimes when the basis of the table is set using ‘auto’.

---

<div class="post-metadata">

**Author:** ![mmurphy](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmurphy/32/11430_2.png) [@mmurphy](https://forum.inductiveautomation.com/u/mmurphy)\
**Post date:** [November 4, 2019, 7:29pm UTC](https://forum.inductiveautomation.com/t/bug-13855-perspective-table-rows-not-showing-on-popup/29607/4 "2019-11-04T19:29:49Z")

</div>

Yes. I set it to ‘FALSE’ and the popup worked. Why is that?

---

<div class="post-metadata">

**Author:** ![osolorzano](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/osolorzano/32/6432_2.png) [@osolorzano](https://forum.inductiveautomation.com/u/osolorzano)\
**Post date:** [November 4, 2019, 7:38pm UTC](https://forum.inductiveautomation.com/t/bug-13855-perspective-table-rows-not-showing-on-popup/29607/5 "2019-11-04T19:38:48Z")

</div>

Virtualization is supposed to make the table only show enough rows to fit the view it is currently in. However, there’s a bug where it doesn’t properly work with popups that are displaying the table in a flex container. I’ve linked this post to the internal ticket so that this post will get an update when it gets fixed, but for the time being you will have to disable the virtualized property in this specific case.
