# How to Prevent Text Field from Converting "kPa" to Uppercase in Ignition Perspective **URL:** \ **Category:** Ignition\ **Tags:** perspective, ignition81\ **Created:** [March 8, 2025, 11:47am UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412 "2025-03-08T11:47:22Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![asgharbmcproject](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@asgharbmcproject](https://forum.inductiveautomation.com/u/asgharbmcproject)\ **Post date:** [March 8, 2025, 11:47am UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/1 "2025-03-08T11:47:22Z")
Hello everyone, I have a Text Field in Ignition Perspective that displays the pressure value. I want to show the value along with the unit "kPa", but Ignition converts all the letters to UPPERCASE. For example, when I set the value like this: Instead of "0.0 kPa", it shows "0.0 KPA". How can I add the unit "kPa" without converting the letters to uppercase? Is there a setting in the Text Field that could solve this issue? Additionally, I've noticed that when I add a format in the Text Field, the bidirectional setting gets disabled. Does anyone know why this happens, and if there is a way to keep bidirectional enabled while adding the format? ---
**Author:** ![Programmatic](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/programmatic/32/70979_2.png) [@Programmatic](https://forum.inductiveautomation.com/u/Programmatic)\ **Post date:** [March 8, 2025, 2:44pm UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/2 "2025-03-08T14:44:00Z")
How are you bringing in the kPa to display? I tested a couple by manually adding it in without a binding and also linking to the engUnit of a tag and both did not display it in all uppercase. You could always have the first field be bound directly to the tag and a second tag set to the engUnit property. Bi-directionality can't work with a transformed value. You are changing the value that would be on a tag and it wouldn't be able to work back to the source value. > [@Bidirectional option in the Configure bind tag is in grey](https://forum.inductiveautomation.com/t/bidirectional-option-in-the-configure-bind-tag-is-in-grey/69909): > > Bidirectional option in the bind tag is in grey. Cant enable that function into the Configure bind tag. the Cant figure it out. Could you help me? Please check screenshot attached. Regards, ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [March 8, 2025, 5:19pm UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/3 "2025-03-08T17:19:42Z")
> [@asgharbmcproject](#): > > I have a Text Field in Ignition Perspective that displays the pressure value. Why? Text fields are for entering text. Use the Label component to **display** values. > [@asgharbmcproject](#): > > Instead of "0.0 kPa"... Why is the user entering both a value and the unit (and a space)? ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [March 8, 2025, 11:18pm UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/4 "2025-03-08T23:18:08Z")
+1 for what @Transistor said. Text fields are for user input only,l. Only raw tag and property bindings support bidirection. Use two components to add the units: a ~~text~~ numerical entry field for the value and a label for the units both within a flex container ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [March 8, 2025, 11:27pm UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/5 "2025-03-08T23:27:10Z")
> [@nminchin](#): > > a **text field** for the value You mean a [Perspective - Numeric Entry Field | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/components/perspective-components/perspective-input-palette/perspective-numeric-entry-field)! ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [March 8, 2025, 11:29pm UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/6 "2025-03-08T23:29:59Z")
Maybe a string tag has units? 🤣 Yes, you're right. Weekend reply ---
**Author:** ![asgharbmcproject](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@asgharbmcproject](https://forum.inductiveautomation.com/u/asgharbmcproject)\ **Post date:** [March 9, 2025, 12:18am UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/7 "2025-03-09T00:18:55Z")
I sincerely thank everyone who responded to my question and provided guidance in the Inductive Automation forum. I uploaded two images to illustrate two different methods for displaying the "kPa" unit: In the first method, the text was displayed in uppercase. In the second method, I attempted to create a unit within a UDT (User-Defined Type), but both approaches were unsuccessful. It was suggested that using a Label component for displaying the unit could solve my problem. While this may work, my main question is whether this is the correct approach in Ignition SCADA. Can’t we combine the value and the unit together? I have very little experience with Ignition. About eight years ago, I worked with it briefly, and I have only recently started using it again. In other SCADA software, it is possible to display both the value and the unit within a single Text Field. When entering a value, the operator can only modify the numeric value. After submitting, the operator sees the value along with the unit. Is such functionality possible in Ignition, or should I use a Text Field for receiving and displaying the value and a Label for displaying the unit? I appreciate your guidance! ![0](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/a/1ad094886c795d4cca1c31d8c3652df8a022d838.png) ![1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/a/ca9d1429fcc9dfe670ede5beb1b1711027ebeae8.png) ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [March 9, 2025, 2:28am UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/8 "2025-03-09T02:28:18Z")
See [[BUG-5618] Perspective format transform with numeric pattern, text being capitalized by default](https://forum.inductiveautomation.com/t/bug-5618-perspective-format-transform-with-numeric-pattern-text-being-capitalized-by-default/56433) for a previous discussion on this topic / problem. However, the big problem is that a Text Field component has no idea about numeric values and restrictions on legal characters. That means that `105.32 kPa` `105 .32 kPa` `10.5.32 kPa` `105.32kPa` `105,32 kPa` would all be accepted. The Numeric Entry Field component - will only accept numbers and the decimal separator. - has a spinner option. - has input bounds. - has a built-in format option. - three mode options. - an invalid-entry style option (e.g. red-border if you go out of range). - will align numbers to the right (although this can be overridden). But the real deal is that your method is creating a string that can't be output back to a numeric tag type. Also, visually, displaying the units in an editable field suggests that they can be edited. I don't know why the other software you refer to would support this. ![Numeric text fields](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/2/42e93dd471bc7972594c35891e45ad7b044d4376.png) _Finally - it just looks right!_ ---
**Author:** ![asgharbmcproject](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@asgharbmcproject](https://forum.inductiveautomation.com/u/asgharbmcproject)\ **Post date:** [March 9, 2025, 4:22am UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/9 "2025-03-09T04:22:00Z")
Dear friends, I sincerely appreciate all of you who took the time to guide me and help solve my issue. Your insights, suggestions, and experiences have been incredibly valuable to me. I was trying to display both the value and the unit in a single input field, but as mentioned, this approach can cause issues regarding data types and the ability to rewrite values. Your suggestion to use the Numeric Entry Field instead of the Text Field seems logical and practical, and I will definitely give it a try. A big thank you to everyone who participated in this discussion and shared their experiences. I hope to contribute my own experiences to the community in the future as well. Best regards 🌹 ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [March 9, 2025, 3:02pm UTC](https://forum.inductiveautomation.com/t/how-to-prevent-text-field-from-converting-kpa-to-uppercase-in-ignition-perspective/103412/10 "2025-03-09T15:02:55Z")
> [@Transistor](#): > > I don't know why the other software you refer to would support this. In others that I've seen, clicking on the input field typically opens a popup with numeric (er, tag _value_) entry only, limiting the suggestion that the units can be edited. The 'formatted string' for that live value is then displayed on the overview. I _much_ prefer the method of Perspective, so that units can be formatted with any style - intentionally different from the process variable (or setpoint - as @Transistor demonstrated): ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/8/083b63808545042693b52e6374704249d2ac438a.png)