If a user enters a search value and selects filters in a service-backed record,

No Carloss, It doesn't guarantee that you will always have the search value. You can use rsp!query (Query data type) in Expression context of Record Type.

Then refer the searchKey inside your logical expression as follows:
with(
local!queryCondition: index(
ri!query,
"logicalExpression|filter|search",
null
),
local!searchKey: index(
local!queryCondition,
"searchQuery",
null
)
)
And also refer following url for more details:
forum.appian.com/.../Service-Backed_Record_Tutorial.html

Attached is a snippet which shows what the rsp!query object looks like when a search term has been entered and two filters have been selected. You can also use this snippet to test any expression that requires an ri! in the form of the rsp!query object.

rspquery.txt

Thanks both. I already have an implementation that can take the data from rsp!query and use it in a!queryEntity, but it currently relies on the type!Search object being the last element (after all the type!QueryFilters), as that's what I've seen in my own testing. That's why I wanted to know if that's guaranteed.

Not sure why you'd need to rely on it being the last object? The parseRspQuery rule in the tutorial link above will get it if it exists - once you've got it into a local you can handle it first or last regardless of the order...?

It's called "not looking for the most recent documentation" :) Thanks again.

No problem! :)

I should add - that service backed record tutorial is excellent, and sets out a very nice pattern for the creation of service backed records and addition of filters, search etc.

Hey Phil, do you happen to have an idea of what rsp!query looks like when a multi select filter is chosen?