MainGrid

The MainGrid component is a standalone grid for displaying Dataverse records. Unlike SubGrid, it does not require a parent RecordContext — it loads records directly from a specified table or view.

Loading by Table Name

Set the TableName parameter to automatically load all public views for that table. The first default view is selected initially.

<MainGrid TableName="contact" />

Loading by View IDs

Use ViewIds and DefaultViewId to control exactly which views are available and which one is selected on load. You can also provide CustomViewDefinitions with inline FetchXML to define views directly in code.

<MainGrid ViewIds="_viewIds"
          DefaultViewId="@(new Guid("..."))">
</MainGrid>

@code {
    private List<Guid> _viewIds = new List<Guid>
    {
        new Guid("..."),
        new Guid("..."),
    };
}

Custom Views with FetchXML

Use CustomViewDefinitions to define views with custom FetchXML queries. This is useful for views that include filters based on the current user, linked entities, or other dynamic criteria.

Note

The Id for a custom GridViewDefinition must be a unique random GUID that does not correspond to an existing Dataverse view. If it matches an existing view ID, the Dataverse view will take precedence and the custom definition will be ignored.

private List<GridViewDefinition> _customViews = new List<GridViewDefinition>
{
    new GridViewDefinition
    {
        Id = new Guid("..."),
        TableName = "contact",
        DisplayName = "All Contacts",
        FetchXml = @"<fetch>
            <entity name='contact'>
                <attribute name='fullname' />
                <attribute name='emailaddress1' />
                <order attribute='fullname' />
            </entity>
        </fetch>",
        Columns = new List<ViewColumn>
        {
            new ViewColumn { ColumnName = "fullname", Width = 200 },
            new ViewColumn { ColumnName = "emailaddress1", Width = 250 },
        }
    }
};

DisplayName

Set DisplayName on a GridViewDefinition to provide a default label for the view in the dropdown selector without requiring a localization file entry. If a localization key exists at tables.{TableName}.views.{Id}.label, it takes precedence over DisplayName. This is useful for custom views where you want a readable name immediately without adding a localization entry.

Toolbar Buttons

The MainGrid supports the same toolbar buttons as SubGrid. For standalone grids, NavigateNewRecordGridButton and NavigateOpenRecordGridButton are commonly used to navigate to separate form pages. See the Grid Buttons documentation for a complete reference of all available buttons and their configuration options.

<MainGrid TableName="contact">
    <Buttons>
        <NavigateNewRecordGridButton Url="/contacts/new" />
        <NavigateOpenRecordGridButton Url="/contacts/edit?contactId={0}" />
    </Buttons>
</MainGrid>

Search Box Behavior

When the user types in the grid's search box, the configured view is automatically re-queried with additional filter conditions applied to every search-eligible column shown in the view. The conditions are joined with OR logic, so a record is included if any of its visible columns match the search term. The default match semantics differ depending on the column type.

Text and Lookup Columns

Text columns (string fields) and lookup columns (matched against the target record's primary name) use a starts with search by default. Typing joh matches values that begin with joh — for example John or Johnson. The match is delegated to FetchXML's like operator, which is case-insensitive in Dataverse.

Use * as a wildcard for more flexible matching. Typing *hn performs a contains-style match (e.g. John, Johnson); typing j*n matches values where any characters can appear between the j and the n (e.g. John, Joneson). The wildcard is converted to FetchXML's % wildcard at query time.

Choice Columns

Choice columns (option sets / picklists) and multi-select choice columns are matched against the localized display label of each option rather than the underlying integer value. Labels are compared case- and accent-insensitively in the current user's culture, so typing cafe will match an option labelled Café. When one or more option labels match, the query emits a FetchXML condition against the matching option values — an in condition for single-select choice columns, or a contain-values condition for multi-select choice columns. When no labels match, the column contributes no condition (keeping the OR filter compact).

Choice columns honor the same * wildcard as text columns: by default the match is starts with (typing act matches Active), and a leading * switches to contains (typing *act additionally matches Inactive). Matching rows have the matched substring highlighted in the grid, exactly like text-column matches.

Numeric and Money Columns

Numeric columns — int, big int, decimal, double, and money — support comparison operators in the search term. The search box parses an optional leading operator and applies the corresponding FetchXML condition operator:

• = 100 or just 100  —  equal (the default when no operator is specified)
• > 100  —  greater than
• < 100  —  less than
• >= 100  —  greater than or equal
• <= 100  —  less than or equal

Note

Search conditions for every column type are added to the same OR filter group, so the same search term is evaluated against text columns, lookup columns, choice columns, and numeric columns simultaneously. Typing 100 in a grid that has both a name column and an amount column will match records whose name starts with 100 or whose amount equals 100. The search filter is layered on top of the view's existing filter, so view-level constraints (such as a statecode = 0 filter) are always preserved.

Disabling Search

Set AllowSearch="false" on the grid to hide the search box entirely. This is useful for grids that contain only a small fixed set of records, or where filtering is handled externally (for example via a custom toolbar).

<MainGrid TableName="contact" AllowSearch="false" />

Full Size Mode

Set FullSize="true" to make the grid expand to fill the full height of its parent container. This is useful when the grid is the main content of a page.

<PageLayout>
    <Body>
        <MainGrid TableName="contact" FullSize="true" />
    </Body>
</PageLayout>

Persisting Grid State

Use PersistedStateQueryParameter to persist the selected view, page number, page size, and sort to a single URL query parameter. The state is restored when the page is opened with that parameter present — useful for bookmarks and shared links. Pass IncludeSearchInPersistedState="true" to additionally persist the current search text (off by default since search terms can be sensitive).

<MainGrid TableName="contact"
          PersistedStateQueryParameter="gridState" />

Multi-Table Grids

A MainGrid can display views from different tables by including view IDs from multiple tables in the ViewIds collection. When the user switches views, the grid automatically loads the correct table's data. Use the OnClick callback on navigation buttons to dynamically set the URL based on the selected view's table name.

<MainGrid ViewIds="_viewIds"
          CustomViewDefinitions="_customViews"
          DefaultViewId="@(new Guid(AllContactsViewId))">
    <Buttons>
        <NavigateNewRecordGridButton OnClick="OnNewClick" />
        <NavigateOpenRecordGridButton OnClick="OnEditClick" />
    </Buttons>
</MainGrid>

@code {
    private async Task OnNewClick(NavigateGridButtonContext ctx)
    {
        ctx.Url = ctx.GridContext.SelectedView.TableName switch
        {
            "contact" => "/contacts/new",
            "account" => "/accounts/new",
            _ => throw new Exception("Unknown table"),
        };
    }

    private async Task OnEditClick(NavigateGridButtonContext ctx)
    {
        ctx.Url = ctx.GridContext.SelectedView.TableName switch
        {
            "contact" => "/contacts/edit?id={0}",
            "account" => "/accounts/edit?id={0}",
            _ => throw new Exception("Unknown table"),
        };
    }
}