Reveal Zip Code Field with airSlate SignNow

Publish zip code field

they're even this is Alma Lutheran from except easy stop and in this video tutorial we are going to learn how we can deploy our code from sandbox to production okay so we learn how we can make our code production ready so that we can deploy to it to any sandbox will production or any other non scratch work from a scratch alright so basically we are going to deploy our code or I should say metadata from a square chalk to non square chalk right and that non-scheduled can be anything I mean in care it can be a sandbox it can be a production right ok so for this tutorial I have just used my previous scratch-off that I created in some of the previous tutorial so in this sketch of I have installed I should it be call out framework so that it has some kind of metadata that I can deploy it to production right so what I'm going to do I am just going to convert all this metadata that is in source format or I should say the scratch OGG favorable format into metadata format right and then I'm going to deploy all this code into into a different environment that is a sandbox ok so the one thing that you should notice is that right now in this code I don't have any package dot XML file right even if I search for package dot XML I don't have any package to examine out here because this whole project is linked to a scratch shop which is this org and when we are dealing with Sketchup we don't necessarily necessarily need package dot XML okay so I don't have any package hood eczema but I will have a package of XML when I will convert it into metadata format so that it can be deployed to production right so we are going to convert we are going to convert our source format format to metadata format right ok so let's do that the command to convert your source code from source for metro metadata format is sfd X force source and then convert right so I mean you can you should execute this command actually from from inside a folder where you have your source for met right I mean you should execute this command from from inside a project I should say okay and it will automatically convert your all all of the files that are present in your project into metadata format there are some optional parameters that you can give for example if you are if you are actually learning this command then you can specify the source directory by - odd you can specify the output directory that you want to that you want to use by - D so let's say I don't want to use this particular directory in which I am in I want to use some other directory so I can give the directory path here right and I can give the output directory name here let's say output dir or something like that and if I want to actually specify a name also along with my along with my deployment I can deploy I can add a package name also by using - N and then the name of the package right I should like to the package name like like this right so I don't I am not specifying the soldier rectory over here because that's not required however I can specify an output directory in a package name as well but for now let's just delete all of this and I am just going to use SF DX for source convert because all of the other parameters are optional right so let's press ENTER in let's see if you are able to convert our source format into metadata format or not okay so you can see here it is showing me that my source for successfully converted to metadata API format and returned to the location and then the location is under my project directory its metadata package underscore something some random number right so if I see here in my source directory I have folder named as metadata and the school package might add a package underscore this whole thing right and in this folder I have all the components that are in my arc in the metadata format and I have also a package of XML that is automatically generated for me and if I check out this package to examine it consists of all the metadata that is there in my arc so that it can be deployed to any kind of sandbox or production environment okay so the one thing to notice is there - I mean I want to show you the difference between source format and metadata format have a look at the objects right because I installed I said typical out framework in my org so let me show you what object that I have I have actually a custom metadata here that is a part of HTTP called framework and this custom metadata has a name of HTTP caller configuration and inside that I have two records one is a test metadata which is used for test coverage and they say the sample sample call-out configuration that I deliver as a part of the framework right okay so I have a metadata record I mean a metadata and I have two records under this and if I check out the metadata I have a couple of fields inside the metadata which are the part of the framework like I can have a body endpoint method time out exit 2 etcetera right so this call out configuration metadata if I see here as a part of my original project that is there let's forget about this converted directory right I'm just to having a look at my project so if I see here the metadata I have the objects folder under which I have this metadata folder and under this I have a fields directory in which I have separate XML for each and every field like for body field I have a separate field example for endpoint field I have a separate XML right so inside each example I just have a custom field tag and some data about the field right ok and if I have a look at the validation rules also I have a separate example for validation rule as well right so this is the structure of the source format because let's see in my inside my custom metadata I have some of the fields and I have a validation rule as well so I have separate examples for each of the field and I have a different XML for a validation rule also right but to now let's have a look at the converted format which is not the source format but the metadata format right so I'm just going to close this folder and I'm going to just expand this folder which is which I which we convert to just now and this format is metadata format and if I check the objects directory inside this metadata format you will see that I just have a single dot object file so this is also in the XML format but this is this has an extension of dot object and if I check out this dot object file in detail I'll see that I have all the fields that part of my object inside the same dot object file as well as if I if I just search for validation rule here I can see here that my validation rule is also part of my object file so inside the metadata format if we check out custom objects we will see that we have all the fields and all the metadata related to an object so all the metadata that is related to an object is in the object file right in case of MDF in a format right however if I talk about source format then all the metadata that is related to an object okay so that's in a separate XML file side here I'm talking about source format which is supported by scratch oxide so scratch-off has a different project structure and metadata API has a different project structure right so here we converted our Sketchup project structure into metadata API project structure so the now the next thing that we need to do is to is to just to deploy it to a sandbox or production so that we can check out whether we are able to deploy this or not right so this is the folder inside which I have everything so I'm just going to change the folder name so I can actually specify the folder name when I'm running this command itself so I'm just going to delete it for a while and I'll run this convert command again and I'll specify a folder name this time so the output folder should be hyphen D and let's say folder let's say I'm giving it as deploy deployment folder right so it will automatically create a directory for me again after converting but this time my folder name will be deployment folder not a random folder name like because I have specified this in the command itself right okay so whenever you want to convert your source code you can just to use this command which is s FDX for suits convert and it will convert your source code right okay so let's move ahead now what I'm going to do I need to deploy this to a production or sandbox site but for the sake of demo I don't have any production of sandbox right now I am just going to create a new scratch OGG and use that stock as a sandbox and I'll use the same commands that you can use to deploy to any production environment or sandbox environment right I'm not going to push it like we do a push in the sky Rock but I'll deploy it specifically using the metadata API to like a scan like a sandbox or a prediction right so let me create a new sketch up very quickly and we'll resume on this so I have just written a command over here which says SF DX for source create so I'm just creating a new square chalk which and I'm giving that sky chalk name as sandbox to deploy and I have specified the number of days as one and I specified my JSON file for that for the creation of scratch all right and I'm also going to use a another develop and my develop me MS curious Fox dev hub and let's create a new scratch rock and we'll deploy it all the source code that is converted into metadata format to - scratch OGG using the metadata API so we'll consider that scratch over the sandbox or a production environment and we'll use the metadata IPE command so my scratch sagas created successfully now and I have just opened my scratch of using SF - force or open and I have given the username which is sandbox to deploy right so I can see here that my scratch sock is open successfully and I'll navigate to the deployment settings page so that I can see the deployment while it's happening ok so here's a deployment status I'll click on this when I was starting the I started apply mint right so for deployment I'm going to use this particular folder that we created and I'm going to use s FDX MDA pay commands right so I'll use SF DX force MD API and then deploy so this command actually needs some parameters if you have a zip file you can use - s command to specify the zip file but right now I don't have a zip file I have a directory over here so I'll be using - D which stands for directory and my directory name is deployment folder right and I also need to specify the username of my production of sandbox environment so here the username of my production of sandbox is sandbox to deploy so I'll just be writing here as sandbox to deploy and I'll use this particular command to deploy everything that we converted right now in to MD API format to our production environment right so let me just clear the screen once and we'll use this command to deploy which is SF DX or somebody appear deploy - D my deployment folder and I - you sandbox would apply so here you can see that my progress is I mean my deployment has been started so let's go to deployment status page and let's check out if our deployment has began or not right so it deployed really fast I think let me check out from here also so if you want to check out a deployment status you can also use this command which it is specifying over here which is s FD X force MD API deploy and then report right let's check it out if our deployment is done or not okay so we are not able to fetch reports so let's see if our deployment is done or not okay so our deployment is done and the deployment is done successfully that's why it is not able to fetch the reports because the deployment is already completed right so here we can see that our 22 components are deployed successful ok so let let me tell you one more thing before moving ahead but before that I just want to specify that if you want to have an output directly by by any user friendly name you can just specify - D here also and you can specify the name like I specified here deployment folder while converting the source code right and while deployment I use this deployment folder here I find a stands for the directory that I'm going to use to defer deployment and - you is my production or sandbox environment username light so here what we did we actually created a scratch org and we use that username - to deploy using the MD API commands but in a chill when I'm when you are going to deploy to a sandbox or to a production environment you have to actually authorize that or Krait you don't do you cannot actually use a username of fear of the sky chalk or something like that you actually need to login and authorize that are using s FDX ID so I'm just going to tell you how you can authorize any sandbox or production environment and give it a user friendly name like a sandbox will deploy our products will deploy something like that right so to authorize any or B you can use s FD X force auth and then web and then login come on right - are here stands for the instance URL so let's say you want to login into a sandbox so I'll give the instance URL s test dot salesforce.com right and if I want to login into a production I will give the instance your less login dot salesforce.com right so - R is used to specify the instance you were in and after that you can specify a user friendly name so user friendly name is nothing but the allows for an org so let's say I'm going to deploy everything into production environment or this whole folder that I just fetched into production environment this particular folder so I'm just going to give a user friendly name for this command so that Elias will be lets say the elias's production to deploy right so I'm just going to use this particular command to authorize my production environment and I have specified the login URL as log and OClO calm so it will automatically open this particular URL and I can login into that orc so let me just execute this command once so that I can show you how I'm authorizing this so as you can see here it has automatically open login dot salesforce.com for me and I can directly login into any kind of production environment using my username and password I'm just going to use this particular account for now to login into my production environment and I'm going to click on login so as you are successfully logged in into your production environment you will see a message in your vs code or any kind of command line tutorial which will say that successfully authorized this particular or with org ID and you may now close that alright so what I have done I have actually successfully authorized my or now and I can directly use that particular or name in this particular deploy command to deploy the a folder to my my production environment right so even if I need to open this or I can show you that so if I need to open this or I can just execute s FDX force force org and then open and I can use my user friendly opening that I said that I set here which was I think production to deploy yeah my arm is production to deploy and I can directly open this org using this you definitely name because I have authorized it once right so as you can see here that the or that I just authorised which is curious folks hy7 something it is automatically opened using SF - force open command right so here you got to know that how we can authorize a sandbox or a production environment and we can actually deploy everything by converting our source code into the metadata API format and then deploy our our whole source code into the production environment right okay so that's all for this tutorial everyone hope you liked it and let me know your feedback in the comments down below and I'll see you in the next video till then have a good day