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
4818 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Hi Everyone, We are seeing some strange behavior when we are populati
brettr
over 9 years ago
Hi Everyone,
We are seeing some strange behavior when we are populating a grid using a queryEntity inside of the with instead of a todatasubet. If we sort on a column that has all of the same data on the first page, and the same data on a couple rows on the second page, there are some rows that are never actually displayed on the grid. Our current theory is that this is occurring because there is no secondary sort field with a queryEntity, and the videos that I will link to later seem to support that. It looks like a query rule will have a secondary sort based on the "Sort query results by" configuration in the query rule itself if you change the pagingInfo.sortInfo that is passed into the query rule. Unfortunately, a queryEntity actually breaks if you pass it a pagingInfo that has an array of sortInfo, so I do not see a way to define, or force, a secondary sort field. According to documentation, it looks like sorting on multiple colum...
OriginalPostID-177486
OriginalPostID-177486
Discussion posts and replies are publicly visible
Parents
0
Andrew P Gramann
Certified Lead Developer
over 9 years ago
I've seen this occasionally if you try to sort on a field that is not unique.
It's not ideal, but you could wrap your entity in a view that returns 2 columns for every field that is displayed in your grid that is not unique. For the duplicate column, append the primary key to the columns's actual value. You can then use this duplicate field as the "field" parameter in your paging grid's columns configurations (ensuring that any sorting is done on a unique column) and keep the original field for the values that you will display.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Andrew P Gramann
Certified Lead Developer
over 9 years ago
I've seen this occasionally if you try to sort on a field that is not unique.
It's not ideal, but you could wrap your entity in a view that returns 2 columns for every field that is displayed in your grid that is not unique. For the duplicate column, append the primary key to the columns's actual value. You can then use this duplicate field as the "field" parameter in your paging grid's columns configurations (ensuring that any sorting is done on a unique column) and keep the original field for the values that you will display.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data