Dynamics CRM 365 - Exporting / importing solution error due to dependencies

(0) Share

Report

Posted on by Hubert Solecki

170

Hi everyone,

I've developed a solution on a developer Dynamics 365 CRM instance. Actually, it's a trial version which contains all proposed modules during installation. Now that I've created my solution, I've exported it as a managed solution and gave it to the customer. He cannot install it because there are some missing dependencies on his instance, which are the following:

So it says that on the USER form that I've adding to my solution, there are some dependencies with some other solutions named "Project Service" and "Field Service".

When I go to the form included in my solution, and hit "Show dependencies", it's written that the solution won't be installed on a system that doesn't have a given list of components. Among them, many components (relations, entities, fields) are from the above two solutions.

As I cannot delete the dependent solutions (FieldService and Project Service), how can I resolve these dependencies ?

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Suggested answer

Wayne Walton 13,730 on at

Like (0)

Report

Make your client install the Field Service and Project service modules in their environment.

Alternately, if that is not possible, roll up a new CRM system with only the Sales module enabled, and rebuild your solution from scratch.

Was this reply helpful? Yes No
Hubert Solecki 170 on at

Like (0)

Report

Thanks for the answer but there is no other way these radical ways ?

Was this reply helpful? Yes No
Wayne Walton 13,730 on at

Like (0)

Report

You could go through one-by-one and try to remove every dependency, but that seems like more work than the other two options.

Was this reply helpful? Yes No
Suggested answer

ashlega 34,477 on at

Like (0)

Report

You might try removing the form from your solution and exporting the solution again. If there are no other dependencies on the FIeld/Project Service, you may be able to install that solution in the customer environment.. you'll still need to re-create the form there, but, at least, all other components might get installed correctly. Or you might spawn another org and do the same there first (but, again, at least you might not have to re-create everything)

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Another thing you can try but is a bit risky (as in you need to do quite some testing to make sure there is no breaks).

Edit the solution.xml file in your exported .ZIP file, and remove the necessary dependency components. You need to have another environment to test whether your solution can still be imported successfully after the dependencies are removed.

Otherwise try to exclude those sub components from your solution if that is not necessary (e.g. field service might have created additional form in contact entity which might not be required for your solution).

Was this reply helpful? Yes No
Indika Abayarathne 671 on at

Like (0)

Report

If you need a radical way, you can play with Solution XML files :)

Create another trial environment with no dependancies such as Feild Service and Project Service solutions and import it to that environment before sending it to client.

But it always risky to change XML files manually and you will have to try few times when you importing.

Was this reply helpful? Yes No
Verified answer

Hubert Solecki 170 on at

Like (2)

Report
Thanks everyone for the answers. What I've done:

deleted the USER entity from my solution which had strong relations with FieldService and ProjectService.

delete all solutions associated to FieldService solution and then the FieldService solution itself at the end.

delete all solutions associated to ProjectService solution and then the ProjectService solution itself at the end.

Having just msdyn_salesapp and msdyn_customerserviceapp installed as solutions, I have recreated the user entity in my solution and exported it.

Everything works find now on the customer instance.

Just notice that the process of deleting the solutions is long and sometimes seems blocked or even not working, but sometimes needs to refresh the page to saw that the solutions are really deleted. Need to be patient.

Was this reply helpful? Yes No