8. A model-driven app view with 50,000+ records is slow to load. What would you check (indexing, view filters, related-record columns)?

Start by checking whether the view is retrieving more data than necessary.

  • View filters: Use specific filters so Dataverse returns only the required records.
  • Indexes: Check whether columns used for filtering and sorting are properly indexed.
  • Related-record columns: Avoid unnecessary columns from related tables, which can increase query complexity.
  • Sorting: Check for expensive sorting on large datasets.
  • Number of columns: Remove unnecessary columns from the view.
  • Paging and search: Check that the view isn’t displaying an unusually high number of records per page. Also check whether Dataverse Search is enabled for large-dataset searching rather than relying only on older Quick Find behavior.

Example: Instead of loading 50,000+ cases, create a view filtered to Active Cases assigned to the current team and display only the required columns.

Interview tip: Don’t immediately blame the record count. Check the query, filters, sorting, related columns, indexing, and paging first.

Scroll to Top