I have a quick but important update for you this week.
An issue I see quite frequently happens when folks try and remember to use the assignment element instead of the update element in record-triggered flows. You can indeed use an assignment element instead of an update element in a before-flow to change the field values on the record that triggered the flow. However, this is not true when running your record-triggered flow in after-save mode.
To avoid confusion and facilitate an easy transition between before-save and after-save, always use the update element in a record-triggered flow to update the field values on the record that triggered the flow.
I am sure you know by now; before-save is labeled as Fast Field Updates, and after-save is labeled as Actions and Related Records in the record-triggered flow start element configurator.
If you have any questions, please do not hesitate to ask them on the Salesforce Break Slack. The invitation link is on https://SalesforceBreak.com.
Content and event updates:
- Orchestrator: Brian Kwong has a super nice recording of an orchestrator built on YouTube. It is no secret that I like live sessions and tutorial-style recordings. Click here to watch the Orchestrator video.
- Flow Office Hours: My good friend Terry Miller and I run monthly office hours for flow. We have a Zoom session every month. Click here to learn more about the flow office hours and to register for the session.
P.S. Originally published on 04/05/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.