Transcripts
1. Course Introduction: or some. We are in the final segment off over course. Siris on Salesforce Change Management. You have truly come a long way. Andi, I really appreciate you for your hard work and commitment here now that in our previous sections that we have had a good understanding about the the overview offer change management sandboxes how to manage sandboxes about metadata, metadata, export, automated, meditator, export and all these. So the one other segment that spending that we need to learn is about a deployments, meditator deployments so that we are going to cover in this particular section. So here we learn about that. How to establish a connection between Tuaregs and Salesforce. How toe deploy meta data from one organ toe another Argh! What are all the various troubleshooting techniques that we have water? All the various best practices that we can follow in this. So all these Kansas fear going to learn. And as a release manager, it is definitely essential to know the concept, right? And also, if you're an admin or developer, this is definitely a value are for your skill set Happy learning
2. Salesforce Metadata Deployment Overview: aspired. Does this at least management for the next topic that we're going to discuss about is how do we deploy meta data? First of all, let's understand the concept off. Moderator. What does moderator very precise It is. Data about data basically defines a rich set off confidence that includes all aspects of the full Starcom functionality. Be to the user interface. Be the work flows, be the validation rules, be the apex classes, beats the triggers, be the official force pages and everything that's part of the four star come functionality . Everything comes under Merida and here I believe we understand the difference between moderate and data. Say, for example, Accounts Accounts is the object. It has got some 10 feels. It has got a couple of validation rules. It has got a couple of workflow rules in that on. There are some five triggers in accounts, or it's all these forms. Metadata off accounts object on regarding to Dana say, for example, there are some 10,000 account records in the system, so those 10,000 account records they fall under the category off data. So married eyes something that stores data. So this is the difference between metadata and data. Say, for example, law, the application that you're working on. Let's consider some sandbox environments and production environment. As we know there can be only one production environment. That's the real time environment on sandbox environments, like can be many, depending on the business, depending on the requirement how many sandbox environments they have confident has many sandbox environments will act actually have in the system. For our example, let's consider there are three sandbox environments. The death sandbox, Cuba sandbox and the staging sandbox. On production, you know there is only one production environment. So whenever we want to make some configuration changes to the system, every project has got their own deployment process because every sandbox that exist it exists for a particular reason. Say, for example, of the deaf sandbox. It is purely for development Cuba Sandbox for doing all the Cuba activities, the staging sandbox kind off a preproduction. There can be other sandboxes as well say, for example, purely for the purpose of integration, testing or for doing some people season, so there can be multiple reasons for a sandbox to exist in the system. So last night, Manasseh develop or as a sales was concerned, Um, that you work in a system, work in a project. You got to understand what all the different sandbox environments that is being used on What is the purpose off those environments on considering or deployment? What is the process that they follow for following the deployment? So in some products, it might be like up every change that goes from death and then Cuba and then staging, and then they migrate to production on In some projects, it is like a no Cuba sandboxes purely for some other integration. So, you know, we're like they do not bother about the Cuba sandbox through the deployment process is like a death and then to staging and then to production. So you distort Lee after the business totally up to the project, the deployment process that they followed or deploy changes to production
3. Salesforce Packages: The first concept that we are going to discuss about is Salesforce packages, one of Salesforce packages. And how do we use salesforce packages for migrating the confidence from one arc toe? Another arc? The concept of packages You can very much compare this with the normal activity that we don't say. For example, I have some couple of documents on and wanted to share these couple of documents with you. So what will I do? I can just send out an email. I passed those documents and send it across to you, right. You get that email, you get that document as simple as that right package. As the name stays, it's a package of confidence. Beat AB's beat fees, beat email templates, bees between force pages, whatever you can group all the competence, which we will share on putting a package and share it. And when we talk about these packages, there are basically two type of packages. One is a managed to package and the other is on managed to package. So what does that managed package? And one's a managed package package? As we know, it's a package of competence, right? Is a back off confidence So I say, for example, I create unmanaged package on in that I unmanaged package. I have got a couple of objects. I have got a couple of feels on, say, a couple of emails template So I created and managed to package and I uploaded and I get a I get that link and you use that link on You can install that and managed to package or effect. But now ones You do that installation off the unmanaged package All the companies that you install you can pretty much work on those confidence. You can edit those competence. You can delete those competence. You can do whatever you want with those confidence That is an unmanaged package. Basically, I will not have any control on those components that with which I created an unmanaged to package. But in the managed packages, no like that. Once I create a managed package and once I said it across to you, you can very much install the managed package. Yes, but he will not have any rights on those competence. Basically, you cannot edit those competence that you have installed. I am managed to packages on those the APP exchange acts that we installed, like we discussed in the previous sections about the field trips or the mirror, such or any app exchange up that you can talk about all those are managed packages. You basically cannot evict those competence that is there near ARC. But I managed to packages. It is just like you know, I'm I'm just giving away some confidence. You get installed, those competence and you can work or call them any of them. Delete them. It's up to you. So I managed packages. There's no concept off upgrading those packages, but managed packages Yes, they can be upgraded, even these up exchange abs What you installed the company who owns the APP exchange APP they released upgraded Washington's So you can very much upgrade your package that managed to package. But there is no concept of upgrading on my Spacca. Gist on managed to packages are very much used to for handling. The moderator on the managed packages are very much useful for handling the applications, the applications that they build it off. Salesforce decorated with salesforce on in this lecture will understand how do we create and manage to pack it on? How do we share it with others. Good application, Such for packages. You have an option packages, as we can see here that are no packages As such, Creator, go through this description. Let's create a new package. Onda, let me say this package and it's in English on you got to give a description. Basically, you know, you can add a child competence that your united the package go safe. Once done, the package is ready. But the package has got absolutely nothing inside that. Okay, just that the package is done. So what next is we go toe act confidence to the package. So for adding the confidence go click at you can see two sections out here. One is a competent type, which particular competent type that you are referring to add and the others a list of all components that are available. Say, for example, up. These three are the acts that are available for me to share. Say, for example, of buttons. These are the burdens that are available for me to share. Say, for example, call center. Okay, so there are no competence over there. So this is the confident type then like it list on like almost everything that is there in emanated up custom fields, custom objects. Say, for example, custom objects. You can share all these custom objects so far as you got to select the confident type on in that competent, you got to select which component we want to add it to the package. So I let me to some email templates on I have these minimal templates. Let me choose the text email template on the letterhead email simply after the package. And as we can see, the dependencies also gets uploaded by default like we just included only the text email template on the letterhead email template. But for us to install the letter email Templar, we also need the letterhead, which is a cashew, that right? So why they fall? The dependencies also gets attached. Even the training template Training Temple. It is basically the folder in which the email temples displaced. So all those dependencies also get, including by default. And along with that, let me also add let me add some custom fields. Okay, so let me add the number off least floors added to my package. Okay, Perfect. So now that the package has got a couple of even simplest to that. And it has also guard a custom feel attached to it. Perfect. So now that the package is ready, right, we have created our package on. We've added all the confidence that we want to attach it with a package. Perfect. So now what next? Now we go to upload the package. So let's given these details here. Say, for example, are Let me say Jan. 2015 on let me check for any other manager feels upload. Perfect. The packages successfully upload it. So do we moved one thing here that when we are actually migrating the competence from one our toe on the ark are from one person to another person. Then we're sharing the meta data. It is not that you're sharing some files. Why? It is not that you're sharing some documents are you does not like a sharing something. It just like all the packages. All the competence in the packages will get a pure and you'll just have that you are in which they're uploaded. So what you got to do with this particular you are, you need to have it on through those the water you can download the package. You can install the package into our different arc are safe, for example Like you can share those you are with the different person on he can use that you are on. He can't install the confidence that attached to this package. So this is the installation. You are allowed here. What we have on Dhere, we can see the package competence that are basically for resources. And there is one field in the package. So now for installing the package, just go to the link. Okay, so it says this app can be installed. Why? Because this package already exists. So don't know that in the concept of packages, if the fact it is already existing in the destination Argh are like with the other person with whom you are basically sharing the Merida, you will be basically not ableto install the package, in fact, is eight is just north of the package. Even with the park package confidence, if you are trying to install some package confidence which is already existing in the destination are Then it would end up saying that this particular competent is already existing. So I let me open up another Argh! So that began Basically installed this package before doing that. Let me also have the You are a handy so far, taking the you are go for packages and we have created our first back. Is that this test package? Go for test package and go for the versions. You have the first wash in version one point little And there you have the installation You are so just copy. Have this installation you are already let me open up under that are And I'll show you like how to be basically download this package. So I have logged into another Sansa Stark. And this is the installation you are from a package. So just I cooperated. I used it in the water. And now, as I told you earlier, it is just not about the package, even package competence. If they already exist in the art, then it would cause an issue. So you know before that it is asking the system. Ask us whether it should not install or it should basically go for careening. So let me say they did not install And you also have the option Whether it is only for admin. Our users are specific profiles. If you can recall what we did before topics in Japs, pretty much we had the same options. So let me say only for admits and let me install perfect installation complete. Go click on Don on. Now In the destination are you will be able to see this package under install the packages . And what is all that? That that was there as part of this package. We had some email templates. So let me quickly go and see if there are those emails templates available out here. So, yes, the mails simples is available very like it was under the folder off training template. So the folders available Training template on within that we have these two templates fax email template on letterhead, email template. And there was another field that is a custom feel on. We added it for the object accounts. So let me go for fields accounts. Andi, I think like it was the field. At least the floors number off. Lease floor. So light. So did this particle of figure number off lease the floors? We did not create it in this arc. Basically, it was created different art. Andi applauded in the package and we used that installation you are on now that we have installed a package. So as a result, all the confidence that were as part of the package, they also go install. And now that as you can see on this particular field or on the package competent that you have install, you have all rights like your other competence. Say, for example, I want to delete this feat. Oh, yes, I wanted to lead this field as simple as that. So we can you know very much you stuff confidence. You can very much work on the components that you have install via unmanaged to package. So the package that we just created the uploaded Winstar's is an unmanaged package on good examples. Off managed packages are those which you install it from the APP exchange APS The field trip are the metadata search. Are the other app exchange upset? We discussed. So this is all about packages. First, you go to create a package at companies to the package on upload the package on all these you lured in your souls organization in the target organization are in the destination organization. You basically use that installation you are on. You install all the confidence that comes as part of the package, but do remember that the packages can be used to for migrating the metadata from one or two another art. It is definitely not a best practice are recommended. Practice for us to migrate the competence from your sandbox toe, other sandbox auto production work. We have to go with other methods, like using chain sets are using snapshot our music full start a mighty before basically migrating the data for deploying the data from one upto on the art. But this whole concept of packages is about sharing the Merida maybe with a team member or maybe for the minor activities that you do. But when we consider deployments, we have to stick on with the best practice on the tools that we use for other deployments.
4. Deployment of Metadata using Changesets Outbound: So in this lecture, we are going to understand how we deploy changes from one environment to another environment using chain sets. So change that is a concept wherein you group all the confidence that you want to migrate from one arc to another arc and that can before ah, specific or requirement are there can be for multiple requirements are for a particular sprint on the objective can be different. But the whole concept of chain says is for migrating the competence from one organization to another organization. Do remember that chain says we use only for deploying metadata and not data. Say, for example, you migrate at the cons object are maybe another object from the deaf to Kuwait. You know, one. Leave the object on its related metadata. That is a field validation rules and all those gets migrated, but not the data that is there with accounts. And when we talk about changes, there are basically two type of change sets. One is the out bone changed it on at the other in bone chain, said Allah, Bone Chain said is basically the set off changes that is there in the Souls Organization. On that, you want to migrate it to the destination organization on In Bomb changed it again like it is the set of changes, but that exists in the destination organization. Very basically want or deploy the changes. Let's understand this concept with some few instances, say, for example, there is a custom field on back particles. Custom feel you want to migrated from death to Kuwait so the field is existing in death and you want to migrate. The confident that is a custom field took you it so the sauce organization becomes deaf on the destination organization becomes cubic. So in the source organization you'll be creating an outboard chain set on the destination organization. Now you will basically accessing in bone, Chain said. I deploy the changes curator staging. So the sources Cuba and the destination is staging. So the source there you create our own Change it on the destination Is that in bunch it's changed. Similarly, staging the production sources staging her investigation is proud staging to give away Sosa staging destination Is Cuba brought to Cuba, stood sold. This product on the destination is Cuba. You like there are multiple instances, very nearly. You have the souls organization and the destination organization and do remember that it is always in the souls organization that you'll be creating the all bold change sex on the destination. Og you will access the involved chain set on deployed in that respective are. Why didn't the scenario? When we talk about the multiple sandbox environments and the production environment, it is not necessary. Or it is not by default that you can migrate competence from any arc to any arc. Meaning which a sandbox we have left you and staging. Right? So we know a definite you it would be can migrate from death take you away. Too bad you deaf death to staging Staging to death Staging took you a Q beta fraud brought the staging Proctor death right? There are multiple combinations, but it definitely does not by default that you can deploy competence from any mark to any Are it all depends on the deployment settings that doesn't defined in the organization. Now let's see, how do we access all these information and salesforce? This is the developer tradition account that we have on as we can see here under build their only three options customize, create and develop right, but actually in real time, in sandbox environments and in production environment, they will be fourth auction out here, it says Deploy on under deployed that it before other options which say's In Bone Chain said, I'll bone chains it deployment status on deployment settings on the last two options. That is the deployment status in the deployment settings. You can very much see it out here, but then, like ideally, you cannot connect this developer tradition account with any other account. So, like we cannot use these options as such. But in real time, in sandbox environments and production environments, we used those options for deploying the metadata from one to another arc. So for us to better understand the concept of changes and how do we deploy competence, let me log into a real time 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 death sandbox and this is our does Israel time. If you log into the death sandbox, it stays like that sandbox are curious and box. It's excuse and box. Are you know which you were sandbox that you have loved? And it says it is that corresponding sandbox on production, it displays nothing. So what? This is the death sandbox that we have loved him on. 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 the deployment settings. So how do we access the deployment sittings? As you can see here, there is 1/4 option out here which says a deploy and under deployed. We have four other options. Alban chain set in bold chain said the deployment settings and deployment status on it is this deployment sightings defines from with sandbox we can access which all sandboxes. So let me click on Continue, you click on Continue. It will basically show you all the deployment connections that is available in your art. As you can see here, you know, we have logged into the death sandbox. So it is showing us the connection for a deaf sandbox with the other environments that we have the other environments that we have is only Cuba and staging on the production environment. So we can very much relate out here. It stays like this organization is deaf. That is a developer Sandbox on with production basically doesn't do way meaning from deaf. You can deploy changes to production on from production. You can deploy changes to death on for Cuba. You know, it says from deaf you can deploy to Cuba, but he does not the other way from Q way. You cannot reply the changes to death on finally the staging sandbox from death. You cannot deploy to staging on from staging. You cannot deploy toe death, meaning you cannot use state chain says for deploying changes from deaf to staging are staging to death but basically it gives the overall idea. But then you can click on the organization detail on you can check out the details. So, like we go head like Mickey Cohen production. So these are the readings that we see here what it says allows in bone changes except all bone changes meaning, you know, from death all domains like from David is going out right? So it accepts our bone changes, so from them it can go out and some production, it can come in. So that's the reason. No, both options subject. So both the rate is possible deaf to plot and proud to death. And if you click on it, you can basically ended the connections. And now you can see after you click on edit, the check boxes has become irritable on. If you aren't check it, then the connections will get updated accordingly. So this is the deployment connection between Devin production environment. Okay, so next let's understand about Cuba. So for Cuba, what do we see as we can see here from death, you can deploy to Cuba, but from two way, you cannot deploy toe left, right, OK, so now let's understand on the deployment collection. So we got to click on Cuba. Once you click on Cuba, it gives you the details of the collection and it stays like that. Have no in all ball changes that are no involve changes. Sorry, Andi know our bone changes are checked, you know, meaning richer as our bone changes are checked from them, it can go out right from David can go to Cuba, but in bond is not checked, meaning from Cuba. It cannot come into death. So that's Ah, meaning off this So you can again likely contradict on you can access this. So, like if you check the check box, what happens? It becomes two way left. Cuba actuator. Death on nexus. A stating law environment. So what is the connection with the deployment connection between Devin staging environment ? So once you click on staging, it'll show you the connection information between event staging. As we can see, both the check boxes are unchecked. Meaning which from death, it cannot go to staging and from staging. It cannot come in tow death. 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 savings off deployment across various sandboxes on the production environment that is there in your ARB as it's hard for me to show all these information real time, basically have taken some screenshots so that you understand the concept better. Okay, now that you understood the concept of deployments, I think how do we use deployment settings for setting up the deployment connections across the various on Let's a take a requirement. Onda. Let's use changed its former implementing this requirement. So the requirement is that a couple of confidence that we want to migrate from death to Cuba. So those confidence, our existing in death on those confidence we want to migrate into Cuba. So which arm components are that? There is a field that is a custom field called us deskee when it isn't the object accounts and that is a valuation room called us test valuation rule. And it isn't the object contacts. So these two confidence, they are available in the left sandbox and we want to migrate to took you a sandbox on. We are gonna use this. We are going to do this using chain sets. So the solution approach will be the source organization. We know it is left on. The destination organization is Cuba, and we know the album change that will be creating it at the source organization. So it doesn't death on the involved change that will be in Cuba so far. Ah, for deploying the changes from death to Cuba using chains, it we have got to fall all these steps first is first. We go to create the outboard changed it in death on God at all, the competence to be migrated without bone, Chain said. And then we got a Plourde the chain said to Cuba on Then let me go to access the inborn chains that in Cuba on validate the change it in Cuba and finally deploy the change that in Cuba No, let's do it one by one. So Step one is to create an outbound train incident. So first, let me log into the death sandbox. So I have logged into the deaf sandbox. As you can see here on now, we got to access the old born chain set. So as we know, all the options are available in the deploy. So go for our born chain set, click on or born chain set. And this gives a description. And as you can see here, you can use changed it for only migrating the confidence from one organization to the connected organization and not, you know, like, unconnected like it cannot do. You can only deploy changes from one organisation. Toe connected organizations go pick on. Continue. So once you click on, continue and see all our bone changed its that were created from death. Like too much of a organization, it can be like it can be toe Ah, Cuba. It can be to staging or whatever. So all these are the old one, chain said, which are no previously existing for whatsoever reason and you can see, like modified by which person on the date. So now, like of our objective is to create out born chain set. So let me click on you for creating all born Chain said. And it's asking for, ah, change nickname. So maybe let me say test sprint on the description Discover here is very important. So in description, you got to say for which purpose. Basically you are creating this hour born chain said. Ah, but here let me against. They are desperate but ideally like in the real time, you say, like for which purpose for, you know, whether it is a boxer, exhorted the maintenance are into some new developmental whatsoever reason. You're creating that out born chain set, So click on Save and now the whole bunch incidents created. But the album change it has just created, that's all it is. It does not have any change, said confidence in that. So once you create our bone chain said, then you goto aren't all the confidence to that change said so click on pad. So once you click on I, you know there's a problem for you to say, like which confident type it belongs to. And here it will list on all the competent objectors available. Say, for example, APS or triggers are paisley outs are fiends are labels are objects, permissions, settings. It'll water So all the metadata tapes are listed on here on you can select which confident pipe that it belongs to. And then you go to select a particular competent. So ask for our requirement. We go to migrate to competence. One is a custom field, and the other is a custom violation rule. Right. So first, let's go ahead and I d custom field. So, like we go for custom field, it will listen. All the custom fields are not existing in the art, and you go toe pick yours. So ours is the cast fee. So let me search for test feel Go footbe search for test feel Okay, So like the test feel and it stays like it, it belongs to account for the art type account, so act to change set. So the first confident we have successfully addict of the chain said that is the best field again. Click on add and then go for validation rules, and it will list on all the validation rules on the name off our validation rules desk violation rule. So let me select that actual change set perfect now that we have created a chain said, and we have successfully added all the competence to the chain set for fact. So what next? Ask for the steps we have completed Step one that is creating an out born, chain sitting death done adding all the confidence to be migrated done. So we are done with step one and step toe. So finally, Step three upload the change that took you pay. All right, so just that we have created a whole bunch incident death. Now we got to applaud the change that took you. Wait. So once you have added all the confidence through the chain said you can see the option upload to be enabled. So click on, upload on. Once you click on upload, it will list on all the target organizations and how it listed all the target organizations . It list only those organizations that is defined by the deployment settings. Say, for example, from death we can do it only took you and production right. Death does not have connections with staging, so basically does not listing those staging It is listing normally Devin que production and Cuba on before our criterion, we have toe deploy The confidence from death took you away, right? So let me click on your way and let me say upload perfect. So it stays. Your upload is currently in progress will send you an email when it is complete. So means the airborne changed it that we have created in death. Now we does deploy to Cuba. All right, Do remember that only the chain said is uploaded to Cuba. The changes are not deployed in Cuba. It just the chain said that we have created and death It was uploaded to your way. Okay. And it stays like it is uploaded successfully. No, we can access the chain set into environment. So how did the access that change set in the Cuba environment? How do we basically validate the change that I will be deployed. The changes to Cuba on all those remaining details will discuss in the next lecture.
5. Deployment of Metadata using Changesets Inbound: This is with continuation to the previous lecture off deployment off moderator Using chain sets on other requirement is to migrate the following components that is a test feel and a validation route from deaf sandbox to Cuba. Sandbox eso The source organization is deaf and the destination organization is Cuba. On the various steps for deployment to create our bunch in certain death, we are done adding all the components to be migrated. We're done with that, uploading the chain said to queue it. We're done with that Steptoe. So the last three steps upending, accessing the email chain said in Cuba. Validate the changed it in Cuba and finally deploy the chain said in Kuwait. So now let's go ahead and do the remaining steps to complete the deployment. First, let's log into the death sandbox on. Let's take a quick look at the ah chain said that we have uploaded so far chicken the changes that were uploaded. We got to go to deploy all bone chain set, click on continue and this will basically list on all the old bone changed it from Dev Environment on the one that we created is a test print so click on past Sprint. One. Simply contest print. You know, you can basically see all the details with respect to change sex, the name, description and who created it and everything on the in the previous electorate. If, like we applauded, the chain said. So once you upload the change that what happens is the chain set is close to the state is off the chain, said Don't closed. So what does it mean? It means that after that, after you upload a particular chance that you will not be ableto are any more companies to the chain said, Meaning you not be able to make any modifications to the chain. Said, As you can see here, that is new. No new button available over here. But before uploading it, you will have an option off adding confidence, right? So once you click on, either you can add the confidence with change set. But once you applaud, the chain said to anyone off the other connected organization, the state as becomes closed on, then on, you'll not be able to add any more competence. And once that is uploaded, it also gives the upload history like it is uploaded on which date to which target organization. So this is death. And, like the uploaded organization is Cuba and uploaded. By which person? What is the status? It does no upload it Perfect. We are no done with Dave Environment. No. Let's log into Cuba and access Ian Bone Chain set. I have no logged into the Cuba sandbox. As you can see here, it says Cuba Sandbox Onda No, in Cuba, a sandbox. This being over target organization, we goto access, the chain said from in gold chain Set. So set up click on deploy will have an option. Click on in bone chain sex. Continue on here. You can see some description about Imo. Chain said What in bone chains that is all about. Please do read the description on being it. You have two sections. Change that awaiting deployment. As the name says. These are all the chain sets. These are all the in bone chain sets that are available in Kuwait from the Frente other connected organizations. But did saints that are still not deployed in Cuba? They are just laying there and yet to be deployed. Do remember only after your deploy changed at all. The competence that are available as part of the chain said will be available in that particular are. So now that the tooth the two companies that is a test field on the test validation do they are just uploaded to Cuba. They are not deployed to Cuba. So if you just go to our council, object and check for the test, feel that particular field will won't be available. So after applauding, you got to deploy for the changes to take effect on deploy changes. Means like these are the inborn chain said that after Deploy took you away on the chain, said that we created that is a test print washing. One point it'll it has just uploaded to Cuba and not a deploy, so it is still under changes, everything deployment. So, as you can see here, the old bone chain said that you creator on uploaded from death to Cuba. You can access it under imam chains that into it, click on the chain, said name. We'll see the D does here. You can see all the details off the chain, said he tells you, like up or the name description, Expiration date and Souls organization basically from which organization that in both chains that has come because when that is an inborn chain said in a particular organization , it can be from production or can be from any connected organization. All right, so the Royals organization here, in other scenario, is death, and it also gives the details off all the competent settle part off the chain set. So for those in bone, Chain said, basically, you have got three options out here. Validate, deployed and delete so daily as the name saying, You don't just delete the chain said safe or what side of the reason you uploaded? Ah, different chain said. Are you approaching some competence? Which are Misuari uploaded some incorrect competence or whatever. You can just go ahead and delete the change so they won't change. That has gone on, definitely cannot be used for deployment. The other two options. What we see here. They are important that is validate and deploy for any involved chains. At first we got to click on validate on. We got to evaluate the chain said. So what does this validate means? Validated basically validated all the confidence that that part of the chain said on then check for any errors. So let me click on Validated and the system will gives us four options deformed run, local test run, all test run specified tests. All these options out here are with respect toe running test in the target organization. So when you're on test, the system insures. If the overall gold coverage is minimum seven per person on all the test classes and the test methods are updated with the updated configuration changes on they passed the test. But if you select the default option, as the name says, no test will be executed on. If you select the second option, that is a run local test. All the destiny or organizations will be run, except that which is ordinarily from the installed manages package on the third option that is a run all just that he include the test run from the managed packages as well on run specified test. If you are very specific about a some particular test that has to be run, then you can go for the fourth option in the sandbox environments. If you go with the first option that is default, no tests will be executed. But in the production environment. If you choose default on if you're changed, it has got some ethics. Classes are trickles though you choose a default by the fall automatically, all the test will be executed. But in sandbox environment, you respect you off. Whether the change that has got apex classes tree goes or not still like if you choose default nor test will be executed. But it is Northern production introduction if you choose default. And if you're changed, it has got some epics. Classes are trickles, then all the test will be executed. However, it is always recommended that you run local test even in the sandbox environments. But now let me go with the default option that quickly can validate. Okay, Perfect. So it says the deployment starter on prime the progress off the deployment and their deployment status. So here comes the fort option. So go for the deployment state as option, go go for deployment status. And there you can see all the chain said which basically failed in the validation process on was basically succeeded and then validation of their deployment process and other album changed it from death. On the indulgence of that basically guarded in Cuba. It is right here, aspirin, and we can see the status that is a deployment history. The validation succeeded, and it has deployed by which person perfect. So now, like we are done with a step off validation. So once validation is done, the next step is to deploy the changes to Cuba. Even at this point of time, the changes will not be present into a environment. Only after you deploy the changes, then you can access the competence in that you environment. So if we go ahead and click on reply, let me go with the default option deployed. Okay, And again, let's track the progress in their deployment status space, go to deployment status. And then it says the test print is succeeded. The deployment has succeeded. So now the process comes to an end. The deployment has finally succeeded, so the deployment of the competence from death took you way. Basically, the custom field on the validation rules are no finally deployed to Cuba environment on in the accounts object we can able to access the custom field. That is a test fee on the contacts object. We can access the validation route that is a test validation route, so he had have a process of deployment. Using Chain says Come to an end revalidated the changed it in Cuba. Yes. And finally we deployed the chain set in Cuba and also don't note one point that we can use change sits on Lee for creating new confidence are for a bit existing confidence in the target organization. We basically cannot use change since for deleting confidence in assistant and changed, its cannot be used to for renaming competence as well.
6. Deployment of Metadata using Forcedotcom IDE: in this lecture, we are going to understand how to deploy metadata using forced or compelled he actually, to be honest, this four star comedy is not an extensive admin, too, because when you consider deployment to have multiple options, you can deploy using chain sets you can deploy using for strike committee. You can deploy using snapshots you can deploy using full circle migration to numerous options on every project has got their old trusses some use chain, said Samuel. Snapshot really differs. Basically on this fourth start committee is more of a developer tool, and this is used extensively for coding compelling for comparing codes across ours for running tests, for debugging, troubleshooting and for all these. But then knowledge is always very good, right? So that's the reason I have included this lecture in the admin program. So as Hagman's, even if you're not aware off the other features off the tool, At least we know how to deploy competence using for start comedy because deployment is definitely a part of an admin tasks. So that's the reason we are going to this lecture. So first, let's understand what is this four star come I d, he collapses her i d. That is integrated development environment that is basically a single point of contact. You can see that is one single location to manage your code on it is very much widely used in Java C Sharp and C plus plus. If you have had prior work experience with all these Leonard of definitely Normal Eclipse on Four Star comments, basically a plug in for Eclipse that can interact with Salesforce like technology, a four star come optics. It knows your salesforce competence. It knows how they behave. So this full start for my tea. He's a powerful client application for creating mortifying on deploying for Starcom applications. So Step One is to set up the environment for us to work four star comedies. Open source So you don't need any license for that. And as you can see here first, we goto downward Eclipse and then install four Star Committee for Downloading Eclipse Navigato those You are eclipse dot og. So go to www dot eclipse start arc and at the right top corner, you can see the option for download. Click on download and you have multiple options over here, depending one. Whether it is a Mac or Windows. And if it's started a bit or 60 to 64 bit and go for this option eclipse I D. For Java developers on if it's a 32 bit or 64 bit on go and down toward the competent. Accordingly, basically as if I gets downloader takes around 15 20 minutes. Once done successfully, then regard toe install for Stark Almighty. So I think now we got the concept. Full Start Committee isn't standalone applications, but eclipses a very standard, widely used open source programming, too. So we are using four star come through Eclipse Onda Once done. Then we got to install four Star Committee. So now let's go back to the installation steps as we can see here. We're done with this. Step on next to snag it because you want it. So navigational does the water, and there you can find the complete information about Forster committee installation. Follow the steps. You can see the installation steps over here, follow all the steps and complete the installation on that. This shouldn't take more than five minutes. It's actually pretty simple. So follow these installation steps and completely or four start comedy installation. Once done, open Eclipse and you should see something like this and at this point to be out of done with our eclipse and four start committing installation on Let's go ahead with the deployment. Let's first have a quick look at the requirement for the deployment. Let's say, because for change, let's be your deployed a some a validation rule and feels right. So for four start committee, let's say like the are targetting toe deploy a trigger from deaf took you away. So then, is that trigger going? That's test trigger on it is with respect to the object accounts, and this triggers existing in the environment. So other objectivist do you suppose toward committee on to deploy this meta data off the test trigger from deaf toe to environment? So for doing what? All the steps that we got to follow Step One is to create a four star come product from the death sandbox. So what it means is that we are creating a full start come project on. We are including all the relevant competence in the project from the death sandbox, because here are source organization is death and the target organization is cubic. So for us, we got to create that project in depth sandbox. And then we got to to that particular competent to be deployed, and then you have the option of deployed to server using that option. And then we got to follow the career aspect of steps and finally deploy toe cubit. So first, let me go ahead and create a new project file new four star come project. And here you go to give a project name, say, for example, love, let me say our test to deployment. And it is always advised that whenever you create a project in four start committee, you finally appended with the environment playing because at any point of time you try to connect the two to this particular product. It always connects to that particular environment. So now that we're trying to connect to death, so we go to say, best deployment in the environment I just thought about understanding, actually, and the user name password and the security Dokka. So use the name password on the security token. Everything is it related to the death sandbox? So your user name password on the security dokka that you use for logging to the left sandbox. And again like the environment, you have multiple lock options. If you're using production, you go to, say production. What if you're using sandbox, you got to say, sandbox. In other scenario or deaf sandbox, there is a sandbox. So I select deaf sandbox. And then I given that, respectively, days he was the name password and that secular due to open. So once you've given the credentials and connect to the respective environment, the next step is to choose the Merida confidence from that particular environment toe, including the project. And as you can see here, there are four options out here. Apex and Visual Force selected material competence contents off a package, and then that is 1/4 option. Onda. Selecting the option totally depends on a witch meta data competent that you want to basically deployed. So if you are right now, never case the desert rigor. So let's go with the first option that is apex and visual force. By selecting this option apex and visual force, it will basically include all the classes, triggers pages, competence, tactic resources in the Dev organization. But it's not include something like objects feel stabs and all those little include only epics and visual force. On the second option is selected metadata competence. Like if you go with this option, it will list on all the metadata. Compensate is available in the ARB on from that list, you can choose which on competence that you want. Oh, deploy. I say, for example, you want to deploy one trigger on, we want to deploy some tabs. Okay, so you know, like you can you go for the second option and very new can select only because and perhaps Hankins off a package. This will include the packages that is there in your arm and finally doesn't so forever Scenarios Apex and Michelle Force. So let me go with the first option Apex and Visual Force and let me click on finish. This takes about a couple of minutes and once it is done, you can see a project that has got creator that this test deployment in depth on when you expand that you have three options Priority inches reference packages on SRC go for SRC. SRC is the source folder on that contains all the meditate off the competence that you have selected in other cases rituals Apex and Michelle Force. So basically, it includes the triggers classes, competence and the pages. So that's the reason, you know, we have different folders for classes, competence pages and static resources that triggers. So all these are into our project now. Perfect. So our next task is to locate the specific competent to be deployed. Right? So we have created a four star come project. We've been through all that 11 competence. And now for us to select a particular competent to be deployed And for other scenario, we have to select vestry. Good. So let me go to eclipse expand the folder triggers on located best regards. Perfect. Here we can see the best Riga. So right, click on past trigger. And there you have multiple options. Then you have an option for Starcom. So go for full Starcom deployed to server. So this option deployed to server. You use this option for basically deploying this particular moderator from one or tow another arc. Now the source organization is death. So from death, we are deploying it toe another are so go for deploy to server. And now the system ask us to specify to which particular target organization we are trying to connect So here, like we got to given the user name password on the security Dokle off the Q b ark because basically, ever talk a target organization is cubic. So you know the credit sure should be off the Cuba sandbox. And again the environment will be selected A sandbox. So let me give in the details once you have successfully connected to the destination are full. Starcom, I d automatically takes a backup. Creates archive, often destination for start come. Confidence on this step is highly recommended. So go for it. You have options off where those arc if eyes to be safe so you can It is up to you very. You want the files to be saved and then click on next. No, the tool frames out our deployment plan for us. He tends us, which are all the competence that are migrated from the source organization to the destination organization. In other scenario, that is only one competent that were migrating. That is a test trigger, no on and the similar fashion. You can choose multiple competence aspect on the lake as you validate as you assure about the competence to be migrated. Then you go ahead and check on validate deployment. It goes to the validation. Perfect. The validation of successful. So close this and then let me go to click on next and actual executed deployment plant. So this validation you can very much compare it with the process of validation in the chain sets basically checks on a trans the test. So once validation is done, go ahead and click on next on this execute state deployment plan. And, as we can see here, the deployment of success foot. And if you click on view logs, it tells it gives a complete our history offer, which is a source organization, which is our destination organization, which had all the confidence that got my greater on all these details. So click unfinished because we are successfully done with the deployment. And now, if you long into the Cuba sandbox, you will be able to access the test trigger. So let you look into the career sandbox and quickly show you that I have no logged into the Q. A sandbox, as you can see here, let me search for progress have extra goes and here it list all the triggers that are available. Go for tea and we can see this s struggle. So the test trigger, which was not there previously, no, like regarded the plight from deaf to Cuba. And how did we deploying the use for start comedy for deployment off metadata from death to Cuba? So this is the whole process of deployment off metadata from one orbit to another or abusing full star comedy. But I do remember that once you do the validation, it is just validation and the changes are not committed. You got to actually execute the deployment plan on Lee. Then the changes will be committed to the destination arc. All right, so you can pretty much compare this with chain sets and how do we basically go through the process? Four Star Committee is another way off for deployment of metadata from one or two. Another organ says forced. So let's go back to the steps real quick. So we did the project and include all the relevant competence we selected that particular confident on. We chose the option, deployed the server on be connected to the destination, or the gave that particular credentials on finally use the validate option to validate and finally deploy the chick. Just so that's all it is.
7. Deployment of Metadata using Snapshot: So at the next deployment method that we're gonna talk about is how do we handle meta data ? How do we deploy metadata using snapshot? Snap shirt does definitely a very excellent tool that focuses on assisting the year system , admits for managing the ski mind their arcs. This tool helps us toe capture the snapshots for version ING and change management. And using the stool, we can easily view, compare, manage, log and report all the changes and deployments that just made to multiple salesforce arcs. And we can easily perform provide comparison and deployment to multiple cells for dogs. We can do audit and complaints management. We can view and identify all the relationships within the art. We can do documentation and reporting on that. Overall, we can manage all the customization that is made to the RV, including the FX cold or the custom objects on the page layout to work flows and profiles and never pick. So, as mentioned here, the stool is widely used to for the front other purposes on just more for deployment by In this lecture, we are just gonna concentrate. How do we deploy moderator using snapshot and how do we take a meditate a backup before be delayed deployment in the previous section in under a moderator export. We basically discussed that using snap shirt was one way off taking the meta data export that summarily the backup. Right. So now, like will the monster we'll see. Like how do we basically do that? How do we take a meditator export using snapshot? And then how do we deploy changes? How do we deploy the meditator using snapshot and to mention definitely, very important. The stool snap short is from the company during factory Onda. It comes with the license. You can goto up exchange and see that search for a snapshot and you know, you get that go for snapshot. And this is the one snapshot a change and release management golden change and release management. And if you give you all the details off that particular application, Yes. So as we can see here it is paid and we got to contact the company that is a dream factory for actually just to know about the licenses and for how many users And if, like, more number of users like will they give ah some a better price on the license or world leaders. I know everything that you can contact to in factory and ask that. And as mentioned here, it's an ultimate tool for our cleanup reporting, auditing compares and lifecycle management. And if you want to check more details to go over the details, stab when, like you'll have more details on the tool, as you can see here. And there is also some data sheets, some case scenarios on all these on I haven't Isa snap short. I use a guy where you can check in the reference materials eso that gives a complete picture off. How do we use a snapshot for various other purposes spent? You can go for reviews and check like basically, how people feel about snapshot on the providers as this comes with the license. It does not command a tree that every project uses a snapshot to distort the up to the project. Only up to the business totally up there. Barge in how much they can basically, you know, expand For all these tools were definitely a snapshot does a very good tool for deploying the meditator, and in case you get a chance to work in a project where the You snap shirt. Definitely. This lecture will be very, very helpful because now that you will know how do we export manager using stature? How do we deployment it by using snapshots? So, you know, snap shirt does no new tool for you, like, you know, you know, like, what a snapshot. And how do we do things with snapshot? Now let's log into the snacks on application by our dream factory. So this is how the screen looks like you got to give in your salesforce credentials the user name password. Basically, even the compass set up. You'll have access of a say, for example, like you are user licences. Ah, barred by your company for you to access snapshot, Then you can use the credentials that you use for accessing the production are accessing the sandbox. So if you want to access so the sandbox and, you know, give that particular credentials user name and password and then check the sandbox account this particular check box. But And if you're trying to connect the production just given the user name and password and leave this unchecked once you have successfully locked in, then you got to select the application that you go to work on. And in our case, like we want to launch a snapshot. So click on snapshot and go for launch. So once you click on launch, you get all these options taking the assets snapshot viewing a set snapshots, profile snapshot and object snapshot. The profile snap shirt is very much related. The profiles and objects is very much later. The objects on the field on now, like first we got to take assets snapshot. So far, no exporting for doing American export off all the confidence that we are gonna deploy I googly Kontic Asset snapshot my name to that sits snapshot Say, for example, meta data deployment and it'll be cheaper data that you are migrating Onda You can also say from which part basically this taken say, for example, now that we born on my great changes from death to Cuba, like you can say in such a way that so it is easily understandable on which particular data just done and from which are basically this snapshot was taken and then you have this option very new, can select all the components that you want to basically take a snapshot offered. The package is whether you want to take all the packages. Awesome. Selected packages are no packages, profiles, objects on the other information. Other information basically includes all your classes, components, pages, triggers layouts were close under all the other components that basically do not fall in this category. So I know what say, for example, like we want, um, my greater validation room. We want to deploy a validation rule from mom deaf to Cuba. Environment on Let that be. Oh, the test validation. Where? Just for an assumption. So the test validation rule is actually a validation room that this is deciding in the accounts object. So what I'm gonna do is I'm gonna select accounts and I'm gonna say OK, in the scenario as it is, one with the valuation rule that we are going to deploy from one or two other, I'm basically not selecting any off the others, but in others, and obviously you can select multiple other options assessment. So go click on OK, create effect. Know that as we can see the assets snapshot of successfully created and what all the competence that we have in that as it's natural. That is just this. So as we can see here, it is one of the accounts object that fear character, the asset snapshot. Okay, What next? So Well, now that we have taken a snapshot off the competent that we want to migrate, right, the snapshot of you can say just a copy of the competent. So no, like we go to connect to the target organization through which we want to deploy the changes on, then push these assets from the soul's organization to that target organization. So for that, we have an option. Go for studio. You have the option off push assets. So go for the option. Push assets on now like it tells you leg it is a two step process. So first it it is logging to their destination. Salesforce arc. Okay, So be to or are you one of my great say? For example, Cuba are staging or production, which others a destination are. So once you give the log in credentials off the destination or what happens is snapshot automatically. There is a step for taking the backup off all the components that you want to basically my great because as we already discussed. It is a definitely a good practice for us to take a back up off all the metadata before we do the changes. So he had let me log into the ark to the say the Cuba are go out of each other destination are. And here we go to give the backup. So let me say meta data backup on Let me give a date and let me say, say, for example, that Cuba art And then like the first you go to connect with the ah destination Ogg. Once you give the user name passport off the destination or on this being a sandbox, I have basically said it's a sandbox icon on the many times that ask you for a security token as well as we know. Whenever we try to connect to the for the stuff applications along with a passport, you also go to upend a security token along with that, So I have appended the password with the security Tilton, and then I'm gonna limit my snapshot. And here you can choose, which are all the confidence that you want to basically take a pack of profit. So, uh, ass like in the devil organization. The snapshot doesn't snatcher that we created is just for accounts. It is biting for showing only accounts, but he doesn't restrict us from taking a back up off the other confidence you can very much Tuesday, other competence assessment. So click on OK and then go for next. So now what has happened is automatically like in all the Medicaid, a backup off off those confidence which we are gonna basically update in Cuba. All those competence are, you know, taken a backup. So snap shirt is so such a wonderful tool that gives you a step for automatically taking the meta data backup. It is not a separate process. It is as part of the process of the deployment Verin. It tells you it gives you an option when you can take that metadata back up. And now that you have taken the magistrate a backup from the target organization. So the final step is for us toe pushed assets from death to Cuba. So here it is, objects. But it is not the whole objects that we're going to deploy. It is only the valuation rule that we're gonna deploy. So go for validation rules go for the selected validation room. So these are all the violation rules that have their accounts. So let me select the validation rule. That is a test validation bill, which we are going to deploy. So now I have selected the test validation rule off their accounts. Object. Go ahead. Click on. Next and step for is for us to review and push the assets from the source to the destination. Or so let me say push. Okay, it is in progress. Perfect. So the deployment is done. They've annoy us. And the reporter changes account Logic was changed on a violation rule was changed. Sylvia successfully done with her deployment. So this is the process of deploying meta data from one art toe. Another Argh using snapshot. Well, firstly, we got to take a set snapshot in the source organization, and then we got to push the assets from the source are to their destination, are so then you basically try to push this? It's from one arc to the target are basically snap shirt has got a step. Very and you can take a meditator back up off all the competence that we are basically gonna update in the destination arm. So it comes as a part of the deployment trusses. So that is something very good about the stoop. But as we already mentioned earlier, just they're doing the deployment or moderate. A backup is not the whole purpose. Off snapshots, Natural has card. Other different good features. Aspen. You can check the user guy that I've uploaded for for just knowing about the baby's other options that we have using. Snapshot. So this is how you do a meta data backup and you do matter data deployment doozy snapshot.
Archana Rajendran, Salesforce Consultant
