Introduction
“Unified Sandbox” is among one of the most notable features delivered in the latest release (Release 13 19D) prior to this (in 19C) we had to opt for the option. I did try to explain a little bit details of the Unified Sandbox in one of my previous post (link here) but in this post let-us try to understand it with a very simple example.
As a part of this example we will create two sandbox (say AH_Sandbox1 and AH_Sandbox2) and we would try to make following changes:
Now from the above image we can clearly see that the delivered values of the Label were Grade and Grade Ladder which we have modified to Rank and Rank Ladder in AH_Sandbox1 and Group and Group Ladder in AH_Sandbox2.
We can clearly see that there is a conflict here.
We can search for available sandbox with names starting as ‘AH_Sandbox%’
Let-us try to publish AH_Sandbox1 now.
When we open the page from Navigator->Configuration->Sandbox->AH_Sandbox1 we could see a banner message which would say “Refresh needed”
Once we click there we can find all changes made in the sandbox
We should do a refresh before we proceed with publishing the sandbox. During the refresh we would get messages stating the different conflicts and would ask us whether we want to accept the changes or not. Once you choose to accept then the changes will be merged.
This will be followed by a refresh (triggers automatically)
Once the refresh is complete one can continue with publish process.
Once we publish the sandbox we can see it in the published sandbox section.
Next, we will try to publish AH_Sandbox2
Now we have changed the value from “Grade” to “Group” and “Grade Ladder” to “Group Ladder” but since we have already published the first sandbox where the names where changed from “Grade” to “Rank” and “Grade Ladder” to “Rank Ladder”. So in the mainline metadata we do not have any value as “Grade” or “Grade Ladder” hence we would see an unresolvable conflict.
As such, we would not be able to publish this sandbox (which is what the Unified Sandbox feature offers).
We would leave the sandbox and check if the changes published via AH_Sandbox1 is visible.
Summary
From the actions performed above we can clearly conclude that “Unified Sandbox” does provides us a clear view of the concurrent changes being made on same object and shows both “Resolvable” and “Unresolvable” defects and provide a solution for the same.
We could clearly see the merge log for (AH_Sandbox2) which shows as below:
With this we have come to the end of the article.
Hope you guys have a nice read.
Apps2Fusion Articles 