So in this lecture we are going to understand how do we deploy changes from one environment to another
environment using change sets.
So change that is a concept when you group all the components that you want to migrate from one or two
under the art and that can be for a specific god requirement or that can be for multiple requirements
or for a particular sprint on the object it can be different but the whole concept of change its use
for migrating the competence from one organization to another organization.
Do remember that change is to be used only for deploying metadata and not data.
Say for example you migrate the icons object are maybe under that object from the deaf to Kuwait.
No one really object and it's related metadata.
That is a field validation rules and all those gets migrated but not the data that is there with accounts.
And then we talk about change that there are basically two types of change it.
One is the old one change it and the other is that it won't change at all and maintains it is basically
the set of changes that is there in the sales organization and that you want to migrate it to the destination
organization and inbound change it again like it is a set of changes but that exist in the destination
organization.
Very basically want to deploy the changes.
Let's understand this concept that some few instances say for example that is a custom field and that
but if it is a custom field you want to migrated from Beth to Kuwait.
So the field is existing in death and you want to migrate the competent that is the custom field to
do it.
So the self organization becomes death and the destination organization becomes QB slowing the sales
organization you'll be creating an old book chain set and the destination organization now you will
basically access the inbound change it and deploy the changes to a staging.
So the source is Kuwait and the destination is staging.
So the source there you create doubt would change it and the destination is that in won't it seems it
similarly stage into production.
So as a staging destination as broad staging to do a soul as a staging destination askew we brought
you we stood a soul as this bra and the destination askew we don't like there are multiple instances
that initially you have the sales organization and the destination organization and do remember that
it is always in the sales organization that you'll be creating the album won't it and the destination
org you will access the inbound chain set and then deployed in their respective order.
But in this scenario when we talk about the multiple sandbox environments and the production environment
it is not a necessity or it is not by default that you can migrate competence from any on to any art
meaning which a sandbox we have left you in staging right.
So we know a death to do it you would begin my edit from dev to QE to age def def to staging staging
to def staging to do a two way defraud brought to staging brought to Dev write there are multiple combinations
but it definitely does not by default that you can deploy components from anyone to any art.
It all depends on the deployment settings that the set defined in the organization.
Now let's see how do we access all these information and sales force.
This is the developer edition account that we have and as we can see here under Bill there are only
three options customize create and develop right.
But actually in real time in sandbox environments and in production environment there'll be a fourth
option out here which says deploy and under deploy that is before other options which saves in won't
change it I won't change it deployment status and deployment settings and thus the larger are options
that is our deployment status and the deployment settings you can very much see it out here.
But then like ideally you cannot connect the SA development additions account with any of that icon.
So like we can already use these options as such but in real time in sandbox environments and production
environments we use both options for deploying the metadata from one or two one of that arc.
So for us to better understand the concept of changes and how do we deploy confidence likely log into
a realtime sandbox environment and let me show you how do we basically do that.
So this is a real time a sandbox environment that I have logged in and as you can see here it says it
is a def sandbox and this is all what does real time.
If you log into the dev sandbox it seems like Dev sandbox Oculus is and what's it safe.
And box are all that you are sandbox video blog then it says it is and that is pointing sandbox and
production and it displays nothing.
So this is the dev sandbox that we have logged in and as I told you it is not necessary that we can
migrate from any sandbox to production or any sandbox to sandbox and production to sandbox.
It all depends on deployment settings.
So how do we access the deployment settings as you can see here.
There is a fourth option out here which says a deployment and under deploy we have four other options.
I'll one change that involve change that deployment settings and deployment status and it is this deployment
settings a defined from sandbox we can access which all send boxes.
So let me click on continue to click on continued we basically show you all the connections that is
available in your audit as you can see here.
You know we have logged into the dev sandbox so it is showing us the connection for a def sandbox with
the other environments that we have.
The other environments that we have is only cube and staging and production environment so we can very
much rooted out here.
It seems like this organization is deaf that is a developer sandbox and that production basically does
it do it.
Meaning from Def you can deploy changes to production and from production you can deploy changes to
death and for Clay it says from that you can deploy it to QE but it is not the other way from Kuwait.
You cannot deploy the changes to death.
And finally the staging sandbox from if you cannot deploy the staging and from staging you cannot deploy
to death meaning you cannot use a state changed it for deploying changes from death to staging or staging
to death.
But basically it gives the overall idea but then you can click on the organization detail and you get
to check out the details.
So like we go ahead and click on production so these are the details that we see here.
What it says allows in bold changes accept old bone changes meaning you know from dev all domains like
from there it is going out right.
So he accepts our board changes.
So from that it can go out and some production it can come in.
So that's it is in both options subject so more than possible possibly left the broad and Proctor def
and if you click on it you can basically edit the connections and now you can see after you click on
edit the checkboxes has become editable and if you uncheck it then the connections will get updated
accordingly.
So this is a deployment connection between Devon production environment.
Okay.
So next let's understand about QE.
So for QB what do we see as we can see here from Beth you can deploy it to QE but from QE you cannot
deploy to death right.
Okay so now let's understand on the deployment connection.
So we got to click on QE.
Once you click on QE it gives you the details of the connection and it seems like there are more in
our bond changes that are not in bold changes sorry and our bond changes are checked meaning richer
as our bond changes are check from Ben it can go out right.
From there it can go to QE but in bond is not checked meaning from QE it cannot come into death.
So that's a meaning of this.
So you can again click on edit and you can access this.
So like if you check the check box what happens it becomes too late.
Therefore the Q rate and QE 2 death and next is a staging environment.
So what does the connection order the deployment connection between the events and measurement.
So once you click on staging he did show you the connection information between the events staging as
we can see both the checkboxes are unchecked meaning which from there it cannot go to staging and from
staging it cannot come into depth.
So these are the same things that you can basically see and basically make using the deployment settings
option using the option of deployment settings.
You control the settings of deployment across various sandboxes and the production environment that
is there any at all.
As a time for me to show all these information in real time basically I have taken some screenshots
so that you understand the concept better.
Okay now I feel understood the concept of deployment settings how do we use deployment settings for
setting up the deployment connections across the various on.
Let's take a requirement and let's use change its for implementing this requirement.
So the requirement is that on a couple of confidence that we want to migrate from dev to Kuwait.
So those competence are existing in that and those competencies we want to migrated to Kuwait.
So which on competence I.
There is a field that is a custom field called this DSP and it isn't the object accounts and that is
a validation rule.
Guileless test validation tool and it isn't the object context.
So these two companies they are available in the dev sandbox and we want to migrate it took us sandbox
and we are going to use this.
We are going to do this using change sets.
So the solution approach will be the source organisation venal it is death and the destination organisation
is great and we know the old Bunch instead will be creating it in the source organisation so it doesn't
get and the inbound change that will be in Kuwait so far for deploying the changes from dev to QE using
teams that we have got to follow all these steps first as floods we got to create the album change that
in death and your to add all the competence to be migrated to Golborne change it and then we got to
applaud the change head to Kuwait and then we go to access the inbound change that incubate and validate
the change that in Kuwait and finally deploy the teams that Kuwait no let's do it one by one so step
one is to create an all bunched incident deck so first let me log into the dev sandbox so I have logged
into the dev sandbox as you can see here and now we got blacks as the old Montaigne set said so as we
know all the options that are available and they deploy so go for old chain it click on old one chain
set and this gives a description and as you can see here you can use change it's for only migrating
the complements from one organization to the connected organization and not only like unconnected like
it can I tell you it can only deploy changes from one organization to connected organizations go click
on continue.
So once you click on going you can see all the Bond changes that were created from that flight to whichever
organization it can be like it can be too.
Q Well can be the staging on whatever so all these out of the old one chains that we know previously
existing flood watch libraries.
And you can see like modified by which person hand the date.
So now like our objective is to create now maintains it.
So let me click on new for creating old maintains it and it's asking for a change that name.
So maybe let me say this print and the description description is very important.
So in the description you got to say for which purpose basically you are creating this I won't change
it.
But here let me again say I'm desperate but ideally like in real time you'll say like for which purpose
for you know whether it is a bug fix ordered the maintenance audit or some new development or whatever
reason you are creating that out maintains it.
So click on Save
and it all.
MONTAGNE That is created by the Alan Bond James it is just created.
That's all it is.
It does not have any chance at competence in that.
So once you create the old ball and chain it then you got to add all the confidence to that chain it
so click on add so once you click on it you know there is a problem for you to say like which component
I think belongs to and here it will list on all the competent types that is available say for example
apps or triggers on Rob Fazli outsider fields or labels or objects or mission settings or whatnot.
So all the money that tapes are listed on here and you can select which competent type that it belongs
to.
And then you got to select a particular component so ask but requiring regard to migrate to competence.
One is a custom field.
And the other is a custom validation tool right.
So first let's go ahead and I did custom field so let me go for custom fee.
It will list on on the custom fields I've got existing in the ARG and you've got to pick yours.
So ours is the best fee.
So let me search for test field go for it be search for test field
OK.
Select the best fee and it says like it it belongs to account for the art type account.
So act to change it.
So the first component we have successfully added to that chain set that is access fee again click on
add and then go for validation rules and it is of all the validation rules and the name of our validation
rules desk violation do.
So let me select that I will change it.
Perfect.
Now that we have created it changed it and we have successfully added all the competence to the chain
said.
Perfect.
So what next aspect of the steps we have completed step one that is creating an album untainted and
Def done adding all the competence to be migrated down.
So we are done with step one and step two.
So finally step three build the chains that took you away.
All right.
So just that we have created a whole bunch instead in debt.
Now we got to upload the chains that took you eight.
So once you have added all the communist through the chains it you can see the option upload to be enabled
so click on upload and once you click on upload it will list on all the target organizations and how
we listed all the target organizations.
It lists only those organizations that is defined by the deployment settings.
Say for example from Def we can do with one lead to Kuwait and production right then does not have connections
with staging.
So basically does not listing those staging.
It is listing normally debit production and Kuwait and for other criteria.
We have to deploy the competence from Def to Kuwait right.
So a quick look on Kuwait and let me say upload
perfect.
So it says your upload is currently in progress.
We'll send you an e-mail when it is complete.
So it means the I won't change it that we have created in Def No way.
This deployed to Kuwait.
All right.
Do remember that one the chains it is uploaded to Kuwait.
The changes are not deployed in Kuwait.
Just the change that that we have created and Def it is uploaded to Kuwait.
OK.
And it seems like it is uploaded successfully.
Now we can access the chain set it to environment.
So how do we access that Jane said in the U.N. Environment.
How do we basically validate the chains and how will we deploy the changes to Cuba and all those remaining
details we'll discuss in the next lecture.