I have a crm system on which I develop solutions. No problem with that.
I have developed two solutions in that development system and can deploy those solutions to other CRM systems with no problems. If I deploy two solutions to one system and then try to remove a solution it fails.
So I have solution A in which I include the user entity because my custom entities in solution A are linked to users. I also have solution B which includes a reference to users because its custom entities are linked to users. Solutions A and B are independent and make no reference to each other. So I have a one : many relationship between users and entity A1 in solution A and a one : many relationship between users and entity B1 in solution B.
I have now changed the properties of solution B. It was only a prototype and only deployed to two systems so that's reasonable. Essentially I changed a boolean property to be a true boolean whereas previously it was a look up to an option set containing two values. On the system with only solution B I can delete the old solution and reimport, it objects if I just import presumably because a property has been replaced with one of the same name but different type but nonetheless the process works. On the system with solutions A and B I can not import the new solution B without first deleting it which was expected but neither will CRM let me delete solution B because it insists there is a dependancy between the two solutions and insists I have to delete solution A which is not an option as it will destroy data. When I read through the XML it seems that the customisation.XML exported by CRM lists every known entity including the entities from unrelated solutions.
Is there some special trick to developing multiple solutions in a single CRM system without having them get confused about dependancies?