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?
Thanks for feedback here. I want to direct you to a couple other conversations around this subject as well.
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!
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?