Patches on customer test tenant

[former_member201819]

Hey Experts,

I have a question concerning lifecycle management on customer test tenants:

We created an add-on solution on a customer test tenant. Later, I created a patch to make further changes. When you do this, an additional patch version of the solution is created. At this point, a message pops up stating that the patch content would be copied back into the original solution after the "Assemble and download"-function is executed on the patch solution.

There's also a paragraph in the 1308 studio documentation which indicates the same:

Creating a Patch on a Customer's Test Tenant

When you create a patch of a solution on a customer's test tenant, the system creates a copy of your solution in a new namespace allowing you to make and test your changes without disrupting the original solution. This patch type is called a patch solution. When you want to test your patch solution in the test tenant, you first need to use the Implementation Manager in the studio to enable the patch solution instead of the original

solution in the test tenant. When you assemble the patch solution, the patch is copied back to the namespace of the original solution.

The patch solution is used for all future updates to the original solution. Any changes you need to make in the future can be made by creating a new patch again. To do this, open the existing patch solution in the Implementation Manager toolbar and click Create Patch. All future patches are created in the same patchsolution but each patch has a different version number.

Now, I just did "Assemble and download", no errors, the file was downloaded. But as it seems, the patch is not merged into the original solution automatically. Do I have to upload the patch into the original solution manually to get it on the same patch level??

PATCH SOLUTION:

ORIGINAL SOLUTION:

Kind Regards

Pablo

[Former Member · Accepted solution]

"Assemble and Download" just gives you the latest version of solution in a .zip file. You need to upload this copy in PROD tenant. This will update the copy of the solution in PROD tenant as well as in the test tenant(s) automatically.

Note that after logging in PROD tenant, in "Implementation Manager --> Tenant Status", you should see the list of tenant in which your solution is deployed. The test tenant, in which you developed this patch, should also be visible there. If it is not visible, then deploying to PROD tenant will not update the test tenant. But I assume it is visible in your case.

Have a look at this for detailed information.

Best regards,

Hari

[former_member201819 · Accepted solution]

Dear Hari,

thank you for your reply.

You said the patch status of the deployed (original) solution in TEST tenant would change when/after uploading the assembled patch solution to the PROD tenant. I'm sorry, but in my case that did not happen after upload and activation. In PROD tenant as well as in the patch solution on the TEST tenant, we have patch status "3", the deployed/original solution on the TEST tenant has patch status "1".

I have to mention, that the solution hadn't been uploaded to the PROD tenant in an earlier patch status, the upload of patch "3" was the first deployment to PROD.

Kind Regards

Pablo

[former_member201819 · Accepted solution]

OK, I just got the information from the customer that the TEST system is not "linked" to the PROD system and is not on the same physical tenant, so that would be an explanation....