FileMaker Finally Has Version Control
Review schema changes before they ship, see the full history of every object, and turn any solution into documentation that stays current. Here is how FM Dojo brings real version control to FileMaker.
For thirty years, changing a FileMaker solution has meant trusting your memory. You open the file, adjust a field, rewrite a calculation, add a script step, and hope you remembered everything you touched. There is no diff to read, no review to request, and no record of who changed what. When the original developer moves on, the knowledge often leaves with them.
FM Dojo changes that. You can now review schema changes the way software teams review code, see the complete history of every object, and generate documentation that keeps itself current — all from the snapshots you already capture.
See exactly what changed, in plain language
Compare any two versions of your solution and read the changes in plain English instead of raw export data. A field whose type changed from Number to Text says so. A relationship that gained a match criterion says so. A script that gained or lost steps says so. Renames read as renames, not as a delete and an add.
This is the difference between "something in this table changed" and "the Age field changed from Number to Text, which will affect sorting." The second one you can actually act on.
Review changes before they ship
Open a review on a set of changes and treat it like a pull request. Comment on individual changes, ask a question, and approve or request changes. When the review is approved, export a sign-off packet as a PDF that a reviewer or a client can put their name on.
For teams, reviews are visible to everyone on the team, so a change can be proposed by one developer and approved by another — with a record of the decision.
A history for every object
Every table, field, script, relationship, value list, and custom function now has a timeline across your versions. You can see when an object was added, when it changed, what specifically changed, and when it was removed — so "who changed this, and when?" finally has an answer.
Documentation that keeps itself current
Point FM Dojo at a solution and get clear, readable documentation generated from the real schema: the data model, every relationship described in plain sentences, the script inventory, value lists, and custom functions. Add an optional plain-language overview that explains how the solution works, then download the whole thing as Markdown or a PDF.
Because it is generated from the live schema each time, the documentation never drifts out of date the way a hand-written document does. The knowledge stays with the business, not in one person's head.
Try it
If you keep snapshots of your solution in FM Dojo, the compare view, reviews, history, and documentation are ready for you now. If you are new, you can see a sample of the generated documentation for an example solution and decide for yourself.
This is the operational layer FileMaker has been missing — and it is just getting started.