# Perspective component get dropdown props from gateway

**URL:** <https://forum.inductiveautomation.com/t/perspective-component-get-dropdown-props-from-gateway/99606>\
**Category:** Module Development\
**Tags:** perspective\
**Created:** [December 9, 2024, 8:33pm UTC](https://forum.inductiveautomation.com/t/perspective-component-get-dropdown-props-from-gateway/99606 "2024-12-09T20:33:42Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [December 9, 2024, 9:20pm UTC](https://forum.inductiveautomation.com/t/perspective-component-get-dropdown-props-from-gateway/99606/4 "2024-12-09T21:20:13Z")

</div>

Seems like an anti-pattern. Components are best when they’re flexible, and making a component do its own queries is at odds with the goals of Ignition. Is there a reason you don’t want to provide your options through a binding?

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-component-get-dropdown-props-from-gateway/99606)._