topic Localizing the property pane using powerbi-visual tools 3 in Custom Visuals Development Discussion

Localizing the property pane using powerbi-visual tools 3

popov — Fri, 21 Dec 2018 13:30:01 GMT

Hello.

I try powerbi-visual tools 3 and have problem with localizing the property pane in my CV. I created folder stringResources and placed file ru-RU.json in this folder. Below fragments in code:

capabilities.json

"textSettings":{

"displayName": "Text Settings",

"displayNameKey": "o_tS_key",

"properties": {

"pattern": {

"displayName": "Pattern",

"displayNameKey": "o_tS_p_key1",

"type": {

"text": true

}

ru-RU.json

{

"locale": "ru-RU",

"values": {

"dr_m_key1": "Поля",

"o_tS_key": "Настройки текста",

"o_tS_p_key1": "Шаблон",

"fontColor": "Цвет",

"textSize": "Размер текста",

"alignment": "Выравнивание",

"fontFamily": "Семейство шрифтов"

}

pbiviz.json

"stringResources": ["stringResources/ru-RU.json"]

After run command npm run package I get message:

{ [Error: ENOENT: no such file or directory, open 'c:\Visuals\smartText\stringResources\ru-RU\resources.resjson']
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path:
'c:\\Visuals\\smartText\\stringResources\\ru-RU\\resources.resjson' }
{ [Error: ENOENT: no such file or directory, open 'c:\Visuals\smartText\stringResources\ru-RU.json\resources.resjson']
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path:
'c:\\Visuals\\smartText\\stringResources\\ru-RU.json\\resources.resjson' }

Re: Localizing the property pane using powerbi-visual tools 3

v-viig — Fri, 21 Dec 2018 14:38:58 GMT

JSON format is no longer supported. Please use .resjson instead.

You can find example here.

Ignat Vilesov,

Software Engineer

Microsoft Power BI Custom Visuals

pbicvsupport@microsoft.com

Re: Localizing the property pane using powerbi-visual tools 3

popov — Fri, 21 Dec 2018 18:34:06 GMT

Thank you, v-viig

I created folder stringResources/ru-RU and placed file resources.resjson in folder. But what should I write in the pbiviz.json?

I tried

"stringResources": ["stringResources/ru-RU"]

and

"stringResources": ["stringResources"]

but it isn't work

Re: Localizing the property pane using powerbi-visual tools 3

v-viig — Mon, 24 Dec 2018 07:00:38 GMT

As far as I know, localization will automatically be loaded. Pleae keep stringResources empty (stringResources: []).

Let us know if it resolves the issue.

Ignat Vilesov,

Software Engineer

Microsoft Power BI Custom Visuals

pbicvsupport@microsoft.com

Re: Localizing the property pane using powerbi-visual tools 3

popov — Mon, 24 Dec 2018 19:42:25 GMT

Hello, v-viig

Unfortunately, I recived some error message.

Re: Localizing the property pane using powerbi-visual tools 3

v-viig — Tue, 25 Dec 2018 06:26:58 GMT

What error message have you received? Can you share a screenshot?

Ignat Vilesov,

Software Engineer

Microsoft Power BI Custom Visuals

pbicvsupport@microsoft.com

Re: Localizing the property pane using powerbi-visual tools 3

popov — Tue, 25 Dec 2018 09:03:17 GMT

Of cource

Re: Localizing the property pane using powerbi-visual tools 3

v-viig — Wed, 26 Dec 2018 06:41:50 GMT

We suggest to remove stringResources from pbiviz.json and run pbiviz package again.

If it won't help you we ask you to share the source code to debug this issue from our side.

By the way, what node.js version do you use?

Ignat Vilesov,

Software Engineer

Microsoft Power BI Custom Visuals

pbicvsupport@microsoft.com

Re: Localizing the property pane using powerbi-visual tools 3

popov — Thu, 27 Dec 2018 13:04:04 GMT

Hello, v-viig

Unfortunately, your suggestion don't helped me. Error message and node.js version in screenshot below.

Re: Localizing the property pane using powerbi-visual tools 3

v-viig — Fri, 28 Dec 2018 10:15:36 GMT

Please share source code by sending it to Power BI Custom Visuals Support <pbicvsupport@microsoft.com>

Ignat Vilesov,

Software Engineer

Microsoft Power BI Custom Visuals

pbicvsupport@microsoft.com

Re: Localizing the property pane using powerbi-visual tools 3

Boxmodern — Wed, 02 Sep 2020 10:36:49 GMT

I have the same error message using pbiviz 3.1.14 and node 10.15.1. Did you discover what the issue was?