Member Junction
    Preparing search index...

    Event payload emitted when the user confirms a restore.

    The host component (typically record-form-container) is responsible for:

    1. Reloading the live record (concurrency safety),
    2. Calling record.SetRestoreContext(SourceChangeID, Reason),
    3. Calling record.Set(FieldName, Value) for each entry in FieldValues,
    4. Calling record.Save(),
    5. Calling record.ClearRestoreContext() after the save returns.

    The provider will write a new RecordChange row with Source='Restore', RestoredFromID = SourceChangeID, and RestoreReason = Reason — producing the auditable lineage chain.

    interface RestoreVersionEvent {
        ChangedAt: Date;
        ChangedByUser: string;
        FieldValues: { FieldName: string; Value: unknown }[];
        Reason: string | null;
        SourceChangeID: string;
    }
    Index

    Properties

    ChangedAt: Date

    When the historical change was made.

    ChangedByUser: string

    Display name / email of who made the historical change.

    FieldValues: { FieldName: string; Value: unknown }[]

    Selected field values, ready to pass to BaseEntity.Set().

    Reason: string | null

    Optional user-entered reason for the restore.

    SourceChangeID: string

    ID of the historical RecordChange row whose state is being restored.