# Decimal Place Formatting Issue **URL:** \ **Category:** Support, Troubleshooting, & Help\ **Created:** [December 11, 2024, 12:42pm UTC](https://community.tulip.co/t/decimal-place-formatting-issue/13318 "2024-12-11T12:42:44Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Horesh](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@Horesh](https://community.tulip.co/u/Horesh)\ **Post date:** [December 11, 2024, 12:42pm UTC](https://community.tulip.co/t/decimal-place-formatting-issue/13318/1 "2024-12-11T12:42:44Z")
Hello all This is Horesh from Bow & Stern and I’ve recently encountered a formatting issue in Tulip when working with decimal numbers, and I’d love to hear your thoughts or solutions. Currently, I can configure the app to round up numbers to a specific number of decimal places when the input exceeds the limit. However, there doesn’t seem to be a way to fixate the decimal places consistently. For example: - If I set the limit to 2 decimal places: - **Input:** `123.456` → **Output:** `123.46` (rounds correctly) - **Input:** `123` → **Output:** `123` (doesn’t show as `123.00`) This inconsistency can cause confusion for customers, especially when precision matters. Ideally, I’d like the app to always display numbers with the same fixed decimal places (e.g., `123.00` or `123.46`). Has anyone else faced this issue? If so, how did you work around it? Alternatively, is there a native setting in Tulip that I might be missing? Looking forward to your insights! ---
**Author:** ![Beth](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/beth/32/5987_2.png) [@Beth](https://community.tulip.co/u/Beth)\ **Post date:** [December 13, 2024, 2:12pm UTC](https://community.tulip.co/t/decimal-place-formatting-issue/13318/2 "2024-12-13T14:12:15Z")
Hi @Horesh - Thanks for feedback here. I want to direct you to a couple other conversations around this subject as well. > [@Treatment of Decimals / Precision of Numbers](https://community.tulip.co/t/treatment-of-decimals-precision-of-numbers/11037): > > Based on previous discussions with support and this old [topic](https://community.tulip.co/t/calculation-significant-figures/6027/10) I understand there are many projects in motion regarding the treatment of decimals throughout the data pipeline. Is it possible to get updates on these projects? I’m running into issues related to the precision of numbers being displayed for my Quality team to verify compliance of completed parts before they are released for shipment. Operators are keying in numbers down to 4 decimals and in most cases Tulip is displaying the value … > [@Calculation Significant Figures](https://community.tulip.co/t/calculation-significant-figures/6027): > > Both variables are number inputs that get populated from a button trigger. Whenever the trigger is executed, the number value spits out more significant figures than it has been set to. Both Quality Index (Lower & Upper Limits) variables have been set to Decimal setting '1.00" for 2 significant figures, but the table record consistently stores 3 sig figs. [image] Thanks for any help! Tulip is targeting enhancements related to this topic to provide customers more control over enforcing number formats to be delivered in a future release. More to come soon! ---
**Author:** ![OlgaStroilova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/olgastroilova/32/7199_2.png) [@OlgaStroilova](https://community.tulip.co/u/OlgaStroilova)\ **Post date:** [January 29, 2025, 5:58pm UTC](https://community.tulip.co/t/decimal-place-formatting-issue/13318/3 "2025-01-29T17:58:50Z")
Hi Horesh, We have an upcoming release to support storing trailing zeros, which includes allowing App Builders to specify the number of digits that should be entered. Is this what you had in mind? Or are you trying to reformat previously entered numbers to show a certain numbers of decimal places, only on display? > [@Upcoming Release: Numbers Precision](https://community.tulip.co/t/upcoming-release-numbers-precision/13644): > > Dear Tulip Contributors, Great news - We’re excited to announce a much-requested platform update to how we store and preserve numeric data, which we’ll start rolling out as of r306/early February. Details – We’re updating how numbers are represented in Tulip Tables and Completions to support capturing, storing, and displaying trailing zeros, for example, 1.20 versus 1.2. Number data, previously stored in our Postgres database as type [Float](https://www.postgresql.org/docs/current/datatype-numeric.html#DATATYPE-FLOAT), will be stored, moving forward, as a different type …