creating patch

[former_member629209]

Hi,

i would like to create patch for 1st time, but i try to enable the patch, there is warning message

from the message state that it will disable original solution and remove scoping.

now my question is:

1. current project is closed, should i create change project for this? and rescope again? even though bac file is same

2. after enable patch and tested ok, should i assemble the patch which means there are 2 solution (original and patch) and which means production also have 2 solution after i upload later.

3. if there are 2 solutions in production, should i enable it (patch solution) manually

4. as per my understanding, all data from custom BO will be invisible/gone, is there any auto process copy data from original?

Regards,

Oscar

[VVancalbergh · Accepted solution]

1. After creating and enabling the patch solution the original solution along with every data linked to it is hidden (until you re-enable it). So from a data standpoint you're starting over. So yes, re-scope.

2. When you Assemble and Download the patch solution the assembled file will have everything in the patch solution (and ONLY that solution) BUT everything will be renamed to the original solution ID. So if you upload it in PRD you will only upload 1 solution.

3. Not applicable.

4. No copy. You start over.

5; Yes. That is why I recommend moving to a patch solution as soon as possible, before you start scoping and preparing data.

Extra: We (at Delaware) have requested and started using a Development Tenant. Positives: All solutions are "Patch Solutions" immediately. Independent of Customer Tenants. You can develop a solution for any Customer ID, so the Test Tenant doesn't need to be ready to start developing. Negatives: You cannot use a "References" file to reference Adaptation Mode fields in code. Every customer solution is grouped up on the same tenant -> may be untenable in the future. If someone Assembles and Downloads a solution the other devs cannot do db operations like add fields until they're done downloading, even if they're working in a completely unrelated solution.

[former_member629209 · Accepted solution]

Hi Vincent,

thanks for detail explanation

1. one more thing, to rescope in test means that i should create change project in production and copy to test and use that profile for patch solution.

2. when i assemble the patch, is the original solution also has same version with patch? if yes then i must upload solution first to production since merging change project only can be done if solution is same right?

Regards,

Oscar

[VVancalbergh · Accepted solution]

I'm a ByD Dev. We don't have "Change Projects" so I can't answer that.

But I can say that, when you Assemble and Download your patch solution, the Original Solution on the Test Tenant stays at version 1. Usually this never changes. BUT you CAN open the Original Solution and upload the new patch solution file into it. This will upgrade the Original Solution to be the same version as your Patch Solution. Though, before we had our DEV Tenant, we never did that because we usually didn't work with our Original Solution on our Test Tenant after creating the Patch Solution. The Original Solution is just a remnant (I don't know if you can delete it, because it's quite useless).

With the DEV Tenant it's no longer a problem since we don't create Patch Solutions on our Test Tenants anymore.

[former_member629209 · Accepted solution]

Hi VIncent,

to make it clear case

test tenant

original solution = YS (ver 1)

patch solution = YSP (ver 3)

after assemble :

original solution = YS (ver 1)

patch solution = YSP (ver 3) which file will refer to original solution. will it be ver 3 or 1?

production

original solution = YS (ver 1)

after upload from file become same as ver in the file. if it is 3 then could it be a problem?

Regards,

Oscar

[VVancalbergh · Accepted solution]

A Download & Assemble of YSP v3 will create a YS v3 file (even though YS on Test Tenant is still version 1). The download converts everything that says YSP to YS.

Uploading this file to PRD into YS v1 will upgrade it to YS v3. This is not a problem.

[former_member629209 · Accepted solution]

Hi Vincent,

thanks for clear explanation

Regards,

Oscar