Being able to use Numeric Abbreviations is helpful, as $3.4M is easier to read than $3,438,723
However, this becomes problematic when your users start to drill down. If the user applies a filter, that $3,438,723 could now be $48,358, and therefore gets abbreviated to $0.0M, which is not useful to the user
There should be an option for Dynamic Abbreviation, to ensure an appropriate level of precision is maintained in the abbreviation as the user drills / filters
Thanks for spotting the odd ones out David You’re right, the KPI in the SQL editor still inherits the legacy system, where it automatically changes the abbreviation.
This might look very powerful but in some cases, people just want the raw numbers, so a conflict of interests over there. The solution should still be smart, but flexible to change if need be.
Revamping the formatting system is not currently on our plan this year, but I will keep a tab of the votes to make sure we don’t miss it during our backlog grooming.
Thanks - do please consider giving an option to use the legacy approach. It won’t always be an issue, but any time we want/expect users to drill down (eg into a specific location from an entire country), we will be unable to include the dashboard in our embedded instance.