Dynamics Community Forum Thread Details

Trouble with managed solution upgrade

Hello all,

please can you help me shine some light on my issue? I am aware it's quite a common question and I've been reading numerous articles, but for some reason I just can't work it.

I've a got solution with versions/patches ranging from 1.1.0.0 to 1.1.23.0. I performed a 'clone solution' in our Dev environment to create 1.2.0.0.

When I then deployed that to our Test environment (as an upgrade, not overriding customisations) it installed 1.2.0.0 but did not roll up/delete the lower versions. When I tried to force a solution upgrade, it wouldn't work.

This is the first time this hasn't worked for me, hence I was very surprised.

The reason for the failure is a load of dependencies. Fair enough, but what I don't get is that all the elements are within this solution (and its patches). It's very much a standalone solution for this particular part of our system. Unless I've gone blind, there is nothing in any another solution that is dependent on this one. So it's listing all these dependencies, but they're all in this solution and in 1.2.0.0.

Now I know that with dependencies they say you have to remove them from the solution before it can be rolled up/deleted. But I'm wary of doing this, because these components are not in any solution and I don't want the upgrade to (accidentally) delete my components.

Maybe I'm having a 'schoolboy moment', but I'm struggling to work out what I need to do.
I have considered just leaving it, but in Dev I'm now on 1.2.0.0 with a patch 1.2.1.0. I'm assuming it's not a great idea to skip the upgrade and deploy patch 1.2.1.0 to Test without have properly rolled up the lower version?

Again, thank you for any advice you can share, I am aware it's a common question, but with everything I read so far I just can't get my head around it. Really appreciate anyone's time and ideas.

I've included some screenshots. I'm sure you appreciate I had to redact some info for privacy/security reasons, but hopefully you get the idea. Also, the screenshot of the 'view' dependency is just one example of several different things, but all pointing to the same required components and same solution layers etc.

Massive thanks to anyone who can push me in the right direction.

Pete.