Order results returned in Pipeline search query

@Stephen Study

Because the pipeline object that is returned from the ​Search Records action is a "list" you will need to be clever about how you reference the value. Unlike when you iterate through the list using the built in loop action, you can't simply reference the value by dragging and dropping fields from the visual builder. Using Jinja, you can (similar to working with an array in other languages) be explicit about which item in the list you'd like to get the value from. For example: If I wanted the Record ID# from the first record in a list object, instead of using the expression that shows up when I drag and drop the field {{a.id}} I would specify that I wanted the value from the first record in the list like so: {{a[0].id}} and if I wanted the second I might use: {{a[1].id}}

Here's what that looks like in action:

Cheers

I stumbled upon this thread last night while looking for a similar solution. I found something that worked after tons of trial, error, and googling. Here's a screenshot. 

It takes the array of results returned in step B, looks for the one with the highest attribute for the field called "specificity_score" and returns that RID to a field in the action step. It's not exactly sorting results but if you were looking for the "earliest" record, you could set the attribute to a "created_date" or similar, and use a min() filter instead of max()

ex: 

{% set desiredrecord = b|min(attribute="created_date")%}
{{desiredrecord.desired_field}}