Solution Management
Pipelines and Git are valuable tools, but for small applications, they might not always be necessary. If you’re developing using an unmanaged solution in a Dev environment and deploying a managed solution to Prod, it’s essential to have a rollback plan.
Best practice: Whenever you deploy a managed solution, always export and securely store the corresponding unmanaged solution. You may not need it, but if you do, you’ll be glad you have it!
If you ever need to revert to an earlier solution version, here are two approaches:
Option 1: Import the Earlier Unmanaged Solution into Dev (Overwriting the Current Solution)
Actions
1. Import the older unmanaged solution into Dev.
2. This overwrites existing components but does not remove new com-ponents introduced in later versions.
3. The solution version is incremented upon import.
Pros:
✅ Simple process, no data loss.
Cons:
❌ Leftover components from later versions (tables, fields, flows, etc.) may remain.
Option 2: Delete the Current Solution First (Clean Rollback)
Actions
1. Manually delete the existing solution from Dev.
2. Import the older unmanaged solution.
3. The solution is fully restored to the previous state. Any newer components from later versions are removed.
4. The version number remains unchanged.
Pros:
✅ Ensures a true rollback with no leftover components.
Cons:
❌ Deletes all components, which may impact dependencies in Dev.
❌ Data associated with the deleted solution is also removed.
Solution Versioning Considerations for Moving to Prod
Since Prod requires a managed solution, follow these steps after rolling back in Dev:
1. Export the rolled-back solution as a managed solution.
2. If using Option 2, increase the version number before exporting to ensure it’s higher than the version in Prod.
3. Import the updated managed solution into Prod.
Summary
✅ Quick rollback? Import the older solution directly (newer components remain).
✅ Clean rollback? Delete the existing solution before importing the old one.
✅ Going to Prod? Increase the version number if using Option 2 before exporting.
By following these approaches, you can effectively manage solution versions while maintaining stability across environments.