MainContext

Here is an example that demonstrates the use of a MainContext component.

Child Components

A MainContext can contain any combination of the following child components:

• RecordContext — Wraps a single Dataverse record for editing.
• SubGrid — Displays and manages a collection of related records.
• ManyToManyLookupEditor — Manages many-to-many relationships.

<MainContext>
    <RecordContext Record="@_contact">
        <TextEdit ColumnName="firstname" />
        <TextEdit ColumnName="lastname" />
    </RecordContext>

    <RecordContext Record="@_account">
        <TextEdit ColumnName="name" />
    </RecordContext>
</MainContext>

Saving

Include a SaveContextButton inside a MenuBar to allow users to persist changes. When the save button is clicked, all dirty records across all child components are saved in a single transactional request to Dataverse. If any record fails to save, the entire transaction rolls back and no changes are persisted.

<MainContext>
    <MenuBar>
        <SaveContextButton />
        <RefreshContextButton />
    </MenuBar>

    <RecordContext Record="@_contact">
        <TextEdit ColumnName="firstname" />
    </RecordContext>

    <RecordContext Record="@_account">
        <TextEdit ColumnName="name" />
    </RecordContext>
</MainContext>

Refreshing

Include a RefreshContextButton to allow users to discard unsaved changes and reload the records from Dataverse. If there are unsaved changes, the user is prompted with a confirmation dialog before the refresh is performed.

Validation

By default, the MainContext validates all child components before saving. Set ForceSuccessfulValidationBeforeSave to false to disable this behavior.

<MainContext ForceSuccessfulValidationBeforeSave="false">
    <MenuBar>
        <SaveContextButton />
    </MenuBar>

    <RecordContext Record="@_record">
        <TextEdit ColumnName="name" />
    </RecordContext>
</MainContext>

Dirty State Tracking

The MainContext automatically tracks whether any child component has unsaved changes via the IsDirty property. If a user attempts to navigate away from the page while there are unsaved changes, a confirmation dialog is displayed. Set DisableUnsavedChangesWarning to true to suppress this dialog for navigation changes. The warning is always shown when refreshing, regardless of this setting.

<MainContext DisableUnsavedChangesWarning="true">
    <MenuBar>
        <SaveContextButton />
        <RefreshContextButton />
    </MenuBar>

    <RecordContext Record="@_record">
        <TextEdit ColumnName="name" />
    </RecordContext>
</MainContext>

Intercepting Save

Use the OnBeforeSave callback to run custom logic before the save operation. Set CancelEventArgs.Cancel to true to prevent the save from proceeding.

<MainContext OnBeforeSave="OnBeforeSave">
    <MenuBar>
        <SaveContextButton />
    </MenuBar>

    <RecordContext Record="@_record">
        <TextEdit ColumnName="name" />
    </RecordContext>
</MainContext>

@code {
    private async Task OnBeforeSave(CancelEventArgs eventArgs)
    {
        // Run custom validation or logic
        // Cancel the save if needed:
        // eventArgs.Cancel = true;
    }
}