# Issue with Using Local Temp Variables in Department Field

**URL:** <https://community.yeeflow.com/t/issue-with-using-local-temp-variables-in-department-field/303>\
**Category:** Ask the community\
**Created:** [September 6, 2024, 7:51pm UTC](https://community.yeeflow.com/t/issue-with-using-local-temp-variables-in-department-field/303 "2024-09-06T19:51:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mauro.roa](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.yeeflow.com/mauro.roa/32/377_2.png) [@mauro.roa](https://community.yeeflow.com/u/mauro.roa)\
**Post date:** [September 6, 2024, 7:51pm UTC](https://community.yeeflow.com/t/issue-with-using-local-temp-variables-in-department-field/303/1 "2024-09-06T19:51:18Z")

</div>

Hi all,

I’ve been working on a new form for direct data entry into a Data List. One of the fields is for selecting a department Parent Node, where users can either choose a static value or a variable. However, when “Variable” is selected, it doesn’t seem possible to use the variables defined at the local temp level.

Could you please update the system to allow the use of user-defined variables at both the temp and filter levels in this scenario?

Thank you!

Mauricio

 ![image](https://canada1.discourse-cdn.com/flex032/uploads/yeeflow/original/1X/294575d70f967930f7ca43ff15aa9f03be94d397.png)  
 ![image](https://canada1.discourse-cdn.com/flex032/uploads/yeeflow/original/1X/9c9f1129b1c8743ea31bbb4a7b64e11866dbf361.png)

---

<div class="post-metadata">

**Author:** ![frank](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@frank](https://community.yeeflow.com/u/frank)\
**Post date:** [September 9, 2024, 1:34am UTC](https://community.yeeflow.com/t/issue-with-using-local-temp-variables-in-department-field/303/2 "2024-09-09T01:34:26Z")

</div>

Hi Mauricio,

Temp variables and Filter variables are only defined and temporarily exist in the form, and the definition of each form is different. Therefore, these two variables cannot be used in the definition of list fields.

Regards,  
Frank

---

<div class="post-metadata">

**Author:** ![mauro.roa](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.yeeflow.com/mauro.roa/32/377_2.png) [@mauro.roa](https://community.yeeflow.com/u/mauro.roa)\
**Post date:** [September 9, 2024, 4:00am UTC](https://community.yeeflow.com/t/issue-with-using-local-temp-variables-in-department-field/303/3 "2024-09-09T04:00:05Z")

</div>

But if this were the case, what would be the point of allowing variables and filters to be declared if they cannot be used in the expression editor within the form? In my view, if you’re allowed to declare variables, it implies they are meant to be used in expressions. Or I’m wrong?

---

<div class="post-metadata">

**Author:** ![frank](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@frank](https://community.yeeflow.com/u/frank)\
**Post date:** [September 24, 2024, 6:07am UTC](https://community.yeeflow.com/t/issue-with-using-local-temp-variables-in-department-field/303/4 "2024-09-24T06:07:24Z")

</div>

Temp & filter variable can be used in formulas on form but could not be used in List field setting. You can think of it like this, the List field settings are cross-form.