# UDT Parameters warning for underscores

**URL:** <https://forum.inductiveautomation.com/t/udt-parameters-warning-for-underscores/85606>\
**Category:** Ignition Early Access\
**Tags:** ignition81\
**Created:** [February 13, 2024, 3:55am UTC](https://forum.inductiveautomation.com/t/udt-parameters-warning-for-underscores/85606 "2024-02-13T03:55:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matthew\_Gall](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@Matthew\_Gall](https://forum.inductiveautomation.com/u/Matthew_Gall)\
**Post date:** [February 13, 2024, 3:55am UTC](https://forum.inductiveautomation.com/t/udt-parameters-warning-for-underscores/85606/1 "2024-02-13T03:55:42Z")

</div>

UDT parameters now give a warning if they include special characters, including underscores.  
I don't see why underscores would cause binding issues, unless the intention really is that we no longer include underscores in parameter names? This menu now looks particularly annoying for those of us using snake case.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/7/f776138218c77e6b18ddc891dd4892b013481feb.png)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 13, 2024, 3:56am UTC](https://forum.inductiveautomation.com/t/udt-parameters-warning-for-underscores/85606/2 "2024-02-13T03:56:54Z")

</div>

Probably an oversight. Underscores should be fine.