Skip to content
Genie logo Genie logo Genie - AI Assistant for FileMaker

DATA Mode

DATA mode is the execution workflow for write-impact operations in Genie.

What DATA is for

Section titled “What DATA is for”
  • Execute approved data updates.
  • Run schema-impact operations with explicit confirmation.
  • Handle multi-step migration requests with stepwise review and execution.

How Genie decides between single SQL and migration plan

Section titled “How Genie decides between single SQL and migration plan”

Genie routes your request to one of two execution paths:

  • Single-statement DATA execution for focused one-step operations.
  • Migration plan for migration-like or clearly multi-step requests (for example, chained operations such as add, backfill, then cleanup).

End-to-end workflows

Section titled “End-to-end workflows”
  1. Switch to DATA mode and accept the warning.
  2. Send a precise request.
  3. Follow either single-statement confirmation or migration step cards.
  4. Confirm, cancel, retry, skip, or abort based on outcome.
  5. Validate results before continuing.

Preflight clarification

Section titled “Preflight clarification”

Preflight is an agentic process that is now always enabled for DATA requests to ensure your intent is clear and schema-aware before execution.

  • Automatic: Preflight runs by default for every DATA prompt.
  • Clarification: If the AI detects ambiguity or requires more schema context, it will ask short questions.
  • Budget: You can control the maximum number of clarification questions in Settings > Clarification Budget > Preflight Questions.

Mode-entry warning and activation

Section titled “Mode-entry warning and activation”

DataModeWarning_2.png

WarningDataMode.png

Workflow A: Single-statement DATA execution

Section titled “Workflow A: Single-statement DATA execution”
  1. Genie returns a final SQL block with action links.
  2. Review SQL and intent.
  3. Click Confirm (or Confirm Full Table Change when required) to execute, or Cancel to stop.
  4. If needed, type the exact confirmation phrase shown in chat instead of using the button:
    • CONFIRM CHANGE for standard staged execution
    • CONFIRM FULL TABLE CHANGE for full-table or destructive execution
  5. Genie returns success, warning, or failure status.

PromptForConfirmation.png

ConfirmedDataMode.png

Workflow B: Migration plan (multi-step requests)

Section titled “Workflow B: Migration plan (multi-step requests)”

In migration flow, Genie returns a plan before execution:

  • A summary such as “Migration plan ready (N steps)”.
  • Optional full-plan review details for all steps.
  • A current step card with SQL preview and plan actions.
  • The current action row uses Execute Step-by-Step, Execute All, and Abort Plan.

DataMigQuickView_2.png

If you choose Execute All, Genie asks for explicit confirmation before sequential execution.

WarningExecuteAll.png

After execution, Genie reports per-step progress and final completion.

MigrationCompleteRefresh.png

Step actions and what each does

Section titled “Step actions and what each does”
  • Execute Step-by-Step: runs the migration one step at a time so you can review each staged action before continuing.
  • Execute All: runs remaining migration steps sequentially after explicit confirmation.
  • Abort Plan: stops the active migration plan.
  • Confirm: executes a staged SQL action. You can also type CONFIRM CHANGE.
  • Confirm Full Table Change: required exact confirmation for full-table UPDATE, TRUNCATE, DROP, or similar high-impact operations. You can also type CONFIRM FULL TABLE CHANGE.
  • Cancel: does not execute staged SQL and returns to controlled review flow.

Failure and recovery actions

Section titled “Failure and recovery actions”

If a migration step fails or is blocked, Genie can present recovery controls:

  • Retry Step: re-stage and retry the current failed step.
  • Skip Step: mark the current step as skipped and continue to the next step.
  • Abort Plan: stop the plan when continuation is unsafe.

When you skip a destructive step, Genie warns that the migration may become inconsistent.

Deterministic safety checks you may see

Section titled “Deterministic safety checks you may see”

Before execution, Genie applies deterministic checks and may block execution:

  • Full-table protection for UPDATE or DELETE without scoped intent.
  • Placeholder/parameter mismatch detection.
  • DATA validation blocks (shown as [DATA Validation] messages).
  • Unsupported SQL-shape blocking for incompatible statements.
  • CREATE INDEX blocking. Genie does not run CREATE INDEX in DATA mode because FileMaker manages indexing through field and storage settings.

The warning block and confirmation controls are shown inline in chat for high-impact SQL.

Fullwarnings.png

Best practices for safe execution

Section titled “Best practices for safe execution”
  • Keep prompts specific (table, fields, filter scope, intended impact).
  • Validate complex targeting in QUERY before DATA execution.
  • Review all migration steps before using Execute All.
  • If you need to change indexing behavior, use FileMaker field/storage options instead of DATA-mode SQL.
  • Treat destructive warnings as mandatory review points.

Recovery guidance

Section titled “Recovery guidance”
  • If confirmation text does not match intent, cancel and restage.
  • If a step is halted, use Retry Step, Skip Step, or Abort Plan based on risk.
  • If Genie blocks CREATE INDEX, move that change to FileMaker schema configuration instead of retrying in DATA mode.
  • If blocked by validation, revise scope/SQL intent and rerun.
  • If plan state is stale, start a new DATA request and regenerate plan.
Section titled “Related pages”