Could not display interface. Please check definition and inputs.

Dan over 10 years ago

I am attempting to use a filter with the Portal to Sail Plug-in but am encountering an error.

My code is the following:
fn!getPortalReportDatasubset(
reportId: cons!APPIAN_ALL_TASKS_REPORT, pagingInfo: topaginginfo(1,10),
filters: { { field : "0", operator : "LIKE", value : "*a*" } },
contextIds: {}
)

Where cons!APPIAN_ALL_TASKS_REPORT is a constant that refers to the Appian out of the box "All Tasks" report.

I've attached a screenshot of the error I am seeing for additional context.

...

Discussion posts and replies are publicly visible

0 venkats533 over 10 years ago

try the following change:
FROM filters: { { field : "0",
TO filter: { { field : 0,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 venkats533 over 10 years ago

the parameter name is filter - singular not filters (plural)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 simranjits over 10 years ago

There is a datatype mismatch between what you are sending as an input and in what type is data present. I got a similar error yesterday while sending input to a queryEntity function. Although, that input was of the same type, but it gave me an error. After wrapping the rule inputs with tointeger(), issue got fixed.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dan over 10 years ago

Venkat, the documentation for the expression has the parameter name as "filters", not "filter". I have also tried 0 vs "0" in the field parameter.

@simranjits, I am not sure I follow the change you are suggesting. Are you saying that the "value" in the filter I am trying to pass in is of the wrong type?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 simranjits over 10 years ago

yes..exactly...read the third line of your error message...although the type may be correct as per you, but you can try wrapping it by an appropriate datatype conversion function.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dan over 10 years ago

That didn't work. I did take a look at the plugin and noticed that we are using version 1.22 instead of the latest. Could have something to do with the issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jorgea272 over 10 years ago

I had an issue with the filtering. What format is the column on the report? I ran into some issues of filtering on an integer column and having to tostring the integer PV in order for the filter to work properly.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dan over 10 years ago

It is the "Name" column of the out of the box "All Tasks" report, so there I don't think an integer issue would apply.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jorgea272 over 10 years ago

Do you know for sure the field value is "0"? The order of the columns in the report does not match the field value. You should output the values of columns[1].field and make sure that is the correct value. I have it my code to write out the field array to a separate local variable the I reference that local!fields[1] to ensure that whatever the field id is the i get the correct one for that column. Downside is that you have to execute the datasubset twice in order to get the fields array.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dan over 10 years ago

Yes, I've confirmed that the field matches.

Reading the error, it seems to me like the issue is related to conversion of:
{ { field : "0", operator : "LIKE", value : "*a*" } }

into a List of type Portal Report Filter but I don't see any real issue with code in that regard. I have also tried using a type constructor to no avail.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel