You’re offline. This is a read only version of the page.
71
Happy Monday All,
I am wondering how do I export all the topics from a PVA bot and import into a different PVA Bot? I saw something on powerapps but I don't see any topics from my bot on the portal?
Let me know!
-n
For single topics, can you try to copy the topic YAML content (you can access it with the 3 dots at the top right corner, and select the code editor view), and paste it in a new topic in the target chatbot?
The complexity here is that your topic may reference entities, variables or other topics that may not exist in your target chatbot, so you may need to fix the topic before it works properly.
Henry
The reality is that the Microsoft people think that everyone is an expert on the software they create, and that means out of the box. But no so. I, myself, have 4 bots for two different websites in two different languages, and each bots contains around 130 really complicated topics that include cards and flows and entities. If I want to create another bot today and I wish to re-use the topics from my other bots, I'm out of lock. There's not an easy solution for something as simple as being able to select the three dots next to the topic and clicking on something like 'save topic to another bot' and select the other bot and bingo, you don't have to re-create the whole thing. I do understand the three steps thing they came up with, but that's only business.
At last, please, Microsoft people, make things user-friendly for others, not for yourselves.
That's odd. Can you or your tenant admin open a support request?
https://learn.microsoft.com/en-us/power-platform/admin/get-help-support
Hi @nk1ng ,
My comments:
PVA for Web (bot developed using the powerva.microsoft.com)
- The best practice is to have 3 environments:
1. DEV
2. TEST
3. PROD
You can develop your bot using the DEV environment. After that, export/import to the TEST environment. After the approval in the TEST env, you export/import to PROD.
- It is not possible to reuse the topics from one bot to another exporting/importing that specific bot in the same environment.
PVA for Teams (developed using the Teams DEsktop or WEb app)
- The best practice is to develop within the final Team that you will use in PROD. Why? Today, we have some limitations to move the bot from one team to another. So, before that improvement, you can develop directly your bot within the final team.
- If you want to move your bot to another team, you can use this documentation: https://docs.microsoft.com/en-us/power-virtual-agents/teams/authoring-export-import-bots-teams
Move customizations between environments - Power Apps | Microsoft Docs
What about this?
https://docs.microsoft.com/en-us/power-virtual-agents/teams/authoring-export-import-bots-teams
or this is different?
Let me know!
-n
So basically, I am starting over on a bot. I have 50~ topics and couple Bot Framework Composer's topics on the old one and need to copy and paste everything from the old one to the new bot? Same environment just need to clone the bot... As for "ALM" thing, I was not using that at all, how to you test in Teams with the powerapps? So you make two "solutions" for the same bot? "Testing" and "Go-live" and then what? What is the correlation between the powerva.microsoft.com (where I currently test and then publish to Teams) and the powerapps.*? I still don't understand what is the point having the powerapps solutions I guess?
@nk1ng ,
When we are developing an App using Power Apps, a flow using Power Automate, or a bot using Power Virtual Agents, the best practice is to develop using a specific environment within a solution. After finish your development, you need to migrate to a test environment. After the approval, you migrate the solution to production (Go Live).
It is part of the ALM process:
#1
Romain The Low-Code...
74
#2
Pablo Roldan
61
#3
stampcoin
10
Share
Report
All responses (
Answers (
