Product Feedback Forum
Help us make Sisense better by posting your product feedback here.
cancel
Showing results for 
Search instead for 
Did you mean: 

 

Background and customer pain points

Currently Sisense is capable of showing numeric figures in abbreviated format, but only in the American/European short scale form: thousand (k), million (M), billion (B), trillion (T). In east Asian countries, there is a different scale form, so viewing information in these k/M/B/T is very difficult to understand. 


Non-abbreviated

Standard abbreviation (US/Europe)

Indian abbreviation

East Asian abbreviation

1,000

1 k (thousand)

1,000

1 千

10,000

10 k

10,000

1 万

100,000

100 k

1 lakh

10 万

1,000,000

1 M (Million)

10 lakh

100 万

10,000,000

10 M

1 crore

1000 万

100,000,000

100 M

10 crore

1 億

1,000,000,000

1 B (Billion)

1 arab

10 億

10,000,000,000

10 B

10 arab

100 億

100,000,000,000

100 B

1 kharab

1000 億

1,000,000,000,000

1 T (Trillion)

10 kharab

1 兆

Business case description/value

To be able to select the scale form for number abbreviations for different APAC regions as well.

Use case

  1. A user in Europe is creating a dashboard in Insights with an indicator to show total profit in an Indicator form. Let's suppose that the total profit to display is 1,610,000. 2. Europe user formats the content to abbreviate the display in the short scale form. User will see "1.61 M". 3. A user in Japan is creating the exact same dashboard on the same data. 4. Japan user formats the content to abbreviate the display in Asian scale form. User will see "161 万". 5. A user in India is creating the exact same dashboard on the same data. 6. India user formats the content to abbreviate the display in the India scale form. User will see "16.1 Lakh".

 
3 Comments

Hi @Sisense Team,

Can we get some update here. If this feature request is prioritised and picked up or not.

Status changed to: Needs Votes & Comments

Hello @Suryakant.

Thank you for submitting your idea!

I have brought this Idea to the product team and will post updates here as they are available.

One of the ways we prioritize development efforts is by community interest. I encourage other users to vote and comment on this suggestion. The more engagement a request receives, the higher the likelihood of it being considered for implementation.

Thank you for being a valuable part of our community!

Hi @DRay ,

Appreciate your kind update here. This functionality is really required by many customers at our end.