 going live. Hello everyone. I am Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. I have Abhishek with me. Welcome Abhishek on the platform. So I am hearing very nice comments about you on deployment sessions as well as on Omni Studio and people are asking doubts as well. So I think you are doing great job and I am already impressed with you, your work and I think now community also getting impressed with whatever you are doing for them and I'm sure this Omni Studio bootcamp will change life of lots of consultants. They will like they will be able to upgrade their CV and they will be able to apply for jobs for for the companies whoever is working for industry clouds. So I appreciate your dedication towards work and today we are having day two of the Salesforce Omni Studio bootcamp. So guys as I promised you yesterday like from day two onwards all the sessions will be having some practical implementation. So today we'll be doing some practical implementation around data raptor. So first component that we are picking is data raptor because it will give you the baseline so that you you will be able to use it in IP or like your flex cards or Omni scripts right. So first we'll be covering data raptor then IP then either flex card or Omni script as per the requirement right. So first I want like Abhishek to introduce himself so if someone joined this bootcamp for the first time so I want they should know who Abhishek is and what he is doing. So over to you Abhishek. Yeah thank you Sanjay. So hi everyone I hope you all are doing well. So myself Abhishek and I'm working as a Salesforce and Velocity developer in Salesforce community and I have around five plus years of experience and I have I have done 200 badges on my trailer and I have I am holding some certifications which are from Salesforce like the first one is like Omni Studio developer then I have CPP Specialist Service Cloud PD1 and Admin and I have done multiple projects on Velocity or Omni Studio where majorly I have I have worked upon like Insurance Cloud and Telecommunication and Industries Cloud. Yeah that's all. So moving on to the next slide so if you want to become part of Sanjay Gupta Tech School community and want to interact with freshers and professionals so you can scan this QR code and you can become part of that group. Lots of folks are connected there and they are interacting on daily basis and next like if you want to receive timely notifications so you can follow Sanjay Gupta Tech School on YouTube, LinkedIn, Instagram and Telegram and all the links are available in the videos description as well and next slide says please provide some reviews and feedback so that it will keep us motivated and like your reviews are like 100% impression of our work. So if we receive positive reviews it means we are doing good work and if we are getting some negative reviews so it means we need to improve but to be honest and YouTube is the public platform everybody can see all the comments. So as of now like 99% I received positive reviews because our intention is pure to help the community. So keep on giving us reviews or feedback so that it will keep us motivated. Okay with this note like over to you Abhishek so today he will be doing some demonstrations in the org so only studio org how you can access that we discussed yesterday and org access link is available in the session tracker as well. So create that org today itself so that now onwards whatever session you watch you can do practice as well. So in every session you will be having like we are implementing scenarios and we are discussing that and if you see any challenge you can ask out live in the session and later on in the telegram group. Okay so let's start today's session Abhishek. Yeah so as a studio components we're going to discuss about the first component will be the data actor so as we have already discussed and we have already seen what actually data actor does is so whenever you want to fetch some data from your database right or you want to manipulate some data into your database then as a Salesforce components what we use general generally is SOQL queries and DML operations like insert command update command absurd command right so if you want to do some some sort of similar thing with the help of omni studio tool then here we go we have the data actor so we're gonna discuss a brief about data actor again today and then we will be seeing the practical implementation of one of the data actor type. So data actor you use for mapping tool that enables you to read transform or write Salesforce data. Read means you can fetch it transform means if you want to you know perform some logic or let's say you want to transform some data and what write means you can perform DML operations then data actor supplies data to omni script and omni studio flex card from Salesforce so as we already discussed omni scripts and flex card are used for creating the UI experience digital experience right so if you are not fetching some data or if you're not saving some data to the database that is that is gathered from the UI then there is no sense of creating the UI so data actors is the backend tool which will fetch the data or save the data and it can supply the supply the data to the omni scripts and flex cards. They typically do via the omni studio integration procedures so whenever we are working in Salesforce right in Salesforce if we are writing any SOQL queries we generally write in the apex classes right so when if you want to if you want to show some data on to the LWC right so you will be calling apex class or you will be using the lightning lightning data services right in the same way when you want to show some data into the omni scripts or flex card you will you will be you can use the data rector directly from the omni script but if you want to perform some business logic around that let's say if you want to if you want to get some let's say data from 10 objects right so we generally use integration procedure in between so from your omni script we will be calling the integration procedure and from the integration procedure we will be calling the data rector and it will be the other way around data rector will provide the data to the IP and the IP will provide the data to the omni script so this is how these components can be integrated. If we see an example of data rector so like as we already discussed we can get the data and omni scripts omni script call a data rector extract via an integration procedure or it can be it can be called directly as well and manipulate data the omni script captures changed and new data based on the user input so let's say you are getting some information some account information right and you want to save it to the database then we can again use a data rector or let's say there can be one more example can be if you are fetching some data and user is making some sort of changes on that data now you want to save that change data to your database then again we will be using the data rector and save data is a simple example of insert insert dml operation if you want to save some new data to your database then again we will be using the data rector yeah so I think to summarize so all these things are available in flow builder as well get data update data create data it is like get record update record create record right and same things we can do in apix as well through soql or dml so I think today you will be demonstrating some things around this I think we'll be doing get data today right yeah so we will be seeing one one data rector type example which is data rector turbo extract I mean first we will be seeing what what type of data rector types we have then we will be seeing the practical implementation of one of the data rector type right so guys stay tuned and watch this session till end don't like stop watching in between because if you are following all the videos then only you will be able to understand the whole concept of omni studio right and as I say consistency is must right so be consistent so we are doing two sessions every week right and rest of the days like you can do practice and we'll be giving you some exercises as well so week by week like you will be able to learn omni studio and the only thing that you need to do is practice and yourself practice doesn't mean like you're watching what we are implementing you need to do hands-on you need to do your hands dirty so watch what we are implementing and implement at your own so that will help you out okay so yeah please continue yeah let's move on to the next slide so this is this is a similar slide that we have seen yesterday so let's let's know about data rector types in brief so typically we have four types of data rector is available in Omni studio so one is data rector turbo extract and second is data rector extract so these both type of data rector extract are used to get or read the data from your database right but the major difference between them is if you want to fetch the data from a single object or a direct parent to it so for example let's say if you want to fetch the contact contact data right and if you want to get the account related account information as well but that account will be your direct direct contact it should not be in the hierarchy like there should not be any third object so then in that case we will be using data rector turbo extract and when I want to fetch the data who are in relationship if they have multiple relationships if they have no relationship between them then also we can fetch the data from data rector extract for multiple objects so why Omni studio have created these two data rectors in a way because data rector turbo extract is kind of a faster data reading process from your database so if you want to fetch your data from if you want to fetch your data from single object then you must use a data rector turbo extract because it will be a bit faster when we are comparing with the data rector extract so these two things are a major difference between them yeah I think we can proceed with these two data rector load and transform like we'll be covering in upcoming sessions so we can skip that as of now okay this is the definition that we have seen it retrieves and filters data from a single object with support for fields from related objects and those related objects should be the direct objects direct relation should be there you can filter the data and select the fields to return doesn't support formulas complex output mappings so whenever you are fetching some data from a database you can perform some actions in the formula tab that we will be seeing in picture in action when we'll be seeing when we'll be doing the implementation and advantages of this it's simpler from configuration you don't need to write any sort of SQL queries you will be just doing all the point-and-click things drag-and-drop things all that and one example can be retrieve opportunities for an account right yeah so opportunities your child object and account is your direct parent object so maybe this this can be our first demonstration right yeah it can be yeah guys so just hold on and like now abhishek will be jumping to the org and he will be doing the first demonstration so right now just focus on how he's doing and once this session ends and like we you you will be if you are working professional so you can do practice on weekend if you are like fresher have enough time so you can do practice on weekdays as well but understand the concept ask questions and then try to implement whatever we are trying to implement okay go ahead so first of all I just want to give you a look around how open studio looks like so there will be there will be a an application in your whenever you will be getting the developer addition or for only studio then you will be getting this only studio which is a console app okay and when you click on the on this only studio then there will be there will be a set of tabs that will be available in this in this application so like these four four tools are the major components are of only studio so first is omniscript then we have flex card then we have data raptors and we have integration procedures right and by default they have added the account contacts and case objects into the only studio application and if you want to add some more some more objects into your only studio application you can do that by click on the editor yeah so so I think I think this is an application right so in this application so if this application is available only studio application is available then only you will be able to do you can you will be able to implement these things like data raptor IP and other things yeah so let's move on to the data raptors that so how velocity slash only studio has designed these components so if I talk about the only studio data raptor this is a Salesforce object right and whenever you are creating a new data raptor right there will be a there will be a record created for this only studio data raptor Salesforce object correct so they have designed in a way that you will not be writing any sort of code so these all are records these all are records so let's jump jump on to the on to the implementation we will just click on the new button similar to like we are creating the account record or contact records and there will be a UI where you will be the giving the data raptor name right so generally when we are working on the working on the projects in consulting companies there are some naming conventions that we follow so let's say if you are creating a data raptor transform code if you are creating a data raptor turbo extract so what we use we generally write it's right is d r t e data raptor turbo extract right and then we use underscore and after that whatever whatever functionality we're building sort of let's say I'm building a functionality where I want to fetch the opportunities with accounts correct now we have the interface type where you will be selecting the data raptor type so as we can see we have four types data raptor expect data raptor turbo extract data raptor load and transform so in our implementation we are creating the data raptor turbo extract and then we have two two another fields which are called as input type and output type so let's say if you want to if you want to if you want your output in the GCN format then we will then we will be selecting the GCN as a output if you want to if you want to get the output in a custom format so this custom option we will be seeing later on but right now for our kickoff of the implementation we will be selecting input type and output type as a GCN only so our input will be in the GCN format only and our output into the GCN format on and we can skip these two things and we can just write the description simple descriptions like get opportunity yeah and I think descriptions are also important if we are working on projects so then if if some developer is developing any data raptor so we can say like why we are creating this and other developers can have an understanding or like if you are working for any requirement so you can mention task number as well for which task actually you created so these are basically part of best practice that you can do let's click on save and there will be a UI created by omni studio data raptor so all the things you can see now abhishek one thing you need to zoom in okay yeah a little bit less like zoom out one time yeah now it is okay okay yeah yeah so like whatever information you have given at the time of creation of the data raptor like this is your name then interface type the turbo extract input output type and description right now whenever whenever you are writing a SQL query right so if I give you example an example what we typically write is select id from account select id from opportunity right so id is the value those are the fields that you want those are the fields that you want to fetch it from your database and whatever you are writing after the from that is your table table name or the object name like opportunity contact um accounts and all so these all sort of things you will be seeing over here as well so in in your first option select an option you will be selecting your object name so let's say I want to fetch the opportunity simply I'm just gonna search for the opportunity and just click on it and it will automatically will see that I want to this data raptor will fetch the data from a parse right and so in apex when we are working with apex when we are writing the isoquel queries whatever data is getting returned from your isoquel queries we are we typically save our data into some map or list right so here also we have to define a variable name so I'm going to call it as let's say OPP data and if you want to give some sort of uh some sort of uh where clause when we are writing the isoquel queries we can see use the isoquel uh where clause as well so in the filter what you can what we can do is for the for the example uh for the example I can select the account ID and here you you will be having all the operators right like equals not equals greater less lesser than greater than and we have this like not like includes and all these operators so I can say that account ID should not be equals to uh blank so what what uh what it what it's gonna return is give me all the opportunities where account ID is not blank yeah so all those opportunities which are related to at least uh any account record correct right and now here comes the part where you where you will be selecting what fields you want to get right so let's say I want to get account ID uh amount close it and uh let's get the stage as well staging so these four fields I just want to get it from the opportunity so if you think uh if you think of this UI it can be it can be your isoquel isoql query will look like select account ID amount close date staging from opportunity where account ID is not equals to null exactly I hope I'm able to make sense Sanjay yes and uh one more thing that opp data can be a list of opportunity right so suppose you have created a variable list of a part list of opportunity type name is opp data so whatever we are doing here the outcome of this thing will be stored in opp data uh that is written inside extract output path right yeah so this is this is your object configuration so whenever you will be creating a data wrapper in the first step in the first step which is called as extract you will be giving the asoql query configuration or the object configuration right and now we will go to the options part so let's say you are calling this data wrapper from an IP right so there are there are three three options that we that we have in the data rector so basically Salesforce platform cache type if you want to store the data this data into your cache then you can select the session cache and the or cache and for for how many minutes you want to store this data into the cache that also you can define over here I mean folks who has worked upon the lwcs or aura components they can get this functionality very well what is cache types and I think it is optional right yeah it is optional you don't need to define it okay and there is one one more checkbox which is called as checked field level security so let's say right now I am I have logged in as a system administrator now I am giving the access of this data to some profile who who have access to only these two fields account ID and amount but not to the close attend stage stage name so if I if I have checked this checkbox then that profile will not be able to get the value of prompt for those two fields right right so that also this feature is also available into the data now if I move on to the next step which is called as preview and I will tell you each and everything over here first we will just click the execute so guys right now Abhishek just clicked on execute right so through execute that query will execute and result will be there yeah yeah so see I mean I have just made one change not equals to null so we have to give the blank single single codes yeah so single codes you need to open and close without any space in between correct so now if I again go to preview now as you can see we have all the possibilities data into the json format yeah closely yeah this is important to understand the outcome is in json format so if you are not familiar with json format so you need to understand that before you understand this and yeah all those fields are also available yeah if and Sanjay if you want me to explain what is json and what other types we have in json we can also do that yeah I think we can because I think there are folks who are fresher and yeah if they have not worked much in Salesforce ecosystem so I think it would be good if we can explain a little bit about that sure sure so you need to just a little bit zoom in yeah yep yeah now it's fine yeah okay so first of all when we are working in a technology or any software there are so many there are so many object types that those technology supports I mean some of the popular object types can be can be named as json can be named as xml format or it can be it can be named as I mean these are the two most popular object types or the data storage types that are popular in technology or software so java json json format the full form of json is javascript object notation and it supports so whenever whenever you are writing creating a json format data right so you have to start everything with the curly braces if I close it if I close this one out once so as you can see everything we have is in the into the curly braces now json also supports a type of a type of data types so as you can see first of all we have a array so whenever whenever whenever you are creating any sort of any sort of variable into the json there are always two type there were there will be always two things first is key and second is value right so as we can see this array is the key name and if we see the value of it is the value of it it's it's in it's into the list which is into the square brackets and those values are comma separated one comma two comma three the next data type that json supports is boolean so again this boolean is the key name and the true or false can be the value it also supports null null data types it also support number data types again this is the key and this is the value and json supports objects of objects as well so if we see this is a complete object right now now if I want to create an object into this object that also that is also supported right so if you see this one this is your key key key name which is object and into into this we have started we have started the curly braces and we have closed the curly braces which is called as object and in that object we have multiple values which like the example can be a is the key value b is the a is the key key name b is the value c is the key name b is the value and json also supports string type of string type of data types as well so this is the brief introduction which can be given for the json formats right yep so I think it would help and at right inside its notations summary is also available right like how output will look like so at left inside how you will write the json and at right inside like how exactly in javascript you can see that result so in javascript like if you if you use inspect like on your UI on your web page if you right click and select inspect then there you will find this kind of output which is available at right inside correct yeah and those who are having javascript knowledge so I think they they might know this thing very well because in javascript we use this frequently yeah so like whatever data that we have received from this data if I copy this json and if I paste it over here so what we have it first of all every json format starts with the curly braces and in that opp data is your key opp data is your key value key name and if I collapse this so it's a json format where we have a list of objects if I open this again then this opp data is the it is holding a list of objects and as you can see we have a object we are starting the curly braces closing the curly braces and then we have string values we have number value 75000 right so this is how our json is json will look like so I'm going to close this one and we're going to come back over here so now we will see what this preview page is showing to us so first of all it has some input parameters that that will that will so I'm going to explain you what this input parameters is used for so let's say I have I have given an input parameter and I'm going to say page name where and this correct so whatever whatever value if I click again as edit editor json there is a input json that I'm providing to this data rector right so you can think of it like from your lwc you are getting some value from your from the user and you are passing that value to your apex class and whatever variable you are I mean whatever value you are holding into that variable you are using that variable as your wear clause so to this data rector I'm passing a variable called stage name where and the value of that variable is closed one and now I can use this variable into my extract step so now I'm going to change my wear clause so let's say stage name is equals to stage name where so whatever input I have provided into this stage name where it's going to pass it over here and we're going to get the opportunities which are closed one and now if I click so right now if I go I have an opportunity called as a stage name called as proposal price code and if I click execute now I will not get that way I will not get that opportunity yeah it is it is understood so you mean to say like you are passing external input into your data rector and basis on that external input your data rector is querying the data yeah so I mean yeah whenever whenever we are working in any of the projects right so we never hard code any sort of values into the wear clause or into the filter criteria we always get some input to the data rector from either omniscript or from flex card and then we use some variable name and then variable name is getting we will be passing it to the filter criteria right so maybe one more thing we can add here like if we are using this data rector in any ip and from that ip if we are passing something as an input so that input will be stored in this variable and then exactly basis on that data will be fetched yeah great I mean whenever whenever we will be seeing these all components integrated like when we will be calling the data rector from your integration procedure then we will pass the value of this stage name way where from your ip so whenever you are passing some data into this input parameters this is your testing environment or this is your testing area where you can pass any so let's say in future this data rector stopped working now if you want to test this test this data rector what do you what you will be doing you will just you will just go into the preview and into the input parameters you will change the value whether I'm getting any sort of value from the from my test value right so so guys right now we are understanding all the components individually right when we'll be connecting data rector with ip so in that case you will understand more the use of this input parameter correct okay and there is one more thing that I can show you so for example I'm gonna do I'm gonna change this one again to let's say this thing where stage name is not equals to blank and if I click execute right so as you can see even though I am passing some value into the stage name where there is no impact I'm gonna get the proposal price code right because I have removed the stage name stage name where from the filter criteria I have hard coded the blank well correct and if I go to a yeah one thing I wanted to say I think you can complete first because I was about to go to right inside where I can see apex like SOQL so yeah that's the part I was about to explain so you can go ahead yeah so you can continue that because that needs to be finished first yeah so I mean so my point was whether you are passing any any value into your input parameters and if you are not using into your filter criteria or anywhere there is no impact of it right I mean data rector will not throw any any sort of error you can you can pass any variable which is not into used into your data up there that is totally fine okay so I think if we have passed any value into input parameters so it depends on us like we are using or not so it is kind of option correct but I think we must use yeah we must use I mean that's the best practice right so if I will go to the right right hand side now and we have two sins if your data is getting failed then there will be some sort of error in into this block and if you if there is no error then whatever configurations you have did you have configured in your extracts extract tab similar to this extract step there will be a SOQL query which will be created by data rector so as you can see we can see our query that we discussed in the beginning of this implementation select id account id stage name amount close date from opportunity where stage name is not equals to blank so yeah guys you can see we used low code platform we didn't write any query but still you can see in debug log whatever configuration we did basis on that this SOQL is available here yeah and for example if I'm if I'll replace this one right your SOQL query into the debug log will get changed automatically see this where stage name is enclosed in is your operator then closed one yeah I think this is awesome tool yeah I mean you're not writing any any sort of or any single piece of line and you are able to get your data awesome so I think this is end of first example right yeah there is only one one more thing missing so as we saw into the into the slides from data rector turbo extract we can get the fields from your object and your direct parent right so if you want to let me guess you are you will be trying to access account information right correct so you will be having one more option into your extract step which where you will be seeing all your direct parents of opportunity like account campaign contact contract and all these things right so right now I want to fetch it from the opportunity sorry the account object only so I'm going to select this one and as soon as you will be selecting this this related object you will be able to see all your related parent fields as well so I think it is auto refreshed yeah it is auto refreshed you we didn't do anything so for example if I want to fetch the account name right I can just click over here and pull it to the right side so if I go to preview it is reminding me child to parent exactly right so and you will be able to see that child to parent as a girl over into this debug log as well if I click execute now if you go here and you can see this account dot name field has been automatically inserted into your as a good right so that's the beauty of only studio data actors and I think you need to focus on JSON as well it is also get updated yep into your JSON you will be you will be getting all your direct fields and there will be a there will be a child a child object will get created into a JSON where you will be having your all parent fields right great yeah I think that's that's it for data after turbo extract but I think in slides we have few more examples if we see so this is the one which you demonstrated and I think if we can pick one more anyone and rest of the examples will be for practice so this weekend I will be creating one exercise sheet as well so what I will do like few examples we will be covering in the session and few examples we'll pick we'll put in that exercise sheet so that folks can practice and if they will be facing any issues so we'll ask if there is any issue so we can demonstrate that in our session yeah so okay let's go with one more example for fetching your account information I think we can pick different one where multiple criterias are there okay okay so what we can do yeah let's pick the second one where the active is equals to yes and annual revenue is greater than equals to one lakh right I would prefer fourth one because it is having input parameters as well so we don't need to hard code okay initial initial first second and third we need to hard code so you already explained both the ways like if you want to hard code you can but as best practice says we need to provide input through input parameters so I think fourth one will be better and maybe fourth one again if you can demo through both the ways hard coding and without so sure yep definitely so just give me a second and I think it is straightforward for account there is no related object involved correct okay so we will go back to our opening studio data reactors we will click again on new button we will call it as drte and we can call it as like account records while you you are creating this I just want to highlight one more thing guys we didn't hit save button anytime right so whatever you are implementing it is saved automatically and this is the thing like I like the most because I remember whenever we create flows and by mistake like if you refresh the page so everything automatically cleared from the canvas so in flows like we need to hit save button again and again if you are updating something and by any chance if you refresh your page so everything will be removed so in this tool whenever you are doing something you are changing something so it is auto saved right so that is also beneficial for us yep we will click the save button and we're going to follow the same steps in the in this option we're going to select the account object let's call it as a cc data and into the filter if I go back to the slide right we have filter as like where active is equals to us and rating is equals to hot right so let's say we have this active field where we'll be saying so whenever you are passing any sort of stream value you have to use single input it comma right so here comes yeah and guys this is this is using hard coded values so first we'll be showing you hard coded values and then we'll show you how we can replace it with input parameter yeah so here comes the new thing if you want to have multiple conditions in your where clause you can just simply click on over here and you can use any any operator like and or or limits offset order by it so whatever whatever keywords can be used into your SOQL queries we can use it into your data raptors as well so for now let's I'm going to select as and and I'm going to give the rating rating is equals to so in our example rating was hot and so so this this is the filter criteria that we have given now we're going to select the value field so let's say active and we're going to select the name and we can also select the rating yeah these three things we're gonna select it and nothing we have to do into into the options we'll go to preview and simply click the execute so as you can see there is there is no no record that I have with the rating hot and active is equals to us maybe you need to apply or yeah so I'll go to the account records and let's say I'm going to open this account record and details and for the active one I'm going to say as yes and there is the rating above at top at top okay let's click it as same so I have modified the data I'll go back to the data vector and I'm gonna hit the execute button again and here you go we have one record yeah only one record because that is modified right away and at right inside also we can see query results found one yeah now what we're gonna do is we're gonna create two variables which will be like first is rating where and second is active where okay and in the in the rating where I'm gonna pass it at this hot and in the active where I'm gonna pass it as active yes one question do we need to use single quotes here or not so in in your input parameters again there are two things this is nothing but it's a json right so they have they have given the ui tool as well so you you can just click on it and put the variable name and the value value and if you want to add your json manually you can just simply click on an editor json and you can write your own json got this is also no name and this is your yeah no single course nothing that yeah we can directly put the key and value pair and it will be converted into json automatically right so I'm gonna go here and pass this as a variable and for the active one I'm gonna pass this as a variable yeah and this is best practice yeah this is your best practice and now if I go to preview and click the execute same value same value I'm gonna get right so I mean like if I go for one more account right let's go to this test abhi and what I'm gonna do is I'm gonna set the rating as again hot and my active will be the no right now if I go back to my data adapter I'm gonna so now I'm gonna click on this one and I'm gonna set as set this as no so see we have so many records with it three records so the you the usage of using this input parameters so let's say if you are if you are calling this data adapter from two ip's from one ip you are getting the getting all the accounts where you want to get the active accounts from the second ip you want to get the accounts which are which are not active so you can use the simple data single data adapter into the both the ip's and you case you can pass the input parameters from your ip so that you don't have to create a new data adapter for getting the accounts which is active or not so that's the benefit of using the input parameters I think this is it for today yep I think yes okay so guys if you have any question you can ask in the chat I I can see the last questions today I think you are able to understand what Abhishek demonstrated and I will make sure like by next week you will have a exercise sheet so two examples we demonstrated today but I will try to put lots of examples on data adapter so that along with what we demonstrated that also you need to implement and other than that we'll be giving you lot more examples as well so so that you can practice them else also right so thank you so much and Abhishek we are receiving great feedback so I just want to ask you like just read the one slaysha posted like simply great Sanjay and Abhishek it's a great channel thank you for your effort so I want to dedicate this feedback to you because it came because of your simple explanation right so yeah thank you thank you so much Risha yeah one example one question from Sanketh while creation of the DR required permission option is there can you please explain the option one so maybe we can explain it in our next session because yeah yeah so when we'll be creating one more DR maybe for export so we'll try to explain it yep and Sudhir yes OPP data is just a variable to store the result it is similar to uh list name which we create in epics okay yeah yeah manjunath I will be preparing an exercise sheet where use cases will be there and I hope you enjoyed today's session so we'll be having lots of sessions for data raptor so today just we just completed turbo extract we have extract we have load transform so everything we'll be covering in detail okay so Arun is asking please show me the questions once uh I think we need to share the screen again yeah okay let me do it slide show no no no yeah yeah so if if you want to take a screenshot of this you can so that you can practice and I think these are recorded in the session so anytime you can have it so Abhishek there is one more question assume we have IP where it's retrieving active yes and other IP retrieving no do we need to create one more DR for no if we have one DR with yes so that's the that's the functionality that I have explained in the into the in the last bit so we can use the input parameters in your data raptor and that input parameter can be passed from your IP so one IP can pass yes and one IP can pass no so data raptor will be the one but that data raptor can be used into your multiple IPs right okay so I think this is it for today thank you guys for joining the session and thanks to those who are watching the recording right keep following all the videos all the streams and do practice so that you can have one more skill set added in your CV and you can apply to those companies where industry clouds are used and thanks to Abhishek once again for like giving your time to the community and sharing your knowledge thank you thank you guys see you next week with some more content