- 0 comments
- 234 views
-
This page is a central repository for FileMaker AI initiatives and Agentic Development
Source of this is from this blog CadenceUX Blog
AI Initiatives
AI Initiatives
A Repository of FileMaker and AI
- 0 comments
- 222 views
- 0 comments
- 184 views
-
https://www.youtube.com/watch?v=7ArQ_T--BEY&t=2429s
Protect Your FileMaker Investment with ai2fm
https://ai2fm.com/protect-filemaker-investment.html
17 FileMaker Clipboard Bugs — verified, with reproducible test files
Published by ai2fm · companion to the v2.5 release · last updated 2026-07-28
During the R&D for ai2fm v2.5 we found, documented and reported to Claris International Inc. a set of 17 bugs in FileMaker’s clipboard serialisation. This page is the account of each one — but unlike a changelog, every claim here is backed by files you can download and reproduce yourself.
For each bug we ship a folder containing the FileMaker file itself plus real captures:
<Step>_<year>.fmp12 — the actual FileMaker file, one per version, so you can open the exact step we tested and copy it yourself.
<Step>_Source_<year>.xml — the exact clipboard FileMaker produced when we copied that step.
<Step>_Result_<year>.fmscript — what ai2fm made of that clipboard.
where a recovery exists, the corrected files that prove the fix round-trips.
Open the file, copy the same step in your own FileMaker, and you will get the same clipboard.
Download the test suite ⬇️ Bugs_Test_Suite.zip — 5.4 MB, every file referenced on this page
- 1 comment
- 256 views
-
- 0 comments
- 183 views
-
- 0 comments
- 185 views
-
Works with Claude Code, Cursor, Windsurf, Codex, Antigravity (Google), and any MCP-compatible AI tool.
- 0 comments
- 178 views
- 0 comments
- 196 views
-
Analyse a FileMaker solution in your browser
Nothing installed, nothing uploaded, works offline.
Clockwork Inspector (SaXML) Drop in a Save as XML export. Unreferenced fields tiered by confidence, broken references, script call tree, relationship graph drawn from the real TO geometry, layout wireframes, and a diff between two versions down to the calculation line. Every check is documented, so the findings are defensible in front of a client.
XML Scrubber (SaXML + others) Strips API keys, passwords and internal hostnames out of FileMaker XML before you hand it to an AI tool.
Reliable AI for FileMaker
AI is genuinely useful for FileMaker development, but only if it stops guessing. Left to its training data, a model invents functions that don't exist, and emits layout and schema XML that FileMaker rejects silently — no error, the object just never appears.
These are open tools and specifications that fix that: the knowledge an AI needs to generate FileMaker that actually works, and the tools to check what it produces. Much of it is reverse-engineering FileMaker's undocumented clipboard XML — the formats Claris has never published, where a wrong guess pastes silently and breaks. The rest is giving the model the vocabulary, reasoning and verification it otherwise lacks.
FileMaker Second Opinion A reasoning skill, not a knowledge file. It makes the model challenge its own first answer on exactly the problems where the common FileMaker solution works in a demo and fails silently in production, and it forces a proper read of Claris Help, Notes and platform sections included, before any behaviour claim is made. Built and refined against production work. New, and the piece the rest of this page stacks under.
FileMaker AI Vocabulary Every FileMaker 26 function and script step in ~7,000 tokens, so an AI stops inventing things that don't exist. The cheapest way to make any model better at FileMaker — no XML required.
Generation — paste-ready FileMaker XML
Script XML Skill (XMSS, XMSC, XMFN) The full script step ID dictionary, plus the hidden paste-handler rules that decide whether your XML survives the trip into FileMaker.
Layout XML Skill (XML2) All 18 layout object types mapped, every flag decoded, element order confirmed against native output. Verified across 45+ layouts in 10 production files.
Field, Table & Value List Definitions (XMFD, XMTB, XMVL) Field, table and value list definition XML — auto-enter, validation, storage, calculation options, and the three value list source arms — verified down to the individual option level.
- 0 comments
- 452 views
- 0 comments
- 211 views
- 0 comments
- 116 views
I'm in private aviation, running FileMaker in-house solutions for about 13 years. To stay on track with AI development I've built a few small tools. Eventually I decided to pack them into a native FileMaker plugin, so it's one tool instead.
The three biggest problems it solved for me:
I am in control of what the AI sees. Everything runs locally, no network calls during conversion, works offline. Nothing reaches an AI except what I paste there myself.
Accidental secret leaks. If the steps I'm copying contain something that looks like a password or API key, the copy stops and asks. One click replaces the values with placeholders. It's a heuristic scan, so a safety net, not a guarantee, but it has caught real leaks for me.
Read-proofing code before it goes back into FileMaker. Whatever the AI changed comes back as plain text I can actually read and check. The plugin also round-trips every conversion against itself before writing to the clipboard; a conversion that doesn't survive its own check refuses instead of pasting something corrupted.
Mechanics: select scripts as batches or single, or script steps, ⌘⇧C — the clipboard now carries the script as text, paste it anywhere (any editor, any AI, git). Copy the edited text, ⌘⇧V in the Script Workspace — it converts back and pastes as real scripts or steps.
For AI: there's a calc function that copies the text-format spec (it does not contain your context!), so an AI can write new scripts from scratch in that format too.
Beta: free, macOS 14+, FileMaker 2025/2026 (older versions untested). If it might be useful for you, sign up at https://fmscriptbridge.com and I'll reply with the plugin.
Windows version is in progress.
If something breaks or converts oddly, there is a bug report feature (you control what is reported)
I will be thankful for your feedback.
Victor
- 0 comments
- 36 views
-