You’re offline. This is a read only version of the page.
360
Hi, here's my scenario:
1) In dev, there's one unmanaged solution (called Base). It has Entity A
2) In that environment, in another unmanaged solution (called Addon), it adds another field to Entity A.
3) Base is deployed to QA as managed solution
4) Addon is deployed to QA as managed solution (so now entity A has the new field)
5) There's an update in Base, an updated managed solution of Base was created from dev and deployed to QA
6) Deployment failed at upgrade stage, because crm thinks that the base solution is trying to delete the original field from Addon.
Is that normal?
Hi Kenneth Leong,
This is expected behaviour if you removed the original field from one of the unmanaged solutions and then tried to export the solution as managed and import it into another environment.
Share
Report
All responses (
Answers (
