There are lots of videos on youtube but you have explained very well in simple manner and stuck to point. Thank You very much.
@salesforcein5minutes
Жыл бұрын
Thanks a lot 😄 will be adding more such videos on lwc as well
@swethamadadi2521
Ай бұрын
Very Useful and informative sessions .All the topics are explained to the point in a very simple manner .Thank you very much!
@salesforcein5minutes
Ай бұрын
@@swethamadadi2521 Thanks, glad you found my video useful ☺
@saimahesh6520
11 ай бұрын
very useful content with neat content and concept is very clear
@salesforcein5minutes
11 ай бұрын
Thanks a lot :)
@vindhyasravan8256
9 ай бұрын
Good session
@salesforcein5minutes
9 ай бұрын
Thanks a lot 😄
@kshitijgupta1220
4 ай бұрын
Pls do live sessions too good Thankyouu ❤
@salesforcein5minutes
4 ай бұрын
Sure 😄
@namanshetty2781
Ай бұрын
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?
@namanshetty2781
3 ай бұрын
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
@salesforcein5minutes
3 ай бұрын
You can use queueable i believe
@satyaprasad9371
6 ай бұрын
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
2 ай бұрын
Why are we using future method to make callout? Can't we make call-out directly in trigger?
@salesforcein5minutes
2 ай бұрын
@@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
@namanshetty2781
2 ай бұрын
@@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?
@namanshetty2781
2 ай бұрын
Please help me with understanding this
@salesforcein5minutes
2 ай бұрын
@@namanshetty2781 write a retry logic or else use platform. Events if possible
@namanshetty2781
2 ай бұрын
@@salesforcein5minutes okay thanks please make a video on this it would be helpful.
@satyaprasad9371
9 ай бұрын
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
@salesforcein5minutes
9 ай бұрын
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
@vaseefcool
Жыл бұрын
In this video session got expired. In realtime as well we need to login everytime to make a callout?
@salesforcein5minutes
Жыл бұрын
We just need to use named credentials to just do authentication again and then you will be able. To make callouts without any problem
@kiranreddy6155
4 ай бұрын
cab you also please make a video on Test a Callout with HttpCalloutMock. please
@salesforcein5minutes
4 ай бұрын
Sure man what exactlu are you looking for test class for integration?
@kiranreddy6155
4 ай бұрын
@@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
@salesforcein5minutes
4 ай бұрын
@@kiranreddy6155 okay sure will create a video around it 👍
Пікірлер: 29