Thank You For this wonderful Flow Series .Thanks to the Entire Apex hours team.
@apexhours2 жыл бұрын
Glad you enjoy it!
@mangeshkadam67072 жыл бұрын
Thank You For this Amazing Flow Series. Kudos to the Entire Apex hours team. :)
@apexhours2 жыл бұрын
Our pleasure!
@brentschreibfeder5765 Жыл бұрын
Thank you for posting this; it was helpful. I would like to point out a correction to the Invocable Variable section. The invocable method takes a List because Salesforce has the option to bulkify calls to this method to improve performance, as it does with triggers - It may combine calls from up to 200 independent flow executions into that input List and expect you to handle it. By running get(0) on line 1, you will ignore any requests. This will cause this example to intermittently not work for most callers when under load. If your invocable method needs to accept a collection from a single flow, it should take a List, again to allow bulkification of up to 200 calls.
@shahirreturns Жыл бұрын
yes, I had the same concern!
@riteshmohapatra Жыл бұрын
Amit You are doing a splendid job.. Glad to know we both are Deloitte Alumnis.. Keep it Up
@apexhours Жыл бұрын
Thanks a ton
@riteshmohapatra Жыл бұрын
@@apexhours Can Invocable methods return value back to flow? i want to return a id and string back from the invocable method. Please help
@compton83013 жыл бұрын
Thank you. This is what I needed to complete a task at work! :)
@apexhours3 жыл бұрын
Glad it helped. Keep watching
@ashum8434 Жыл бұрын
Why we added the decision element? We have option in the first element to check when the flow is triggered...everytime record is updated or. Only at time when the particular mentioned field is updated
@vidyashree4052Ай бұрын
same thing i noticed. Decision was not needed
@snehalm42223 жыл бұрын
Thank u so much for video its very helpful ,but could you please tell what causing issue to save email as activity .
@apexhours3 жыл бұрын
Let me check
@AnshuRaj-s6j Жыл бұрын
how can we provide multiple record to variable. if i am getting multiple record in GET RECORD element. I want to send them all to apex class at a time???
@anandhikandasamy33302 жыл бұрын
Nice Explanation @Amit! I have a question. Is it possible to pass single record ID instead of list of Ids as Invocable method's parameter?
@apexhours2 жыл бұрын
Yes, you can
@anandhikandasamy33302 жыл бұрын
@@apexhours Thanks Amit! It would be helpful if you post a video regarding this
@nagachaitanyayepuri30162 жыл бұрын
Hi, Thanks a lot for the sessions, they are very helpful. I have a question, I have created a flow for auto-renewal, the flow takes Opp recordId and I need to pass it to LWC which then passes it to Apex method which has soql query to get list of Opportunity products of the Opportunity that entered the flow. Could you please advise how to acheive this? I need to display data table with Opportunity products along with Sales Price so that user can select them. Thanks in advance.
@ayushkhanna19962 жыл бұрын
Hi Naga, I have kind of similar requirement. Are you able to resolve this? This would be really helpful
@nagachaitanyayepuri3016 Жыл бұрын
@@ayushkhanna1996 Hi, sorry for the delayed response. Have you found the solution?
@madhukumaram6023 Жыл бұрын
Hi Sir, What about related Emails. The flow working fine I'm getting Emails when ever Case is created ( Origin = Email && contactId=!null ) but the Email size is still it's showing Zero. Any solution for this?
@serhataygun62452 жыл бұрын
Hi, I did the same everting but I have received this error. Flow didn't accept my Invocable apex. "Remove this element from the flow, or move it to a scheduled path. A record-triggered flow can’t execute actions that make external callouts in a path that runs immediately."
@serhataygun62452 жыл бұрын
Sorry my bad, I found the problem :D I had a callout=true in my apex class. After remove it worked.
@apexhours2 жыл бұрын
Glad you are able to fix it
@jainprajwal202 жыл бұрын
Can we call flow inside for loop in apex
@apexhours2 жыл бұрын
soon
@Kirankumarsundarapalli2 жыл бұрын
Hi apex hours team while the account is set to in active why it deleted only 2 opportunities but not 4 of them which are available in account related list of opportunities
@ameensams2 жыл бұрын
Because the condition was set to only delete "ClosedWon" opportunities.
@kyefang82789 ай бұрын
Your demo of deleting the opportunities actually used Delete Record action, instead of Apex. Kind of failed the purpose somewhat.