Skip to main content
Topics#Salesforce DeveloperBaird Straughan の質問
Baird Straughan が「#Salesforce Developer」で質問
2023年8月23日 15:35

Flow for field update fails if source is empty/null. Workaround?

I have a very simple Flow that updates a field on Oppty if it is empty.  It's a before operation in Flow, and basically if the field is empty the Flow populates the field with a value from a field in that record's Campaign (which we require).  I the "Passage" field in Oppty is blank, fill it with the value from the Passage field in  the Campaign that record is associated with.

It worked fine until I changed the name of the source field in Campaign because the two fields with identical names was confusing users, especially in reports.  After I changed the name and checked that the Flow was updated properly, the flow works fine unless that source field (now called "Campaign Passage") is empty.  In that case the Flow now fails.  The error is something like source not found or not set or assigned.

I can't figure out why it worked before the name change but now fails.  I can see that if the source field is empty and the Flow replaces that with nothing (leaves it empty) there's a possibliity for an endless loop (though only if it's recursive).  If this is the source of my error, I'd be interested to know that's the problem.  But then why didn't it fail before the name change?

Any thoughts would be greatly appreciated.  
2 件の回答
  1. Baird Straughan
    2023年9月6日 14:22
    Hi Swetha,

    Thanks for replying.  Sorry for the slow response.  I've been busy!  Here are some more details.  The flow is started when an Oppty record of a certain record type is created or updated with an empty "Passage" field (empty string, and any time it is updated and meets the conditions).  The only action in the Flow is the field update, whereby the value from the "Campaign Passage" field in the source campaign is entered into the Oppty "Passage" field.  Then the flow ends.  Like I said, very simple.

    Debug doesn't show any errors now.  It was showing the error I mentioned above, something about the source either "not found" or "not set or assigned."  Unfortunately, it's not showing that error now.  I'm a bit confused at this point.  I wonder if it was connected to the field name change, and perhaps the change didn't fully register for a fairly long while after (days I think).  Oddly the field name showed as changed right away in the Flow itself.

    I'm looking for the original error email but I can't find it at the moment so can't provide the exact error.
回答を記入...
0/9000