# REQUEST - Add a position/priority/order value property to dashboard nodes for Subflow and dynamic ordering

**URL:** <https://discourse.nodered.org/t/request-add-a-position-priority-order-value-property-to-dashboard-nodes-for-subflow-and-dynamic-ordering/93269>\
**Category:** Dashboard\
**Created:** [19 November 2024 20:04 UTC](https://discourse.nodered.org/t/request-add-a-position-priority-order-value-property-to-dashboard-nodes-for-subflow-and-dynamic-ordering/93269 "2024-11-19T20:04:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![phedders](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/phedders/32/33548_2.png) [@phedders](https://discourse.nodered.org/u/phedders)\
**Post date:** [23 November 2024 14:19 UTC](https://discourse.nodered.org/t/request-add-a-position-priority-order-value-property-to-dashboard-nodes-for-subflow-and-dynamic-ordering/93269/4 "2024-11-23T14:19:30Z")

</div>

Both effectively 🙂  
Primarily ordering subflow instances in a group.

I can now remove hundreds of duplicate node groups in a dashboard flow because I can pass suitable data to instances - thats grreat but nodes appear in a random order and the dashboard side control cant re-order them because being dynamic they do not exist. Yet. But if I give a priority to each _instance_ for the group to build up the right ordering then that would be amazing.

Now if you also wanted to be able to give a 'sub'priority to each dashboard node in a subflow that would be even better because if for a particular control you wanted a Button and a Slice - you can either group and order them, or by making the offset bigger than the instance priority set, group each type of node. Presumably you would apply it as an offset (or give a calculation so you could be more flexible with the layout)

---

_[View the full topic](https://discourse.nodered.org/t/request-add-a-position-priority-order-value-property-to-dashboard-nodes-for-subflow-and-dynamic-ordering/93269)._