Salesforce Facts by Abhishek

Another use case using Screen flow action(Beta). We can have a screen flow to take email Id as input and find out what all existing contacts and leads are present with the same email. For this, we create a subflow to fetch the contacts and leads based on the input email passed. Also, to avoid unnecessary fetching of records, we can add validation to ensure the get records are performed only when the email is of valid email format. And in the main flow, we can refer the subflow in screen action and show the matching contacts or leads instantly. Attached are the screenshots.

Have you encountered the error: 'You are restricted from sending email' while sending email from the activity section on record detail page. This is because the 'Enforce Email Privacy Settings' option is enabled under Setup -> Email -> Deliverability. Reference:  https://help.salesforce.com/s/articleView?id=000381335&type=1

Sometimes in the emails sent from Salesforce, noreply@salesforce.com is added automatically. This can be controlled from an email deliverability setting. Setup -> Email -> Deliverability -> Email Security Compliance section -> Uncheck the 'Enable Sender ID compliance' checkbox. Reference:  https://help.salesforce.com/s/articleView?id=000383125&type=1

Suppose there is a scenario where we need to show the contact email and phone in screen flow datatable only if a particular custom permission is assigned to the user. Otherwise, it would be hidden to the user. We can implement the same using a bit of formula logic. Attached are the screenshots.

What happens when an email field is evaluated to an incorrect value from a trigger. The below error is encountered: data changed by trigger for field <fieldName>: invalid email address: (value has been hidden) In this example, we have a dummy email field on contact which is populated with an invalid value from trigger and is eventually encountered as an error. Note: The code snippet is only for quick demonstration purpose. Attached are the screenshots.