Unanswered

Can I duplicate a Power Virtual Agent?

(0) Share

Report

Posted on by michae22

I would like to translate a chat bot into various languages, but I understand that this functionality is not yet available. In lieu of this, I was hoping to duplicate my current Power Virtual Agent for each of the languages I need it translated into, and then just paste the translated text into the duplicated Agent. This would save me the time of duplicating all of the logic from the original Agent eight times.

Categories:

Bot administration

I have the same question (0)

All responses (3)

Answers (0)

CU22081450-0 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @michae22 ,

Today, we don't have this feature available yet. 😞

But you can try to do a workaround.

I never tried it using Power Virtual Agents yet, but I already did some changes to Power Automate workflows using the same logic with exported workflows and worked well.

Basically, when you export as a solution, you have a .zip file that contains all configurations about your workflows, chatbots and something like that.

You can change the principal language, chatbot name and try to import it again to your environment.

Export and import bots using solutions (preview) - Power Virtual Agents | Microsoft Docs

Was this reply helpful? Yes No
Mira Ghaly 11,415 Moderator on at

Like (1)

Report
Copy link

Link copied!

@michae22

Please vote for the idea here

https://powerusers.microsoft.com/t5/Power-Virtual-Agents-Ideas/Duplicate-Power-Virtual-Agents-BOTs-in-the-same-solution-in/idi-p/686764#:~:text=Duplicate%20Power%20Virtual%20Agents%20BOTs%20in%20the%20same%20solution%20in%20Power%20Apps.&text=10%3A53%20PM-,Duplicate%20Power%20Virtual%20Agents%20BOTs%20in%20the%20same%20solution%20in,BOT%20within%20the%20same%20solution.

Was this reply helpful? Yes No
shanBot 4 on at

Like (0)

Report
Copy link

Link copied!

Getting this error, I edited the bot.xml file and importing the zip file in solutions.

The solution file is invalid. The compressed file must contain the following files at its root: solution.xml, customizations.xml, and [Content_Types].xml. Customization files exported from previous versions of Microsoft Dynamics 365 are not supported.

Was this reply helpful? Yes No