Solved: Re: How to connect to Microsoft Translator from Po...

Silvester_Lee · ‎10-10-2021

I have followed the official document to build a translator in Power App. First, I created a resource in Azure successfully (Attachment Figure 1). After that, I try to add a connector "Translator" and copy and paste the key from Azure (Attachment Figure 2). However, the error occurs. Anyone can tell me are there any mistakes I have made? Thanks.

StalinPonnusamy · ‎10-15-2021

Hi @Silvester_Lee

Overall UI

1. InputLanguage - Text Control to enter input

2. Combobox to display Languages

Set Items Property to

MicrosoftTranslatorV2.Languages()

And Set Code and Name as per below for that language combo box

3. Set OnSelect Property of Translate button to

Set(LanguageResponse, MicrosoftTranslatorV2.Translate(LanguageSelector.Selected.Code,InputLanguage.Text))

4. Set Text property of Label control to

LanguageResponse

Add-on: We can avoid a button too

For easy thing, We can remove the button and Set the OnChange property of the Combo box to

Set(LanguageResponse, MicrosoftTranslatorV2.Translate(LanguageSelector.Selected.Code,InputLanguage.Text))

View solution in original post

Silvester_Lee · ‎10-18-2021

Dear Stalin,

I have followed your steps and the translator is created successfully. I really appreciate your efforts! Thank you so much.

Now, I can input English and translate it into Chinese. It is so great!

Thank you again!

Silvester

View solution in original post

StalinPonnusamy · ‎10-10-2021

Hi @Silvester_Lee

I used translator service which region was East US and never had issues. I see you created it in the Eastasia region. Not sure, the region is the problem. Can you try to create in a different region or Global region and try?

v-bofeng-msft · ‎10-10-2021

Hi @Silvester_Lee :

Please check the number of the Microsoft Translator V2 connections.Only 2 connections can be created per account.

I think this link will help you a lot:

Microsoft Translator V2

Best Regards,

Bof

StalinPonnusamy · ‎10-11-2021

Good point @v-bofeng-msft

Silvester_Lee · ‎10-13-2021

Thank you for your help and it works. However, the label still cannot display the translation. The error occurs. Did I miss any setting in the function? Thank you.

StalinPonnusamy · ‎10-13-2021

Hi @Silvester_Lee

Can you share the error please?

Silvester_Lee · ‎10-13-2021

There are 3 errors as follows:

1. The name is invalid and the identification code cannot be recognized;
2. The function 'Translate' has some invalid arguments;
3. The behavior function in the non-behavior attribute, you can't use this attribute to change the value in other places of the application.

StalinPonnusamy · ‎10-13-2021

Hi @Silvester_Lee

Let me create my side and let you know.

Silvester_Lee · ‎10-14-2021

Thank you very much.

StalinPonnusamy · ‎10-14-2021

Hi @Silvester_Lee

Looks like the Issue with regions and PowerApps. It works well with a console application using the subscription key.

Find the Article for the Regions Availability.

I have my Azure AD in the US and selected eastus2 as a database and not working for me. For Proof of concept, don't need to enter the subscription key

It works fine

If no subscription key is provided, the shared API key will be used, which comes with built-in throttling limits based on the number of characters that are being translated, specifically 55,000 characters per day and 100 requests per minute.

Please create a Microsoft ticket to connect using a subscription key before going to production