# Floating precision forced limit on screen in perspective **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [September 21, 2023, 7:22pm UTC](https://forum.inductiveautomation.com/t/floating-precision-forced-limit-on-screen-in-perspective/79474 "2023-09-21T19:22:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Project2501](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@Project2501](https://forum.inductiveautomation.com/u/Project2501)\ **Post date:** [September 21, 2023, 7:22pm UTC](https://forum.inductiveautomation.com/t/floating-precision-forced-limit-on-screen-in-perspective/79474/1 "2023-09-21T19:22:20Z")
This feels like it's easy and I'm missing the point, that happens alot. Problem statement: Tags in perspective had a high level of precision when bound to a Props.text. I first changed the tag property to force 2 digits only by doing .##, but noticed that the display was using it as a string. So I added a Transform to force it to a number, thinking that would be the fix: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/f/0fa5c754558acf819f2b4f0c4bc0b674fa11a5d4.png) And it looks great at 3. The folks at work want it limited to two. So I'm almost there. If that Format Pattern field wasn't greyed out... What have I missed? ---
**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:** [September 21, 2023, 7:29pm UTC](https://forum.inductiveautomation.com/t/floating-precision-forced-limit-on-screen-in-perspective/79474/2 "2023-09-21T19:29:12Z")
2.1457672 × 10-4 = 0.00021457672. Round that to two decimal places and ... ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [September 21, 2023, 7:32pm UTC](https://forum.inductiveautomation.com/t/floating-precision-forced-limit-on-screen-in-perspective/79474/3 "2023-09-21T19:32:40Z")
If you want to use a format pattern, change your format field from `Number` to `Pattern`. Also, if you want to force two decimals don't use `.##` use `.00` ---
**Author:** ![Project2501](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@Project2501](https://forum.inductiveautomation.com/u/Project2501)\ **Post date:** [September 21, 2023, 7:33pm UTC](https://forum.inductiveautomation.com/t/floating-precision-forced-limit-on-screen-in-perspective/79474/4 "2023-09-21T19:33:22Z")
so i picked a bad screenshot, trying to show the transform. Understood. Here is another example showing the issue as described. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/7/572c46bffab0f20e54451656efb5504c70b13e70.png) I want to fix that at 2 digits. the transform property doesn't have a format field that I can edit. ---
**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:** [September 21, 2023, 7:33pm UTC](https://forum.inductiveautomation.com/t/floating-precision-forced-limit-on-screen-in-perspective/79474/5 "2023-09-21T19:33:30Z")
Use an expression binding instead: `numberFormat(2.1457672e-4, "0.00E00")` ---
**Author:** ![Project2501](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@Project2501](https://forum.inductiveautomation.com/u/Project2501)\ **Post date:** [September 21, 2023, 7:33pm UTC](https://forum.inductiveautomation.com/t/floating-precision-forced-limit-on-screen-in-perspective/79474/6 "2023-09-21T19:33:47Z")
oh super helpful, thank you.