# Enable Device System attributes calculated via workflow

**URL:** <https://forums.losant.com/t/enable-device-system-attributes-calculated-via-workflow/5407>\
**Category:** Feature Request\
**Tags:** device, device-state\
**Created:** [February 7, 2024, 8:25pm UTC](https://forums.losant.com/t/enable-device-system-attributes-calculated-via-workflow/5407 "2024-02-07T20:25:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Logan\_Parker](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/logan_parker/32/4860_2.png) [@Logan\_Parker](https://forums.losant.com/u/Logan_Parker)\
**Post date:** [February 7, 2024, 8:25pm UTC](https://forums.losant.com/t/enable-device-system-attributes-calculated-via-workflow/5407/1 "2024-02-07T20:25:37Z")

</div>

Device systems are an awesome way of aggregating different sets of devices - however, the attributes on the device systems should be able to be set not only as aggregates of the children device data, but also by workflows / custom calculations - there’s a lot of cases where we would benefit greatly by having the ability to update our parent device system state through workflows which calculate correlated values based on the children devices.

A workaround we are currently implementing is an extra device which holds all the calculated values in its state - the device system then aggregates data from this device, but it doesn’t feel like the most optimal solution.

---

<div class="post-metadata">

**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\
**Post date:** [February 8, 2024, 3:29pm UTC](https://forums.losant.com/t/enable-device-system-attributes-calculated-via-workflow/5407/2 "2024-02-08T15:29:17Z")

</div>

Hi @Logan_Parker, and welcome to the Losant Forums!

Thanks for the feedback on system attributes. I’m unsure of how big a change to that architecture your request would be but I will forward this on to the engineering team for evaluation. I will follow up if it is a feature we decide to tackle.

Please keep the suggestions and questions coming!