The Round function performs the mathematical round of a number to a specific number of decimal places. It uses the rules defined “Half Round-Up” where it rounds up if the last digit is 5 or more and low if not. For example,
Round(3.14159,4) will return 3.1416 and
Round(3.14159,2) will return 3.14.
- Convert multi-column tables before being able to use the Round function.
- If you want to round always up or down, you need to use the alternative functions RoundUp or RoundDown.
- Unless you want a mathematically correct rounding, I recommend using, for clarity, RoundUp or RoundDown. By doing this, you have a clear direction of the rounding.
- You can round an entire table (single column). The Round function will return a new table with the rounded values.
- Only use rounding when you want to present a lot of information in a compact view. For calculations ensure you’re using the original values.
- Be careful when rounding to get an integer number. Always think if the rounded value will make sense, otherwise, keep at least one decimal place to provide a little bit more context to the user. To do so just do Round(“3.14”,0) .
- Use any of the round functions (Round, RoundDown or RoundUp) instead of Text when displaying the information. You can get the same result as above just by using,
Text((3.14159),"[$-en-GB]#0")but you’d be losing clarity in the formula and not in control in the rounding direction. Use this formula only if you want a strict display of the result like keeping the right-hand zeros, for example.
- You can perform arithmetic operations within the function. For example,
- Arithmetic operations can contain variables but, if the value is not a number, the result will be empty and not an error, so be careful when setting the variables.
- Please note that formulas may have localization-based differences. For example, you should write
Round("3.14",2)with “,” separating each of the arguments, but if your localization is Portugal, you should use “;” instead.
Back to the PowerApps Function Reference
2020-09-03: My thanks to Larry for spotting a typo in this article.