I am running an Quey Rule in a Record to gather data for a grid. It is a simple

... data: index(local!datasubset.data,"approveDeny",{})
),
a!gridTextColumn(
label: "Comment",
data: index(local!datasubset.data,"comment",{})
)
},
value:local!pagingInfo,
saveInto: local!pagingInfo
)
}
)
)
)

I have created the input variable in the Interface, selectFeasibilityID.

Hi Leslie,

In line10 of your code [label: "Response for " &index()] - index() takes three arguments but you only specified two. The right syntax would be similar to -

label: "Response for " & index(local!datasubset.data, ri!selectFeasibilityID, {})

I made that change, even took that line out and still have the same error.

I removed the if(local!datasubset.totalcount<1, and that seemed to help. I no longer get the Interface Definition: Expression evaluation error but I am now getting "Interface Definition: Expression evaluation error in rule 'pd_getfeasibilityresponsesbyfeasibilityid' (called by rule 'pd_feasibilityresponses') [line 20]: " It is very Query rule is very simple. It looks up the list of records by feasibilityId. feasibilityId is a Numeric(Integer) field. There are records in the table.

I don't see the rule 'pd_feasibilityresponses' in your previous code. Could you please paste that part of the code?

Here is the PD_feasibilityResponses code:
load(
local!data: rule!PD_getFeasibilityResponsesByFeasibilityId(ri!selectFeasibilityID),
local!pagingInfo:a!pagingInfo(
startIndex: 1,
batchSize: 5
),
with(
local!datasubset: todatasubset(local!data,local!pagingInfo),
label: "Response for " & index(local!datasubset.data,ri!selectFeasibilityID,{}),
a!sectionLayout(
firstColumnContents: {
a!gridField(
totalCount: local!datasubset.totalCount,
columns: {
a!gridTextColumn(
label: "Assignee",
data: index(local!datasubset.data, "assigneeName",{})
),
a!gridTextColumn(
label: "Response",
data: index(local!datasubset.data,"approveDeny",{})
),
a!gridTextColumn(
label: "Comment",
data: index(local!datasubset.data,"comment",{})
)
},
value:local!pagingInfo,
saveInto: local!pagingInfo
)
}
)
)
)

Thanks Leslie. Have you tested the PD_getFeasibilityResponsesByFeasibilityId rule in the expression editor? I used a similar rule with your code above and found no errors.

That was a great suggestion, so I did just test it in the expression editor and it does work. It pulls back the expected records from the table.

Interesting. Here's a few other tests that you might try -

1. Use a different query rule in place of PD_getFeasibilityResponsesByFeasibilityId (Sometimes the interface designer needs a refresh so you might try opening a new designer window and pasting your code)
2. Check the application server log located in <APPIAN HOME>/log for any errors.