Is there a default limit to the amount of data displayed within a Record view? I have a view that has 235 rows and 40 columns. When I try to display the data from this view, only 42 rows appear. I can export the full dataset and I can search for and filter for the full range of values in the table. But the row count and pagination isn't showing the correct values.
Discussion posts and replies are publicly visible
Have you tried to debug this issue using a query entity to see how many rows it returns?
Yes. The all the rows are returned.
Is there any sort of filter logic at all in the query? Anything that would theoretically prevent some kind of row from being returned by the query, or is it just SELECT * FROM ; ?
Are there any conditions on JOINs that might prevent some rows from being joined when forming the VIEW? You might try switching from JOIN to LEFT JOIN to RIGHT JOIN to OUTER JOIN to see what that does to your results.
no logic applied. When exporting to excel, the full expected dataset is returned. The issue is the displayed data. Even when filters are applied they are applied to the entire dataset not just the 42 rows.
Ok...Could the "Visibility" property be set on the Grid in the Record View? Try switching to List View and see what happens.
Not sure what you mean. The only visibility setting I see is for columns not rows.
Hi naomi0001,
This happens in case if your view doesn't have a unique identifier[Primary Key in your CDT]. You can verify that by running the below SQL code.
SELECT COUNT(DISTINCT <PRIMARY_KEY_COLUMN_NAME>) from <YOUR_RECORD_VIEW_NAME>;
If the above result is not equal to the actual rows count. It means your record is referring to a view which doesn't have a unique identifier. You may have to build your view to have a unique identifier which can be referred as a Primary Key in your CDT.
Thanks for this. I was able to verify.