Bro this was so simple. Thank you for showing me this technique.
@Rotive4 ай бұрын
No problem 👍
@mohammadrazzak53554 ай бұрын
Thank you for sharing the tips
@Rotive4 ай бұрын
Any time! Let us know if there's any topic you're interested in learning more about
@JeltjeRotterdam3 ай бұрын
Thank you for this video, it is very clear. I have another problem related to this: I want to change the recordtype of cases. We get a lot of case through Outlook. Depending on the sender or the subject, the type and recordtype can be set automatically. But I only manage to do this by using the recordtype Id. Is there a trick to use the name of the record instead of the ID here as well?
@Rotive3 ай бұрын
No trick here. If you're updating a Case's record type, you need to update the case field with the ID of the record type. It shows us the name of the record type when we see it in the UI, but that field is actually a lookup that contains the ID so that's what you need when updating it.
@JeltjeRotterdam3 ай бұрын
@@Rotive Thanks. I did manage to do this with get records as well, after some research 🙂
@tomaszwida2 ай бұрын
how can u do the same on a Scheduled-trigger flow?
@RotiveАй бұрын
Because a schedule triggered flow's trigger will match against record field values, I'd use the formula field trick and match based on record type api name.
@ShiwaniSehgal-m6h9 ай бұрын
Excellent vedio like all of your other flow vedios. You are the best.
@Rotive9 ай бұрын
I appreciate that! So glad you're finding our videos helpful.
@joymontgomery62865 ай бұрын
Thanks you!!!
@Rotive5 ай бұрын
You're welcome!
@rameeshar7076 ай бұрын
Hi, could you please tell how to get a record type dynamically as one of the superbadges had it as a requirement?
@Rotive3 ай бұрын
Getting the record type by name should do it.
@tonycadiz891 Жыл бұрын
Excellent video!
@Rotive Жыл бұрын
Thank you very much! Let us know if there are any other topics you'd like us to cover 😊
@madhumohan2952 Жыл бұрын
Cool explanation, but I didnt get why didn't we use get records to detect the record type id then we can for decision element right for 2nd method
@Rotive Жыл бұрын
Thanks for the comment! In this particular example we don't need to Get the RecordType record because we can already see it through the lookup field on the Global Variable record that triggered our flow. If this was a screen flow, you probably would have needed to include a Get.
@paolocavalli77 ай бұрын
you're the man!!
@Rotive6 ай бұрын
Haha. Thanks!
@sha35635 Жыл бұрын
Good explanation
@Rotive Жыл бұрын
Thank you!
@theokofi Жыл бұрын
Hi Brian. Could use your thoughts on the below. My org has several flows where we are fetching and using record type ids in several different flows for different objects. I’m contemplating creating a reusable flow where we first check the sObject and then go into a decision for different objects to retrieve the various api names of the record types for each object and then reuse that flow in other flows where we need to fetch the record type api names. I’m also considering creating a cmdt table to store the different record type api names for our most used objects and then get that cmdt object in our flows. We have a similar challenge with manually referencing queue Ids in flows. Thoughts?
@Rotive Жыл бұрын
Thanks for the comment. I’m not sure why the subflow would be necessary. Is there a lot of reusable logic? If record type A then set these 6 variables, etc.?
@PaoloCavalli-e1o7 ай бұрын
aaaaaaa THANK YOU
@Rotive6 ай бұрын
You're welcome! Glad it was helpful
@TimCollins-px9mi4 ай бұрын
Looks simple enough but I still can't get it to work correctly. Every time I go to debug... it goes down the No path
@Rotive4 ай бұрын
Hard to say. Try changing your decision criteria. Maybe you need "contains" instead of equals. Maybe there is a typo in there.