Microsoft Dynamics 365 | Integration, Dataverse...

Solution can't be imported because of missing dependency (Custom Workflow Assembly)

(0) Share

Report

Posted on by binnall

I have an issue with a solution being deployed because of a dependency. Note this is a Power Platform solution that has been created in utilising the CDS and Modal Driven Apps.

The dependency is a Custom Workflow Assembly that can be found here: https://github.com/binnall/AdvancedMath

My scenario is the following:

Two environments 'Development' & 'Integration'. These environments are in the same O365 tenant.

I used the plugin registration tool to deploy the DLL into the Development environment, create an instant workflow to get the results based on the inputs for control.

This all works perfect. I pass in the figures and get the values as I would expect.

I then use the plugin registration tool to deploy the DLL into the Integration environment. Again this works as expected.

However, I have been using Azure DevOps to deploy my Solution into the different environments. And when trying to deploy the solution with the custom assembly as part of one of my instant Workflow Processes as part of the solution a dependency error occurs.

The error that I receive is: The following solution cannot be imported: [[SolutionName]] . Some dependencies are missing. The missing dependencies are .... (Custom Assembly Namespace)

Does anybody know why I can't deploy the solution into the environment when I have an instant process that uses the Workflow DLL?

removing the workflow that uses this DLL enables the solution to deploy as expected.

I'm not sure If I am missing a particular way of registering the DLL into each of the environments so that it is referenced in the same way?

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Adrian Begovich 1,027 Moderator on at

Like (0)

Report

Hi binnall,

You need to include the missing dependencies in the solution you are deploying or remove the dependency associations from components in the solution before deployment.

Was this reply helpful? Yes No
Suggested answer

Francisco Murtinheira on at

Like (0)

Report

Hello binnal,

If I understood your situation correctly, then you are importing a managed solution with dependencies to a Custom Workflow Assembly, but the Assembly has already been registered on the target with PRT.

This is expected, as when you import a managed solution, the dependency calculator will search for the dependencies on a managed layer. However, your Assembly is registered on the active layer as unmanaged, since you used PRT.

I would advise you here to try and unregister the Assembly from the Integration environment, and add it to your solution instead, so it moves alongside the dependent process.

Hope this helps.

Was this reply helpful? Yes No
Abigail 552 on at

Like (0)

Report

You need to add the dependencies mentioned in the error message to get the solution running in the Integration environment.

That would solve your problem.

Was this reply helpful? Yes No