# Why can't we add elements to the "form" node similar to how we can use msg.option on "dropdown"?

**URL:** <https://discourse.nodered.org/t/why-cant-we-add-elements-to-the-form-node-similar-to-how-we-can-use-msg-option-on-dropdown/73084>\
**Category:** Dashboard\
**Tags:** node-red-dashboard\
**Created:** [2 January 2023 23:47 UTC](https://discourse.nodered.org/t/why-cant-we-add-elements-to-the-form-node-similar-to-how-we-can-use-msg-option-on-dropdown/73084 "2023-01-02T23:47:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![HerrTuulik](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/herrtuulik/32/72220_2.png) [@HerrTuulik](https://discourse.nodered.org/u/HerrTuulik)\
**Post date:** [2 January 2023 23:47 UTC](https://discourse.nodered.org/t/why-cant-we-add-elements-to-the-form-node-similar-to-how-we-can-use-msg-option-on-dropdown/73084/1 "2023-01-02T23:47:07Z")

</div>

Hello  
I wish to define the elements on a form using msg properties by sending it an array of objects. Unfortunately the node does not currently support this.  
Looking for any suggestions, alternatives.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [3 January 2023 06:53 UTC](https://discourse.nodered.org/t/why-cant-we-add-elements-to-the-form-node-similar-to-how-we-can-use-msg-option-on-dropdown/73084/2 "2023-01-03T06:53:42Z")

</div>

A form is a bit more complex than a single dropdown.

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [3 January 2023 07:06 UTC](https://discourse.nodered.org/t/why-cant-we-add-elements-to-the-form-node-similar-to-how-we-can-use-msg-option-on-dropdown/73084/3 "2023-01-03T07:06:32Z")

</div>

Form node does quite of complex calculations to fit defined elements depending on dashboard and card size configuration. If this kind of calculations left to user to figure out, the widget will be unusable due the complexity. Way above the average user considered to achieve without deep diving into the front-end coding practice. Major difference with the drop-down widget is that overflow behavior is predictable and simple for drop-down.

You can develop the form using the ui\_template or you can make the form using simple ui\_widgets and create the overall form logic flow at the server side.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [17 January 2023 07:06 UTC](https://discourse.nodered.org/t/why-cant-we-add-elements-to-the-form-node-similar-to-how-we-can-use-msg-option-on-dropdown/73084/4 "2023-01-17T07:06:42Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.