How to use ISCHANGED and PRIORVALUE in Before Save Flows by GORAV SETH

/6 Comments/in /by

GORAV SETH demonstrates how you can use ISCHANGED and PRIORVALUE in Before Save Flows
Check it out

You might also like
How to Build a Flow Action with Apex
Get Record Type Info by Object - Flow Action
Navigate to a Record in View or Edit Mode at the end of a Flow
Flow Use Case - New Task Button with picklist for selecting the record type
Flow Extensions April Update
Update N Records in Flow Without a Loop by Jessie Rymph
How to Declaratively Handle with Flow When Files are Shared to Records by DOUGLAS C. AYERS
Creating a unique collection in flow by GORAV SETH
Subscribe
Notify of
guest
6 Comments
Inline Feedbacks
View all comments
Alex Edelstein

Very nice!

0
Reply
Marie Niekamp

Thank you for posting! I’d love to learn more about Before Save Flows. If you have recommendations on other articles, please let me know.

0
Reply
Tamar Erlich

Hi Marie, there are several posts on this site about before save flows. Here is the link to the official documentation
https://help.salesforce.com/articleView?id=flow_concepts_trigger_record.htm&type=5

0
Reply
Vishesh Maskey

After Save did not work
I was very excited to get rid of few PBs and did a Unit test to check out this feature for After Save. As you had mentioned in your comment it worked for After Save as well. However it did not seem to work for me 🙁

FlowNameChanged.png
0
Reply
Vishesh Maskey

Actually this worked for me. The additional Update Records is not needed. The assignment does the update. Just wanted to leave this here if someone else is having the issue. Works both with Before and After Save.

0
Reply
Joseph

Unfortunately it didn’t work in after save event, could you please explain if there is any way to check the ischanged in after event ?

0
Reply
wpdiscuz   wpDiscuz