# Select Elements/Components From ID instead of Hierarchical

**URL:** <https://forum.inductiveautomation.com/t/select-elements-components-from-id-instead-of-hierarchical/82851>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [December 7, 2023, 3:21pm UTC](https://forum.inductiveautomation.com/t/select-elements-components-from-id-instead-of-hierarchical/82851 "2023-12-07T15:21:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Subin\_Adhikari](https://avatars.discourse-cdn.com/v4/letter/s/898d66/32.png) [@Subin\_Adhikari](https://forum.inductiveautomation.com/u/Subin_Adhikari)\
**Post date:** [December 7, 2023, 3:21pm UTC](https://forum.inductiveautomation.com/t/select-elements-components-from-id-instead-of-hierarchical/82851/1 "2023-12-07T15:21:41Z")

</div>

Dear Gurus,

I see in perspective I can set a DOMID to any components, so I wonder if instead of

> self.parent.getChild("FlexContainer").getChild("tblList").props.data

can I do something like

> document.getElementByID("MyId").props.data ?

This would honestly be a game-changer for me since I am a newbie to Ignition and I change design frequently.

also, I would like to know the right place to post feature requests if this feature doesn't exist, please.

Best Regards.

EDIT :: Feature Request upvote link for those who think would help to have this feature [Select Components From ID | Voters | Inductive Automation](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/select-components-from-id)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [December 7, 2023, 3:25pm UTC](https://forum.inductiveautomation.com/t/select-elements-components-from-id-instead-of-hierarchical/82851/2 "2023-12-07T15:25:33Z")

</div>

No, at least not currently. Scripts are all running on the backend, where there is no DOM, only the explicit parent child links we set up. We could implement something _like_ this (or you could create a project library script to do it yourself) but it's not going to be any kind of efficient.

I would suggest leaning heavily on component messaging to accomplish the goal of decoupling, instead.