SAP Cloud SDK : Custom Field Value removed After Creation of Patch Solution
We have scenario to create extension BO for Lead we have created 4 fields and that fields we have added into Account screen. When we create Lead and "Convert Account and Contact" that custom fields from Lead is coming under the Converted Account / Prospect. This Functionality working fine.
Now in above scenario we have added Custom OVS on Lead as well as Account screen and to make custom OVS we have follow below steps:
1) Create custom bo and store data through XML file Input.
2) Create OVS for above custom BO.
3) Add this OVS into custom field that we have created into Lead screen.
In above case all the scenario working fine.
we have created 1 custom button on Lead screen, but customer want to remove / hide that button from Lead screen.
Now we have create patch solution for this deployed solution and we have only remove custom button from Lead screen using UI designer The Problem is when we Enable the Patch solution all the data under Custom BO and all the data used in Lead screen as well as Converted Account using Lead with Custom OVS from Custom BO will be gone.
Also when we enable the Original Solution I can able to see data under Custom BO , Lead Screen , Converted Account using Lead and Custom OVS.
Can anyone help me to do some changes into patch solution is really effect the data?
Why the data will be loss when we enable the Patch solution?
why the data comes when we enable the original solution and disable the Patch solution ?
Stefan Hagen replied
I've explained this here in Phase 3 - Switching to Bug Fix mode:
Original and Patch solution are completely separate solutions. Data you create will be stored in the currently enabled solution. If you enable the other one, all custom / extension fields will be empty if no data was created with this solution active, yet.
But to answer your question: There is no way to move data from one solution to the other. You can enable the patch solution and create new test data and work with newly created data. Don't forget to also switch the namespace in the integration in case you're using custom web services.
The first link posted in this thread also explains the behavior. Did you read it? I don't think so. It explains exactly your issue.