Is it best practice to seperate a flow out into its specific Before save and After save flows even if you may be querying the same related record twice?
For example,
Flow fires when a field on Contact changes.
Goal is to update the related Acc(s) based on Contact’s current and previous value change.
5 answers
I figured it out.
Because flow now define “After Save” as Related Record updates it made no difference to use both $Record. and $Prior.Record. in the same flow.
However flows are still very frustrating because I could have avoided an additional Get Record if it let you filter AccContRel table on AccountId.{fieldname}. This is allowed in the Decision elements for some reason but not Get Records
