Metadata Explorer
Metadata Explorer defines the schema context Genie uses for generation and analysis.
Global actions
Section titled “Global actions”| Label | Description |
|---|---|
| Expand | Toggle normal/expanded panel width. |
| Refresh | Pull latest schema from FileMaker. |
| Clear | Remove all selections. |
| Preview | Open selected metadata JSON in Viewer. |
| Close | Close the Metadata Explorer panel. |
Panel resizing and active table
Section titled “Panel resizing and active table”- You can drag the explorer edge to resize the panel.
- In Tables, one table can be marked as the active focus.
- When a table is active, the Fields section emphasizes fields from that table.
- This helps narrow prompts and reduce field ambiguity.
Schema sections
Section titled “Schema sections”- Tables
- Fields
- Layouts
- Scripts
- Custom Functions
Each section supports:
- Search
All/Nonebulk actions- Per-item checkbox selection
Select fields on a layout
Section titled “Select fields on a layout”In the Layouts section, each layout row includes a small Select fields on this layout button. Use it when a prompt depends on the fields that are actually available on a specific FileMaker layout.
When you click the button, Genie:
- selects the layout
- reads the fields available on that layout
- selects the matching fields in Fields
- keeps the selected table, layout, and field context together for prompts and
#autocomplete
This is useful for layout-aware CODE, QUERY, and DATA work where a table has many fields but only some are available or relevant on the target layout.
Metadata scope and autocomplete
Section titled “Metadata scope and autocomplete”The Metadata Explorer selection drives # autocomplete in the composer. If you type # and do not see the table, field, layout, script, or custom function you expected, check the current explorer selection first.
- Use Refresh after schema changes in FileMaker.
- Select the relevant metadata before sending prompts that depend on exact names.
- Use Preview to confirm what Genie will receive as schema context.
- Import custom functions when your prompt depends on project-specific calculation helpers.
If required metadata is missing, Genie may ask before generating CODE, QUERY, or DATA output. Advisory gaps can still produce a draft, but Genie should not silently invent unknown fields or functions.
Metadata preview
Section titled “Metadata preview”Use Preview to verify exactly what will be sent as schema context.
Custom Function import
Section titled “Custom Function import”Import custom functions so Genie can reason with your real function definitions.
Why import helps
Section titled “Why import helps”- Better parameter and return-value usage.
- Fewer placeholder calculations.
- Better reuse of existing logic.
Import workflow
Section titled “Import workflow”- Click Import in Custom Functions.
- Follow the dialog instructions in FileMaker.
- Select functions (
Cmd+Aor manual selection). - Return to Genie and confirm import.
Custom Functions are saved per project. Re-importing updates existing imported functions and keeps the project copy in sync.
See: Project Rules