NEVER do THIS in Salesforce Flows

Подписаться 3,6 тыс.

Просмотров 1,6 тыс.

50% 1

In this video we talk about one of the most important best practices when working with record types inside Salesforce Flows, and exactly how you can use a Salesforce Flow to query record types for any Salesforce object.
Always, always make sure you query for your record type IDs before using them inside specific data elements!
Join the Salesforce Saturday Email for weekly Salesforce and Career tips (Free):
www.nickfrates.com/blog
Get the 10 Ways to Boost Your Salesforce Career Guide (Free):
www.nickfrates.com/career-guide
Check out the Salesforce Flows Complete Guide:
www.nickfrates.com/2024-sales...
#salesforce #salesforceflow #salesforcetutorial

Опубликовано:

18 июн 2023

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 8

@CyrilOnForce Год назад

You're 100% right to make this video to remind everyone about this. Let's try to stay away from Hardcoding as much as possible 🥳

@aarondicker2979 7 месяцев назад

So clear, thank you

@salesforcenow Год назад

Feels like we all go through hardcoding IDs when first learning flows... ouch. Great walkthrough of how to level up flows!

@hasithasubhashana Год назад

Thanks you. Very nice explanation is such a short time.

@andrewstevenson5449 Год назад

Excellent point. But one thing I've struggled with unsuccessfully is including RecordType in the entry conditions for a flow. E.g. we have a number of record types on Accounts, each record type holding quite different data (not entirely our fault - most were installed by Salesforce's EDA pack, when we installed that), and to limit the overhead (particularly when uploading large amounts of data), we don't want every flow to run for every record type. But only RecordTypeID is available when setting entry conditions. Any thoughts? Moving the criteria from the entry conditions to a get record as in your video and then a decision element won't work, as the flow will still trigger for all record types, which is what we need to avoid.

@nickfrates Год назад

Awesome question. I think in those specific scenarios you could try using "Formula Evaluates to True" for your entry conditions and then use the {!$Record} functionality to specify a condition like: {!$Record.RecordType.Name} "Standard" (in addition to any other requirements). This way the ID isn't hard coded and you can still filter out the record types you don't want by using the name.

@andrewstevenson5449 Год назад

@@nickfrates Excellent! That's worked.

@RK-gu2fq Год назад

Even though Flows are not "code" you should still build them like a developer. Not hard-coding Ids is a Salesforce best practice. Users would be well-served reviewing Salesforce's best practices for Apex development, and leverage those for their Flows as well.