# \[FEATURE\] New "Find/Replace selected Views" - Add this at the component level

**URL:** <https://forum.inductiveautomation.com/t/feature-new-find-replace-selected-views-add-this-at-the-component-level/61664>\
**Category:** Ignition\
**Created:** [July 8, 2022, 12:58am UTC](https://forum.inductiveautomation.com/t/feature-new-find-replace-selected-views-add-this-at-the-component-level/61664 "2022-07-08T00:58:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [July 8, 2022, 12:58am UTC](https://forum.inductiveautomation.com/t/feature-new-find-replace-selected-views-add-this-at-the-component-level/61664/1 "2022-07-08T00:58:09Z")

</div>

The new addition of the view/window/templates context menu to find/replace stuff within the selected items from a context menu is awesome, but we also need this at the component level as well.

For example, right click on View.root.FlexContainer1 and have the option “Find/replace in component” to search and replace for things _just inside of this Flex Container_.

Edit:  
Maybe this is this idea already:

> **[Find Replace for selected tags/Objects Only | Voters | Inductive Automation](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/find-replace-for-selected-tagsobjects-only)**

It still says “planned” so I’m guessing/hoping that this is already in the works/on the horizon?

---

<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:** [July 8, 2022, 3:40pm UTC](https://forum.inductiveautomation.com/t/feature-new-find-replace-selected-views-add-this-at-the-component-level/61664/2 "2022-07-08T15:40:39Z")

</div>

I think that idea was basically the thing we just did. I don’t know how it would work for component-specific stuff, given the way our current find & replace mechanism works, but it’s a neat idea.

We have something else in the pipeline that might achieve the same goal; basically a way to explore a particular view’s configuration (scripts, bindings, etc) separate from the main editing UI.