Queryable Mode

• Feb 04, 2026
• 2 minutes to read

Queryable Mode Overview

The Queryable mode is used in lookup List Views if the corresponding List View node of the Application Model specifies any data access mode other than Client.

The collection source exposes an IQueryable<T> query shaped according to the settings specified in a List View. In this mode, a List Editor does not load all objects immediately. The List Editor control extends the query to load only the objects visible in the control. Once ready, the editor iterates the query and loads objects from the database.

Queryable mode is supported in LookupPropertyEditor and DxTreeListEditor.

Note

The default data access mode for lookup, root, and nested List Views in ASP.NET Core Blazor applications is Client.

Expected Behavior

• In this mode, List Views do not show custom persistent properties (IsCalculated = false) created in the Model Editor and the CustomizeTypesInfo method.
• This mode does not support the filter, sort, and group operations with the following properties:
  • Custom properties added at runtime.
  • Non-persistent properties that are not decorated with the PersistentAlias (XPO).
  • Non-persistent properties in EF Core.
• Queryable collection sources create a new collection from a query and use it instead of the original collection. As a result, custom logic implemented in an original collection’s getter and event handlers is not executed.
• This mode does not support legacy databases that use compound primary keys.
• Data-aware operations (such as grouping or sorting) are performed by the database server. This approach significantly increases the List View’s performance when you need to process many objects. All properties are calculated as needed (for example, if a property is visible in the List View or is used in the Appearance and Security rules).
• This mode does not support advanced syntaxes, such as:
  • The Single aggregate function
  • Free Joins
  • Upcasting