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
5 replies
Subscribers
7 subscribers
Views
2272 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Hi All, I was trying to pass paging info (along with other filtering detail
Mike Schmitt
Certified Lead Developer
over 8 years ago
Hi All,
I was trying to pass paging info (along with other filtering details) into a rule for use with Download Data Subset; I got everything working but for some reason it would never match the "ascending" value in the on-form sortInfo.
Then I did a test, calling a!toJson directly on a!sortInfo(field: "testFieldName", ascending: false()) - and the resulting JSON string *always* assigns a value of true() to the "ascending" property. I tried seeing if it just always treats boolean properties this way, but in other instances they work. In the attached screenshot I am displaying a sample of each.
Is this a known limitation of calling a!toJson on complex data created by an a! rule? Or maybe just an oversight? For my export requirements I side-stepped the issue by passing the ascending property directly into its own field in the json string, but it seems like such workarounds shouldn't really be necessary.
OriginalPostID-157911
OriginalPostID-157911
Discussion posts and replies are publicly visible
Parents
0
Mike Schmitt
Certified Lead Developer
over 8 years ago
Ironically, i'm trying it in a 7.8 environment too. I'll try it real quick in a 7.9 and see what happens.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Mike Schmitt
Certified Lead Developer
over 8 years ago
Ironically, i'm trying it in a 7.8 environment too. I'll try it real quick in a 7.9 and see what happens.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data