Video

Diagramming Salesforce Solutions – Matthew Morris – Video

Matthew Morris, Salesforce Innovation Director at Capgemini, presented about “Diagramming Salesforce Solutions” for the Jacksonville Florida Architects Trailblazer User Group on 10/13/2022.

I would like to thank Matthew Morris for this wonderful presentation. Please find the YouTube video and the presentation file in pdf format below.

This topic was presented originally by Matthew at London Calling 2022, the community-led event in the UK; therefore, I would like to give them a well-deserved shout-out as well.

Youtube video:

Presentation slides:

Enjoy

Standard
Flow Tips Newsletter, Uncategorized

Winter 23 Flow Formula Editor – Salesforce Flow Tips Newsletter

Hello folks,

Let’s get started with the Winter 23 Flow enhancements, shall we? Who doesn’t like to save time and effort?

One of the biggest improvements is the formula resource editor with the instant syntax check button.

This functionality first came for the start element and the collection filter in the previous releases. Now we get the same editor across the board in the flow builder.

No more writing a formula, saving the flow, and crossing your fingers hoping it won’t yield an error message.

You can check for errors as you build your formula on the same screen using the Syntax Check button.

One disclaimer is that I saw some inconsistent behavior in my preview Dev Org:

Some of the collection filter formulas I built that I thought should pass, did not pass the syntax check. But we still have time until the release. I am sure it will be ready by then.

Now content announcements:

  • I am super excited that my session proposal has been accepted for Florida Dreamin’ 2022. I will be presenting there for the third year in a row. My session is titled: “Flow Design & Mapping: From Idea to the Flow Canvas“. It will be super interesting, I promise you. Come and see it: Register for the event here.
  • Last week, I presented the new Winter 23 Flow functionality at a virtual Jacksonville Salesforce Saturday event. I tried out the new enhancements live and recorded the event. Watch Winter 23 Flow Features – Salesforce Saturday here.

Enjoy.

P.S. Originally published on 08/30/2022.

Read the previous issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.

Standard
Flow Tips Newsletter

Start Element Formulas – Salesforce Flow Tips Newsletter

Hello folks,

How cool are the brand new start element formulas?

One of the best use cases for it is the Record Type criteria. You can now check for the RecordType.DeveloperName or the RecordType.Name in your start element. This was not possible before. You either had to hardcode the RecordType.Id or defer the criteria to a decision element, making the flow less efficient.

What else can we do with start element formulas?

When you want to trigger your flow in case the triggering object record is created or updated, and you want to build sophisticated criteria, then the formula entry conditions are ideal for this purpose.

A popular use case is the auto-naming of records when a new record is created. For example, you can append the Industry picklist value to the Account name using a before-save flow.

Here is the formula resource that does that:

The difficulty is when you want to trigger such flow on create and update. If you don’t build your flow carefully, you will append the same thing to the name multiple times based on multiple updates. You will need to check whether the auto-name logic ran before if you want to avoid this outcome.

Here is the start element formula that ensures that:

I recommend you go and play with this functionality yourself if you haven’t already. You will like it. It is super powerful.

This is the only area where we have a function, a logical operator picker, and a syntax check button within flow.

If you have comments on this topic, please join the discussion on Twitter or LinkedIn.

Enjoy.

P.S. Originally published on 07/18/2022.

Read the previous issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.

Standard
Flow Tips Newsletter

Standard or Custom Object? – Salesforce Flow Tips Newsletter

Hello folks,

Recently, I posted polls on Twitter asking about standard objects: What cloud license does each standard object come with? The answers to these questions are widely unknown. You will see that only about half of the respondents got the answer right.

As a response to these posts Emily McCowan, an Architect, posted this writeup and clarified some of the confusion around this topic. Please read it, it is very good.

You may know the data model very well. You will also need to know what standard objects come with your license to decide whether to use them when the need arises.

Enjoy.

P.S. Originally published on 07/08/2022.

Read the previous issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.

Standard
Flow Tips Newsletter

The Importance of the Data Model – Salesforce Flow Tips Newsletter

Hello folks,

I wrote this several times before:

If you want to attempt Actions and Related Records flows, you need to know the schema very well. This can be easily done with the schema builder in your Org.

There is another good way for reviewing the data model. The Architect’s site by Salesforce has the data model diagram posted for the most popular Clouds. You can go there and view and download the diagrams in pdf, png and Lucidchart format:

Click here for the Architect’s Site by Salesforce.

You can see the Sales Cloud example image from the Architect’s site above. Please click on the image to see a bigger version.

Enjoy.

P.S. Originally published on 06/27/2022.

Read the previous issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.

Standard
Flow Tips Newsletter

Which Object Do You Trigger On? – Salesforce Flow Tips Newsletter

Hello folks,

Suppose you know you need a record-triggered flow: You want to perform automated steps based on the transactions executing in your Salesforce Org.

If you deal with related records, you know you will be in the after-save mode (a.k.a. Actions and Related Records).

If you have come this far, this means you have already found answers to two essential questions:

  1. What type of flow do I need?
  2. If it is a record-triggered flow, will it be before-save or after-save?

You know that I answer a lot of flow questions on a regular basis. My observation is that folks often struggle with the next critical step:

Which object will I be triggering on?

Based on the previous decisions, we know you are already dealing with at least two objects. However, suppose a junction object is involved, like an Opportunity Contact Role that connects the Opportunity to Contacts or an Opportunity Line Item that connects the Opportunity to the Products. In that case, you may have three or more objects involved.

This is the part where things get confusing:

Which object will I trigger on, and what object(s) will I create/update?

The answer is surprisingly simple when you fill in the blanks in this format:

