Paging grid row limitation

Question

Hi, 
 
 I have a paging grid which is displaying only 1,175 rows in all environments but from query entity i am getting 3000+ records and from sql query as well. Is there some limitation on the number of rows that are displayed in a paging grid or what could be the reason for this?

TIA!!

Peter Lewis · Answer

Can you check to see if your primary key is unique? Appian should always return the correct number of rows if you use -1 as batch size, but it relies on a count of the IDs for all other batch sizes, so it can return incorrect numbers if the primary key isn't unique. 
 Even if you don't have a unique field, you may need to create a view that uses a row count field or something to make sure your total counts are correct.

Mike Schmitt · Answer

This is a known issue when querying from a View where the View's CDT is configured with a Primary Key column that is not actually unique within the View's data set. In other words, if whatever column you've defined as "primary" in the CDT has duplicates in different rows of the view table, only the unique instances will be counted when returning the paged TotalCount. I don't consider this an error within Appian but rather an error in implementation. The solution to this is to configure your View such that it has at least one column that will always be unique, and configure the CDT for the view to use this column as the Primary Key.