Power Virtual Agents extensions for Dynamics 365 (workaround on installation hiccups)

a “strange behavior” and a “fix”

Holger Imbery
3 min readJan 21, 2023
Photo by Joshua Aragon on Unsplash

Situation

You want to use Power Virtual Agent with Dynamics 365 Customer Service, and you are trying to install the extensions to activate variables and actions.

Figure 1: Message to documentation for installing the extensions.
Figure 1: Message to documentation for installing the extensions.

You are following precisely the path described in the documentation,
but you get an error message saying the solution is not compatible with your environment.
In my case, all language settings are on en-US, but my tenant has a location in Germany.

Figure 2: Error Message
Figure 2: Error Message

Motivation

This article is to overcome the situation for those running into the error.
It is a “works-on-my-machine” solution and should help those who can fix it to find the root cause of it.

Workaround

Here comes a dirty workaround to get it done in between.

Open the developer tools in your browser (Edge: CTRL+SHIFT+I) and open the Network Tab. While clicking on “install”, you will see an error “400”

Figure 3: error “400” while installing.
Figure 3: error “400” while installing.
Figure 4: Body of “POST” Request
Figure 4: Body of “POST” Request
Figure 5: countryCode
Figure 5: countryCode

You will then recognize a result code “200” in the status line.

If you close the installation popup and go straight to the environment you want to install the extensions to, you will see that this “fix” was successful.

Figure 6: Successfully installing the extensions.
Figure 6: Successfully installing the extensions.
Figure 7: installed variables.
Figure 7: installed variables.
Figure 8: Installed actions.
Figure 8: Installed actions.

Conclusion

Do not give up when something unexpected happens. Find the root cause with the tools you have and give a first thought a try.

Originally published at https://the.cognitiveservices.ninja.

--

--

Holger Imbery
Holger Imbery

Written by Holger Imbery

* Microsoft MVP (Copilot Studio), MCT * principal architect - Copilot Studio | Copilot | power platform | azure * My Blog: https://holgerimbery.blog

No responses yet