Getting Started with FM Dojo
FM Dojo is a FileMaker workbench: ask questions, add schema context, build in focused tools, automate repeatable work, and validate changes before they reach production. This guide is numbered so you can track where you are, but each section is useful on its own.
I want help with FileMaker work today
Start with AI Chat, Code, or a Snapshot. You can ask a question first, then add schema context when the answer needs your real tables, fields, scripts, or layouts.
Jump thereI want FM Dojo to understand my solution
Create a Project, add a Snapshot or server connection, then use that context across Chat, Code, Diagram, Canvas, FM Deploy, and Server Deploy.
Jump thereI want to manage FileMaker Server
Go to FMS Admin, add server access, review health, then layer in alerts, restore workflows, Server Pub/Sub, and deploy planning when you are ready.
Jump there01Orient yourself
Use this page as the map. You do not have to complete every step in order.
- Open the Dashboard when you want a tool grid and recent activity.
- Use Cmd+K, Ctrl+K, or / for global search when you already know the destination.
- Use the public User Guide when you need the full feature reference.
Open next
02Ask the first question
AI Chat is the fastest starting point when you want an answer, a plan, a script, a calculation, or a second opinion.
- Ask in plain English and include the FileMaker version or feature area when it matters.
- Paste a script, calculation, ExecuteSQL query, error, or layout idea directly into the conversation.
- When AI Chat needs real schema context, move to Snapshots or a Project instead of retyping table and field names.
Open next
03Create a Project when work should persist
Projects keep related FileMaker work together so context can travel between tools instead of living in one-off chats.
- Use a Project for a client file, product module, deployment, audit, or longer feature build.
- Attach schema context with Snapshots, server connections, Database Authorizations, or LiveConnect evidence as the work matures.
- Return to the Project when you need continuity across Chat, Code, Diagram, Canvas, and deployment review.
Open next
04Add schema context
Snapshots and live connections let FM Dojo reason from your actual FileMaker structure instead of generic examples.
- Upload a DDR/XML Snapshot when you want schema review, diffs, diagrams, or AI answers grounded in tables, fields, scripts, layouts, and relationships.
- Connect multiple files when a workflow spans related FileMaker files.
- Use LiveConnect or server access when you want current context without repeatedly exporting files.
Open next
05Build and edit in the right surface
Use the focused tool for the artifact you are changing, then bring the result back to FileMaker.
- Use Code for FileMaker calculations, scripts, SQL, JavaScript, JSON, YAML, validation, side-by-side comparison, and saved clips.
- Use Diagram when you need to understand or design relationships visually.
- Use Canvas when the output is layout structure or FileMaker-ready layout XML.
- Use SVG Designer for button icons and interface assets.
Open next
07Connect server operations when needed
FMS Admin is where server health, logs, databases, schedules, alerts, SSL, backups, and recovery work come together.
- Add server access only when you need live FileMaker Server visibility or administrative workflows.
- Review dashboard health before running restarts, commands, restores, or maintenance work.
- Use alerts and Server Pub/Sub when server events should notify people or trigger a Connector.
08Automate repeated work
Connectors helps you build automations from FileMaker events, schedules, webhooks, and app actions so repeatable work stops depending on manual steps.
- Start with a simple trigger and one action before adding branches or nested connectors.
- Use FileMaker triggers, schedules, webhooks, or Server Pub/Sub events depending on where the work begins.
- Keep credentials and database access in Database Authorizations instead of scattering them across automations.
09Validate before changes reach production
Use audits, diffs, preflight checks, and deployment history before treating AI output or schema changes as done.
- Run Snapshot audits when you need schema risk, cleanup, relationship, reference, or script safety checks.
- Use FM Deploy for data-preserving schema changes between FileMaker files.
- Use Server Deploy for moving FileMaker files between servers with run history, validation evidence, rollback context, and notifications.
Open next
10Keep learning and get help
FM Dojo includes docs, guided lessons, release notes, community support, and product help when you need the next level of detail.
How the tools fit together
Think in groups instead of memorizing every page name. Most real work uses one tool from two or three groups.
Answer and plan
You need direction, a first draft, a FileMaker explanation, or a guided route through a larger task.
Tools
AI Chat, Ask FM Dojo, User Guide
Context and understanding
You want answers and plans grounded in your actual FileMaker files, schema, relationships, scripts, and layouts.
Tools
Projects, Snapshots, LiveConnect, Diagram
Build and transform
You are editing calculations, scripts, SQL, layouts, icons, snippets, or FileMaker-ready XML.
Tools
Code, Canvas, SVG Designer, XML Tools
Operate and deploy
You are managing servers, automating FileMaker work, preparing production changes, or collecting run evidence.
Tools
FMS Admin, Connectors, Server Pub/Sub, FM Deploy, Server Deploy
Common first workflows
Use these recipes when you know the outcome but not the route.
Improve an existing FileMaker feature
- 1Create or open a Project
- 2Upload a Snapshot
- 3Ask Chat to review the goal
- 4Edit in Code, Diagram, or Canvas
- 5Run Snapshot audit or validation
- 6Deploy through the appropriate deploy path
Troubleshoot a server issue
- 1Open FMS Admin
- 2Review health and logs
- 3Ask Chat about the observed issue
- 4Use commands or maintenance flows only after reviewing impact
- 5Add an alert or Server Pub/Sub listener if it should be watched next time
Automate a repeatable FileMaker task
- 1Decide where the trigger starts
- 2Create or reuse Database Authorization
- 3Build the Connector
- 4Test with a safe record or event
- 5Add branches, nested connectors, or notifications only after the base path works
When you are unsure
Use the lightest useful next step. You can add more context later.
Need an answer?
Open AI Chat and ask. If the answer depends on your database, add a Snapshot or Project next.
Need a change?
Open a Project. Keep the work in one place and review the plan before editing or deploying.
Need live server work?
Open FMS Admin. Check health and active users before running commands, restores, or deployment workflows.