I want to create/update __ Object records when __ Object records are created/updated.

What you write in the second blank will show you what object you are triggering on.

Once you know that, you will need to go from one Object to the other using the relationships. Depending on the depth and the structure, you may use multiple gets.

I thought I’d step back from technical posts for now and focus on the fundamentals again.

Enjoy.

P.S. Originally published on 06/15/2022.

Read the previous issue of the newsletter here.

Read the next issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.

Standard
Flow Tips Newsletter

The Answer for the Collection Filter & Collection Sort Challenge – Salesforce Flow Tips Newsletter

Hello folks,

Last week I told you that I challenged myself to use as few elements as possible when searching for particular records among the cases in my Org. You can find the Collection Filter and Collection Sort post here.

I started with a get element that returns all the cases that have both account and contact assignments. I was able to extract the following information with only one get element:

  • Most Recently Modified Case
  • Oldest Modified Case
  • Oldest Modified Case Account Name
  • Number of Cases by this Account
  • Most Recently Closed Date for this Account
  • Contact Id on this Case
  • Number of Cases for this Contact
  • Oldest Closed Date for this Contact on this Case

It took me 21 elements, including one get, to find all these records. How did I achieve this? Check the image above for the details. Click on the image to see a bigger version.

Enjoy.

Andy Engin Utkan

P.S. If you like this newsletter, forward it to your friends. They can sign up for it here.

Enjoy.

P.S. Originally published on 06/07/2022.

Read the previous issue of the newsletter here.

Read the next issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.

Standard
Flow Tips Newsletter

Collection Filter and Collection Sort Challenge – Salesforce Flow Tips Newsletter

Hello folks,

How powerful are the collection sort and collection filter elements? How should you use them?

I experimented with collection filter and collection sort elements to see how far I can go using only one get element. In other words, I wanted my flow only to use up one SOQL against the governor limits.

I started with a get element that returns all the cases that have both account and contact assignments. I was able to extract the following information with only one get element:

  • Most Recently Modified Case
  • Oldest Modified Case
  • Oldest Modified Case Account Name
  • Number of Cases by this Account
  • Most Recently Closed Date for this Account
  • Contact Id on this Case
  • Number of Cases for this Contact
  • Oldest Closed Date for this Contact on this Case

Please see the image for the results.

How many elements did I use? Did I have to loop?

Here are the answers:

  • Your get element gives you sorting functionality. Use it.
  • You have to loop to get the min and max values, such as the oldest and most recent, sorted by Date and Time. But you need to loop only for one iteration. So you can exit after you assign the first record to a variable.
  • Your loop can use the existing sort or the reverse sort. Use this functionality.
  • Initially, I used a counter variable to exit the loop, but this was unnecessary. You need to exit the loop regardless after the first iteration. Insert a decision and connect both branches to the next element outside the loop.
  • You can get a count of records by using an assignment element with the operator “equals count”.

I experimented with the formula criteria inside the collection filter element without much luck. I think this functionality does not allow for filters with variable values on the right side of the equation. “ContactId on the current record = ContactIdVariable” formula did not work.

What do you think? Can these elements save you lengthy loops and executed elements?

How many elements, excluding the start or the end element, did I use to extract this information.

Join the discussion on LinkedIn here or Twitter here.

Live session recording links:

Watch Melody Lwo of Salesforce Flowsome and me either on LinkedIn here or YouTube here.

Enjoy.

P.S. Originally published on 05/30/2022.

Read the previous issue of the newsletter here.

Read the next issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.

Standard
Flow Tips Newsletter

Post to Slack from Flow in 6 Easy Steps – Salesforce Flow Tips Newsletter

Hello folks,

This is an exciting week for all of us. The Release Readiness live webinars are here.

I was reading the Release Notes for Summer 22 this past weekend and I was wondering whether I can use the brand new Slack invocable actions in my Salesforce flows already. Salesforce announced the new actions are in beta, and they will be released sometime in June. It turns out I can already use them. I don’t even need a Preview Org or Summer 22 Sandbox for it. The steps required took some time to discover, but the whole thing is fairly simple to set up.

I am posting a step-by-step guide here so that you can dive directly into it. Try it now without wasting any time. Here are the 6 steps you need to take to post to Slack from Flow:

1. Go to “Setup” and “Enable Slack for Salesforce”. Review and agree to the Pilot terms if you want to proceed.

2. Create and assign a permission set to the user who will post on Slack and use the integration. The permission set will have “Connect Salesforce with Slack” system permission activated.

3. Now go over to your Slack Workspace. You can use a free Workspace, but if you have used all your permitted 10 App limit, you will need to remove an App. On the upper left side click on “More”, then “Apps”. On the screen you see in the middle, click on “App Directory”. Find “Sales Cloud for Slack”.

4. Go to the App page. Click on “Add to Slack”. This will take you to a web page that is super confusing. Find “Add Sales Cloud For Slack App”. Click on the link. Give the necessary permissions. (Update: I received feedback that the Sales Cloud Slack app did not work for some folks. If this is your experience try one of the other apps on the same page. I tested the Salesforce Digital HQ app as well, and this app worked for me.)

5. Now go to any public channel on Slack. Click/tap on the channel header where you see the title. Scroll all the way down and get the channel ID as seen below.

6. Go to Salesforce and build a simple Autolaunched Flow with one single element. You will need to add the invocable action “Send Slack Message (Beta)”. Configure it as seen below. Include the Slack Channel ID. Run it. Voila!

Next week, I will continue my preview with the new screen flow functionality.

Enjoy.

P.S. Originally published on 05/24/2022.

Read the previous issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.

Standard