I maintain over fifty flows and I am currently struggling with a Data Action that returns an array of customer records from our CRM. I need to find the record where the ‘Status’ is ‘Active’ and extract the ‘PolicyNumber’ field. I am using a JSONPath filter like $.records[?(@.status=='Active')].policyNumber, but the Data Action returns an empty string when there are multiple active records. How can I force the Data Action to return only the first matching item from the array so that I can use it in my Architect flow?
I have seen these JSONPath filters fail in the Data Action UI. The Genesys Cloud translation engine is very limited when it comes to complex filtering. Instead of doing the filter in the ‘Translation Map’, you should use a ‘Velocity’ macro in your ‘Response Template’. You can use a #foreach loop to iterate through the records and an #if statement to find the first active one. It is much more robust than relying on the JSONPath engine!
I inherited our GC org six months ago and I am still learning the ropes. To follow up on Han77, here is a quick Velocity snippet you can use: #foreach($item in $records) #if($item.status == 'Active') $item.policyNumber #break #end #end. This will stop at the first match and return only that value. I used this for our ‘Member Lookup’ flow last week and it saved me a lot of time. Make sure you also handle the case where no active records are found, or your Architect flow will hit a ‘Type Mismatch’ error!
I want to add a note about ‘Performance’. While Velocity macros are powerful, they add a small amount of latency to every Data Action execution. If your CRM returns a massive array (e.g., hundreds of records), your macro will slow down significantly. You should try to perform the filtering on the ‘CRM Side’ by using a more specific API query if possible. Only use the Velocity macro as a ‘Last Resort’ for legacy APIs that do not support server-side filtering!