Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
13 replies
Subscribers
8 subscribers
Views
5907 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
I am trying to construct a Web API that queries a data entity and compares a fie
judym598
Certified Senior Developer
over 9 years ago
I am trying to construct a Web API that queries a data entity and compares a field in that data entity with an array of values that I've stored in a local variable (created from another a!queryEntity). I've hardcoded the value in my first query so I know what results I should get in the second one. Both queries work individually, but I get this expression evaluation error when I combine them. Any suggestions on what I'm missing? I'm pretty sure that once I get this working, I'll also have to add something to account for null values in the first query....but that's another issue. See the attached file for the code.
Expression evaluation error at function a!queryEntity [line 33]: Cannot apply operator [IN] to field [checkid] when comparing to value [TypedValue[it=197,v={TypedValue[it=1,v=621],TypedValue[it=1,v=622],TypedValue[it=1,v=623]}]].
NestedQueryForWebAPI.txt
OriginalPostID-200061
OriginalPostID-200061
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 9 years ago
@judym If you are sure that '0' doesn't have any significance at any point of time, you might proceed with using {0}. Also it might be worth adding the comments in code stating why {0} is added rather than doing null checks, as few might not be able to understand this.
At the same time, if you come across the records with a value '0', then this might fail and in this case null handling will be beneficial which will be like attached code snippet.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 9 years ago
@judym If you are sure that '0' doesn't have any significance at any point of time, you might proceed with using {0}. Also it might be worth adding the comments in code stating why {0} is added rather than doing null checks, as few might not be able to understand this.
At the same time, if you come across the records with a value '0', then this might fail and in this case null handling will be beneficial which will be like attached code snippet.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data