Open saiankith-explorer opened 4 years ago
I am cloning the unmanaged solution in stage and then importing as a managed solution(Holding) into QA. In the next Task, I am using Apply solution upgrade in QA. Here I get a new solution called solutionxtx_Upgrade. Eventhough the Clone component looks disabled it was active when I ran the piepline and I can see the upgraded solution in stage where its unmanaged. I am using the latest Component V10 and we are on Dynamics 365 Online with Wave 1 2020 enabled
@saiankith-explorer
Are you getting any errors from the upgrade operation?
I notice one of the solutions is a patch not sure where this comes from.
Normally you can do two things in this situation, try to run the upgrade from the UI and see what happens.
If that doesn't work, then there is a problem normally with the solution. Depending on the error you get, you may want to try to delete the _upgrade solution and try again with the fix.
I believe the tasks are working as expected. You can increase the timeout if this is the issue you are facing...
@WaelHamze We add many patches until we get QA approval. Later on we upgrade it so it is normal for us to have many patches. I am not getting any errors on upgrade but I am getting anew solution called upgrade which is something new and the merging of solutions(Base Solution+Patch+Upgrade) is not happening. Am I missing anything here ?Earlier I had both Import Solution and Apply Solution Upgrade as Async but now I tried Import as Sync and Apply Solution Upgrade as Async and it sill did the same. I tried deleting the upgrade and performed the result is the same I get a new solution called upgrade. Have you heard of this issue before ?
@WaelHamze Do you need any info from my end ? Can you please guide us here. I tried all your solutions and even with a brand new solution.
@saiankith-explorer did you try to run the upgrade from the maker portal UI? Does this work? (Does it remove the upgrade solution and the patches)
I have tested this today and the import and upgrade tasks are working as expected.
Below are screenshots from sample release
@WaelHamze I tried in the portal UI and it did work as expected, it removed the upgrade and patches. Below is what I tried today again: A) In instance 1, created an unmanaged solution (core) B) Exported the core (managed) from Instance 1, and imported in Instance 2 C) In instance 1, created an patch for core solution D) Export the patch(Managed) from Instance 1 and import it on Instance 2 E) In Instance 1, cloned core solution F) In instance 2, we are using Import and Upgrade Components and below is the configuration for them
@WaelHamze I figure what the issue is. I was using the display name of solution instead of the solution unique name. However, I encountered a different issue using import and upgrade. I used Async mode for both import solution and apply solution. Even though solution import is done the import solution task keeps running and eventually times out. If I re-run, it succeeds in 2 sec since solution is already existing. I am using version 12. Any thoughts ? Do you want me to close this and create a new ticket ?
@WaelHamze I used synchronous call and it worked. Please close this issue.
I am using the Apply Solution Upgrade component and facing an issue where the Delete and Promote Action is not taking place and resulting in three solutions. 1)base 2)patch 3)upgrade. Because of this i cannot import more solutions and the environment is not in a usable state. I have faced issues earlier and tried asyc mode. I also ran the pipeline again with synchronous mode but the upgarde did not happen. Please let me know how to proceed. Right now our environmetns are blocked. Thank you very much