Dynamics Community Forum Thread Details

Plugin Assembly included in solution but DLL not deployed on client environment?

I’m trying to deploy a plugin via a solution to a client environment, but it doesn’t work OOTB, and I need advice on the proper approach. Here’s what I did:

On my development environment, I registered a plugin assembly using Plugin Registration Tool (PRT) 9.2.25094, selecting Database as the location.
I registered the plugin step to the assembly.
In Power Apps, I added the assembly to my unmanaged solution via Add Existing → Developer → Plugin Assembly.
I exported the solution both as unmanaged and managed.
The exported solution contains a PluginAssemblies folder with the DLL, and all steps appear in the customization.xml (there is no <Content> with base64 of dll in customization.xml, I don't know if that's problem, and show SourceType as 0)

The problem:

When importing the solution into the client environment, the plugin assembly does not actually deploy — the plugin doesn’t run. It does nothing.

My questions:

0. How to fix this, I want the solution to work OOTB on different client environments?

Is there a way to include the DLL in a managed/unmanaged solution using the current PRT / Power Apps interface so it will work OOTB?
Can this be done entirely via Power Apps / solution, without using the old PRT 9.1.x?
What is the best practice today for deploying plugin assemblies in a solution for client environments?

Thanks in advance for any guidance!

Categories:

Power Platform integration

Quick Links

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics