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?
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.
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.
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.
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?
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.?
![How to Use Custom Metadata in Salesforce Flow [FULL Example for 2024]](http://i.ytimg.com/vi/7NxLsq8SQNM/mqdefault.jpg)
Bro this was so simple. Thank you for showing me this technique.
No problem 👍
Excellent vedio like all of your other flow vedios. You are the best.
I appreciate that! So glad you're finding our videos helpful.
Thank you for sharing the tips
Any time! Let us know if there's any topic you're interested in learning more about
Excellent video!
Thank you very much! Let us know if there are any other topics you'd like us to cover 😊
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?
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.
@@Rotive Thanks. I did manage to do this with get records as well, after some research 🙂
you're the man!!
Haha. Thanks!
Thanks you!!!
You're welcome!
Good explanation
Thank you!
how can u do the same on a Scheduled-trigger flow?
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.
Hi, could you please tell how to get a record type dynamically as one of the superbadges had it as a requirement?
Getting the record type by name should do it.
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
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.
aaaaaaa THANK YOU
You're welcome! Glad it was helpful
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?
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.?
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
Hard to say. Try changing your decision criteria. Maybe you need "contains" instead of equals. Maybe there is a typo in there.
Rose Apothecary 😂