I have a scheduled flow that reads customers from System A, creates them in System B (where a customer ID is assigned), and then uses the enrich step to write system B’s customer ID back to a field in System A.
This flow is filtered to only run for customers that don’t yet have a customer ID in System A, so that a new customer is only created in system B once. It works well when there actually are new customers, however when there are no new customers I get failed run notifications because many of the fields that exist in the flow are from JSON fields that have been flattened. The fields that I’m pulling from the flattened JSON don’t exist when there is nothing to flatten.
Examples below. How can I avoid a “failed” notification driven by using flattened JSON info in my flow?
The column Addresses.PrimaryBilling no longer exists.
Sub QB Terms ID
The column PaymentTerms.Name no longer exists.
Could not find left column matching “PaymentTerms.Name”