Hi! This is very helpful, thank you for the video! I have a question, If I want to create multiple records through flow, and the action that would trigger the flow would be click of a Button, what flow type should I use, screenflow?
Thanks @bhatsunayana! You can technically call Flows from buttons either via autolaunched or screen flow. But you probably want to prompt your users before they create those records, so I'd suggest a screen flow.
Hello Mam, You explained the concept extremely well, I have 10 opportunities whose stageName is not equal to closed Won/Lost and I am not using any date criteria. But after the flow kicks in I am seeing for under each opportunity 10 Tasks are being created instead of a single Task
Thank you Krishna. It's difficult to troubleshoot without seeing it, but I would start with the debug log. Run the debug and see 1) how many records you find in the GetRecords element, 2)how many Opportunity Ids iterate in the Loop and 3) if your final CreateRecords element is sending the correct number of Tasks to Salesforce . If it's sending multiple tasks with the same Opportunity Id, then it's something earlier on in your Flow - possibly an issue with your Assignment elements, though I can't imagine what that might be. Also, I assume you're using a Schedule-Triggered Flow like the one in the video. If you happen to be using a record-triggered Flow, then it's possible that separate update operations are causing your Flow to continue firing/creating Tasks. Hope some of that was helpful
Great video. I see what I’ve been doing wrong; thank you. When adding the single-record variable to the collection-record variable, you point out removing the period from the value selection, so the whole record is selection instead of a single field. Is that called dot notation? How do I describe that in order to do some more research? I don’t understand why the two step process is needed: collect a single record and then add the single to the collection. Seems like I should be able to add each individual value to the collection-record in a mulit-value assignment, instead of the doing that to the single-record first. Does that make sense? Again, thank you so much for taking the time to make the video. I found it very helpful.
Hi Greg - first, apologies for taking so long to respond. I'm just figuring out how to keep tabs on my video comments! I don't believe that step (of removing the period) is considered dot notation necessarily. But to your larger question about adding records to collections vs specific values - you should definitely be able to do the latter. But that depends on how you've set up the collection variable, and more specifically, the format that you select when creating. So for example - if you wanted to grab just the record Id value (text), you could choose that in your Assignment and then add it to a text collection variable. But if you have a record collection variable, like I do in the video, then it only supports full records. A bit late for an explanation, but hopefully that makes sense
CASE( MONTH({!$Flow.CurrentDate}), 1,DATE(YEAR({!$Flow.CurrentDate})-1,12,1), DATE(YEAR({!$Flow.CurrentDate}),MONTH({!$Flow.CurrentDate})-1,1) ) Case formula that looks at the month # value for the current/flow run date. If the month is 1 (January), then returns December 1 of the previous year Otherwise, returns the 1st of the previous calendar month
Hi Ritam - in the Flow, create a new resource > choose 'formula' (not variable). For the input, this is what I have: DAY({!$Flow.CurrentDate}) = 1 $Flow.CurrentDate is a system variable you can find within the Flow. DAY is a function that returns the day (number format) of that flow date. The total expression checks if the Flow date is equal to 1.
Thanks for watching, Trevor. You can see how the Task variable is configured in this other video, that further explains how record variables work. It starts at 1;37 > ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Dh-Lt04sahE.html
