# \[FEATURE\] Make dropdown options an embedded view

**URL:** <https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [September 26, 2022, 6:32pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491 "2022-09-26T18:32:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\
**Post date:** [September 26, 2022, 6:32pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491/1 "2022-09-26T18:32:39Z")

</div>

Hi there, I have a feature request for the Perspective Dropdown component. I’m trying to build something like this  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/9/2927653fd8fb807161d8c8ae4bb4b1f4ebaf847c.png)  
but with a modern UI design (basically a dropdown with a color picker). I’ve run into situations where a dropdown is the perfect component but the fact that it has very few properties to customize makes it less usable.

Maybe by default it’ll be a simple dropdown where the `options` object would be a value and a label, but then for a more complicated (useful) dropdown, there could be a property to specify a view.

---

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [September 26, 2022, 6:37pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491/2 "2022-09-26T18:37:46Z")

</div>

Interesting idea. I could see lots of scenarios where this might be useful.

In the interim, you could do this with a pseudo “dropdown” done with a flex repeater, and a message handler between the embedded views on-click and the parent view to manage selection.

---

<div class="post-metadata">

**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\
**Post date:** [September 26, 2022, 6:59pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491/3 "2022-09-26T18:59:12Z")

</div>

I was going to use a Table with an column rendered as a view but I think I can get away with using a Flex Repeater like you’re saying. Thanks for the suggestion!

---

<div class="post-metadata">

**Author:** ![Matthew.gaitan](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@Matthew.gaitan](https://forum.inductiveautomation.com/u/Matthew.gaitan)\
**Post date:** [September 26, 2022, 6:59pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491/4 "2022-09-26T18:59:20Z")

</div>

+1 for this request.

I believe IA uses [react-select.com](http://react-select.com) for the perspective dropdown and reading their documentation ([replacing-components](https://react-select.com/components#replacing-components)) it seems like it would support using an embedded view

Having a lot of these futures would be amazing. Particularly groups, individual item styling, with per item icons 🤤

---

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [September 26, 2022, 7:03pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491/5 "2022-09-26T19:03:56Z")

</div>

It’s probably worth adding to the [suggestion box](https://ideas.inductiveautomation.com/)

---

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [September 26, 2022, 7:46pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491/6 "2022-09-26T19:46:56Z")

</div>

> [@Matthew.gaitan](#):
>
> I believe IA uses [react-select.com](http://react-select.com) for the perspective dropdown and reading their documentation ([replacing-components](https://react-select.com/components#replacing-components)) it seems like it would support using an embedded view

If only creating perspective components in modules was easier! lol

---

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [September 26, 2022, 7:48pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491/7 "2022-09-26T19:48:09Z")

</div>

Speaking of…

> **[Embedded View in Perspective Dropdown | Voters | Inductive Automation](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/embedded-view-in-perspective-dropdown)**

---

<div class="post-metadata">

**Author:** ![Matthew.gaitan](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@Matthew.gaitan](https://forum.inductiveautomation.com/u/Matthew.gaitan)\
**Post date:** [September 26, 2022, 7:51pm UTC](https://forum.inductiveautomation.com/t/feature-make-dropdown-options-an-embedded-view/64491/8 "2022-09-26T19:51:19Z")

</div>

It’s honestly not too hard from the little bit I’ve played with it.

I just don’t feel like devoting the time to doing it. Especially for work cause I’m the one who would have to maintain it ☹

Upvoted the ideas post 🙂
