Custom Visual - Localization

[Nishantjain]

Hi, 

I am trying to add localization to my custom visual and I am struggling to get the data labels to format as per the users locale. 

Here is what I am trying to do

As per this Microsoft Doc Example I am setting up the localization 

import { valueFormatter } from "powerbi-visuals-utils-formattingutils";

let iValueFormatter = valueFormatter.create({ value: 1e6 });

iValueFormatter.format(1234567890);

// returns: "1234.57M"

I am using the culture to format the data label in German

import { valueFormatter } from "powerbi-visuals-utils-formattingutils";

let iValueFormatter = valueFormatter.create({ cultureSelector: "de-DE", value: 1e6 });

iValueFormatter.format(1234567890);

I expect the output to be "1234,57 Mio" but I am getting "1234,57M". 

Not sure what I am missing and I can't find an example in any of the sample in github. Any help is much appreciated

Thanks

Nishant

[Anonymous]

Hi @Nishantjain,

I checked the documents but not found they mention the compatibility about combine using two features.

In my opinion, I'd like to suggest you test with a single feature first to confirm they work on your side if you not mixed two features.

Regards,

Xiaoxin Sheng

[Nishantjain]

@Anonymous Not sure which 2 features you are referring to. I am only trying to get the localization working.

Just need an example of how to make it work. 

[Anonymous]

HI @Nishantjain,

The two features mean the formatting and localization of custom visuals.  I'd like to suggest test two features alone to confirm the both of the two features work in your environment and the resulting style if they sensitive to the parameter orders.

import { valueFormatter } from "powerbi-visuals-utils-formattingutils";
let iValueFormatter = valueFormatter.create({ value: 1e6, cultureSelector: "de-DE" });
iValueFormatter.format(1234567890);

Regards,

Xiaoxin Sheng

[Nishantjain]

@Anonymous Thanks for the suggestion. 

I have tried changing the parameter order but no luck. 

[Anonymous]

HI @Nishantjain,

It can be a reason if some internal issue occurs as 'dm-p' mentioned.
You can test to use different formatting parameters at the same time to confirm if this scenario appears when you work with multiple parameters or only appears if you combine with cultureSelector and other type formatters.

Regards,

Xiaoxin Sheng

[dm-p · Accepted solution]

Hi @Nishantjain,

My two cents: based on my experience with the library, you're using this as intended.

It's not stated in your OP, but is the format as you expect for a core visual for the same measure, but not for the formatting utils? If so, then I would suspect this is a bug in the formatting utils and you should probably raise an issue for it. Of note, I see there's currently an open issue specifically with this locale, so it might be worth reviewing/weighing-in on that.

Regards,

Daniel

[Nishantjain]

@dm-p Thanks for your reply. I believe I have got exactly the same issue as you mentiond in your post (valueFormatter ignores culture #36). 

The issue has been open for over 4 months so not sure what the priority is to fix this. 

Nishant