RecordContext

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

Loading a Record

There are several ways to specify which record a RecordContext should load:

• Record — Pass a TableRecord object directly. Useful when you already have the record in memory or are creating a new record.

<RecordContext Record="@(new TableRecord { TableName = "contact" })">
    <TextEdit ColumnName="firstname" />
    <TextEdit ColumnName="lastname" />
</RecordContext>

• QueryParameterName and TableName — The context reads the record ID from a URL query parameter and retrieves the record from Dataverse automatically. If no ID is present, a new record is created.

<!-- URL: /my-page?id=00000000-0000-0000-0000-000000000001 -->
<RecordContext TableName="contact" QueryParameterName="id">
    <TextEdit ColumnName="firstname" />
    <TextEdit ColumnName="lastname" />
</RecordContext>

• RecordId and TableName — Specify the record ID directly as a parameter instead of reading it from the URL.

<RecordContext TableName="contact" RecordId="00000000-0000-0000-0000-000000000001">
    <TextEdit ColumnName="firstname" />
</RecordContext>

Record Loaded Event

Use the RecordLoaded callback to run logic after the record has been retrieved from Dataverse. This is useful for initializing dependent state or loading related data.

<RecordContext TableName="contact"
              QueryParameterName="id"
              RecordLoaded="OnRecordLoaded">
    <TextEdit ColumnName="firstname" />
</RecordContext>

@code {
    private async Task OnRecordLoaded(TableRecord record)
    {
        // Initialize dependent state or load related data
    }
}

Context Template

Instead of using ChildContent, you can use the ContextTemplate parameter to access the TableRecord object directly in your markup via a template variable.

<RecordContext TableName="contact" QueryParameterName="id">
    <ContextTemplate>
        <h2>Editing: @context["firstname"]</h2>
        <TextEdit ColumnName="firstname" />
        <TextEdit ColumnName="lastname" />
    </ContextTemplate>
</RecordContext>

Deleting a Record

Call DeleteAsync() to delete the current record. The user is prompted with a confirmation dialog before the delete is executed. Use the OnBeforeDelete callback to run custom logic or cancel the delete by setting CancelEventArgs.Cancel to true.

<RecordContext TableName="contact"
              QueryParameterName="id"
              OnBeforeDelete="OnBeforeDelete">
    <MenuBar>
        <DeleteContextButton />
    </MenuBar>
    <TextEdit ColumnName="firstname" />
</RecordContext>

@code {
    private async Task OnBeforeDelete(CancelEventArgs eventArgs)
    {
        // Optionally cancel the delete
        // eventArgs.Cancel = true;
    }
}

URL Navigation

When using QueryParameterName, the RecordContext automatically monitors URL changes. If the query parameter value changes while staying on the same page, the context reloads the new record without a full page navigation. After saving a newly created record, the URL is updated to include the new record's ID.