very great way of practical implementation , now i understood how to do callouts from future , pls post the link which you did for anonymous window callout and setting up of named credentails
Can I use Queueable instead of future to make call-out here? If so is there any difference or drawbacks. Also the call-out is inside a for loop , so i think this isn't best practice, so can you please guide me with the best practices here
I have a requirement that when a account inserts via data loader for each 200 records and if Phone number is not null, then the phone number field is validated from integration by making call-out and another checkbox field is updated based on call-out. So since each trigger has size of 200 records. But the maximum call-out allowed per transaction is 100. How to achieve this?
Hi "We get token from third party where we save it and if it expire what will be our logic ? how we achieve in our code?" i am getting these question mostly ,please help me how can i answer for this question
@@namanshetty2781 trigger exectues immediately but the callouts are made or we get the response of callout after some time hence we use it, also to make callout u need to use future with callout = true or database.allowcallouts
@@salesforcein5minutes Thanks for the clarification. But what if the response takes more than 60 seconds, let's say 180 seconds which is exceeding the CPU time of asynchronous Apex i.e 60 seconds also exceeds maximum time to get a callout response i.e. 120sec?
Is it required to edit named credentials every time if we want to callout, please clarify it for example i logout ang login again after some time is work fine or i need to edit and save named credentials again
You can just edit the named credentials and save it without any updation it will navigate you to the target website where you will be able to validate once more to send and receive the data
@@salesforcein5minutes Thanks for asking brother. It's about wring a test class for an apex callout and about implementing MockFactory for the test cases. It is so confusing what's happening over there. just for your reference check the trailhead unit on Apex REST callouts. Thanks
There are lots of videos on youtube but you have explained very well in simple manner and stuck to point. Thank You very much.
Thanks a lot 😄 will be adding more such videos on lwc as well
Very Useful and informative sessions .All the topics are explained to the point in a very simple manner .Thank you very much!
@@swethamadadi2521
Thanks, glad you found my video useful ☺
very useful content with neat content and concept is very clear
Thanks a lot :)
very great way of practical implementation , now i understood how to do callouts from future , pls post the link which you did for anonymous window callout and setting up of named credentails
Hi glad you liked the video, thanks for watchinh ill check in playlist for the things that you are refering to
Can I use Queueable instead of future to make call-out here? If so is there any difference or drawbacks. Also the call-out is inside a for loop , so i think this isn't best practice, so can you please guide me with the best practices here
You can use queueable i believe
Pls do live sessions too good Thankyouu ❤
Sure 😄
I have a requirement that when a account inserts via data loader for each 200 records and if Phone number is not null, then the phone number field is validated from integration by making call-out and another checkbox field is updated based on call-out. So since each trigger has size of 200 records. But the maximum call-out allowed per transaction is 100. How to achieve this?
Good session
Thanks a lot 😄
Hi "We get token from third party where we save it and if it expire what will be our logic ?
how we achieve in our code?" i am getting these question mostly ,please help me how can i answer for this question
In this video session got expired. In realtime as well we need to login everytime to make a callout?
We just need to use named credentials to just do authentication again and then you will be able. To make callouts without any problem
Why are we using future method to make callout? Can't we make call-out directly in trigger?
@@namanshetty2781 trigger exectues immediately but the callouts are made or we get the response of callout after some time hence we use it, also to make callout u need to use future with callout = true or database.allowcallouts
@@salesforcein5minutes Thanks for the clarification. But what if the response takes more than 60 seconds, let's say 180 seconds which is exceeding the CPU time of asynchronous Apex i.e 60 seconds also exceeds maximum time to get a callout response i.e. 120sec?
Please help me with understanding this
@@namanshetty2781 write a retry logic or else use platform. Events if possible
@@salesforcein5minutes okay thanks please make a video on this it would be helpful.
Is it required to edit named credentials every time if we want to callout, please clarify it for example i logout ang login again after some time is work fine or i need to edit and save named credentials again
You can just edit the named credentials and save it without any updation it will navigate you to the target website where you will be able to validate once more to send and receive the data
cab you also please make a video on Test a Callout with HttpCalloutMock. please
Sure man what exactlu are you looking for test class for integration?
@@salesforcein5minutes Thanks for asking brother. It's about wring a test class for an apex callout and about implementing MockFactory for the test cases. It is so confusing what's happening over there. just for your reference check the trailhead unit on Apex REST callouts. Thanks
@@kiranreddy6155 okay sure will create a video around it 👍