# Perspective DOM

**URL:** <https://forum.inductiveautomation.com/t/perspective-dom/31147>\
**Category:** Ignition Early Access\
**Tags:** ignition80, perspective\
**Created:** [January 8, 2020, 3:06pm UTC](https://forum.inductiveautomation.com/t/perspective-dom/31147 "2020-01-08T15:06:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RadicalRumin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/radicalrumin/32/11543_2.png) [@RadicalRumin](https://forum.inductiveautomation.com/u/RadicalRumin)\
**Post date:** [January 8, 2020, 3:06pm UTC](https://forum.inductiveautomation.com/t/perspective-dom/31147/1 "2020-01-08T15:06:06Z")

</div>

I was wondering if it’s somehow possible to interact with the DOM in perspective. Via script maybe or some other way.

If anyone has any ideas I’d like to hear them.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 8, 2020, 3:07pm UTC](https://forum.inductiveautomation.com/t/perspective-dom/31147/2 "2020-01-08T15:07:50Z")

</div>

It is deliberately not available. You can write an SDK module to present your own component(s), though, and they can include true client-side scripting.

---

<div class="post-metadata">

**Author:** ![RadicalRumin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/radicalrumin/32/11543_2.png) [@RadicalRumin](https://forum.inductiveautomation.com/u/RadicalRumin)\
**Post date:** [January 8, 2020, 3:21pm UTC](https://forum.inductiveautomation.com/t/perspective-dom/31147/3 "2020-01-08T15:21:38Z")

</div>

Fair enough.  
The reason I was asking was in fact for a component module I’m working on.  
I’ve run into a hyper specific problem where my component won’t rerender when the main datasource changes after removing an item from it.  
I thought I might be able to solve it by interacting with the DOM, but to do it from the designer for flexibility reasons.
