Question

Your team maintains two managed solutions in a production environment: a 'CoreEntities' solution containing a custom table 'Contract', and a 'ContractApprovals' solution containing a model-driven app and a business process flow that both reference the 'Contract' table. A cleanup request asks you to delete the 'CoreEntities' solution from production because it is being retired. When you attempt the deletion, it fails with a dependency error. What is the correct first step to allow the deletion to proceed while preserving supported ALM practices?

Accepted Answer

Remove or uninstall the 'ContractApprovals' solution (or rework it to remove references to 'Contract') before deleting 'CoreEntities', since a managed solution cannot be deleted while another managed solution depends on its components.

Answer

Manually delete the 'Contract' table directly from the environment's default solution to break the dependency, then retry deleting 'CoreEntities'.

Answer

Export 'CoreEntities' as unmanaged, delete the component references, and re-import it as managed to strip the dependency chain.

Answer

Add the 'ContractApprovals' components into 'CoreEntities' as a single merged solution and then delete it in one operation.