# Rendered view in table as a column in perspective

**URL:** <https://forum.inductiveautomation.com/t/rendered-view-in-table-as-a-column-in-perspective/62586>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [August 2, 2022, 1:53pm UTC](https://forum.inductiveautomation.com/t/rendered-view-in-table-as-a-column-in-perspective/62586 "2022-08-02T13:53:40Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [August 3, 2022, 6:33am UTC](https://forum.inductiveautomation.com/t/rendered-view-in-table-as-a-column-in-perspective/62586/4 "2022-08-03T06:33:46Z")

</div>

I have said what you can do for that in this topic too.

> [@\[Perspective\] Turn table columns into dropdown](https://forum.inductiveautomation.com/t/perspective-turn-table-columns-into-dropdown/62332/4):
>
> scope should probably be page instead of view. Updating the table directly is dangerous… Because im guessing you want the tables data to be filled by a binding it self. This will cause the binding to rewrite the data, so the users edit will be lost. Either update the sql directly here, or if they have to press a confirm button somewhere first, save all the changes seperately and make your table combine the pulled data and the changes I dont think this will do anything because the event comes…

---

_[View the full topic](https://forum.inductiveautomation.com/t/rendered-view-in-table-as-a-column-in-perspective/62586)._