After assembling a patch in test system it is not merged in original solution

[kostadin_terziev]

Hello!

I create a patch for a solution in test system.

It says that after I assemble it , it will be merged back to original solution.

This is not happening and the patch solution (with its own prefix) is staying as a separate solution.

Because of this when deploying to production after the first time , I need to deploy the patch solution version.

This causes problems with the bindings of extension fields in the print forms.

Is this a bug, can it be fixed?

[ThiagoSarmento · Accepted solution]

Hello kostadin_terziev,

If I am not overlooking your statement, this is pretty much the system behavior.
When you create a solution for the first time, it is considered an original solution, having its own ID. After assembling it, you need to create a patch.

Patches have their own ID, which will not be the same as the original ID. They are considered two separate solutions and only share their Description and linkage between original and solution.

When you download the patch solution, you are given a .zip file with the original solution ID, but with patch content.
If you wish, you can even upload this .zip on top of the original solution so it gets updated with latest patch files.

Kindly refer to below blogs:
https://blogs.sap.com/2019/03/15/sdk-lifecycle-management-best-practices/
https://blogs.sap.com/2015/08/27/sap-cloud-applications-studio-deployment-landscape-basics/

All the best,
Thiago

[kostadin_terziev · Accepted solution]

Hi, thiago.sarmento ,

Thank you for your answer.

If this is the expected system behavior then why is there a message pop-up when creating a patch saying that after assembling it it will be copied back to the original solution?

Regards,

Kostadin

[ThiagoSarmento · Accepted solution]

Hi kostadin_terziev,

Because this is exactly what the system does 🙂

When you click on Assemble and Download button of your patch solution, you are given a .zip file containing the patch content with original solution ID. Hence the patch ID is aliased (or copied) to the namespace (ID) of the original solution.

So creating a patch for the original solution for the first time means that:

• the SDK creates a new solution which have a different namespace (ID)
• and when assembling the patch, the solution content is aliased to the original solution namespace

I hope this shed some light to it, I am sorry if the pop-up was misled.

Regards,
Thiago

[kostadin_terziev · Accepted solution]

Hi, thiago.sarmento !

So the behaviour is not that the patch solution will disappear but rather it will stay and its new version of the code will be copied to the original solution?

And so when deploying to production we should assemble and download and then upload the zip file from the patch solution?

Can we download the zip file from the original solution so that the solution prefix is consistent with the first deployed in production?

Regards,

Kostadin

[ThiagoSarmento · Accepted solution]

Hi kostadin_terziev,

Exactly, the patch will remain and will work as a separate solution.

Basically, you are going to download the patch solution .zip and upload this to production. The only thing that can confuse is that when you download the patch content, the .zip will have the namespace (ID) of original solution.

You don't need to download the .zip from original. You can download the patch, it will reference the original solution.

Please, take a reading on the below blog, at least until "Phase 5: Deployment to production"
https://blogs.sap.com/2015/08/27/sap-cloud-applications-studio-deployment-landscape-basics/

Regards,
Thiago

[kostadin_terziev · Accepted solution]

Thank you thiago.sarmento !

It is clear now.

[anant_acharya]

@kostadin_terziev Kindly confirm if you are developing your Patch solution for the first time, then its expected behavior as explained by Thiago it will always consider patch new namespace.

However if its subsequent patch solution from dev to test ( QA) system then, that scenario needs to be further checked as communicated earlier.

Regards
Anant

[anant_acharya]

Alright, then i would suggest to report an incident as this may require deep analysis from backend to confirm the root cause.

You can also refer to Patches on customer test tenant | SAP Community

Regards

Anant

[anant_acharya]

Dear kostadin_terziev,

If the solution was normal Assemble & Download from your source development tenant then yes it should take the Original in the target test system.

I could see below could be the possibility:

1. If the solution was Downloaded as Download as Copy and then upload to the test tenant,it may have new namespace generated.

2. During upload if the older patch exists ( Did you got any pop up) Replace Patch solution or Original in your test target system ?

Please check and confirm from your side, if you still cannot figure it out please report an incident to SAP, so that we can access the backend and guide further via an incident.

Regard
Anant

[kostadin_terziev]

Hello, Anant.

It was normal assemble and download process.