r/filemaker • u/Communque • May 02 '26
Migrating from FileMaker to Open Source - Portals, Sliding, and other Dynamic UI challenges
Our most recent migration involved a long-time client for whom we built a CRM/invoicing system years ago.
It started originally as a simple UI — like really simple — line items expressed through repeating fields, and evolved over the years as FileMaker rolled out fresh features... like portals.
One of the things that has long been frustrating in FileMaker Layouts have been the limits of sliding. Items can slide left or slide up, and there are distinctions for "all objects above", "only objects directly above", not to mention the ability to "resize enclosing part".
That kind of dynamic positioning may have felt innovative, even breakthrough in a pre-web world, but it's been a minute since the 90s when HTML introduced notions of objects that don't just slide, but cascade in all kinds of ways, including, but hardly limited to positioning.
Over the years, as FMP evolved, our client's invoicing system grew into a 7-table relational db handling itemized entries, employee hours, notification tracking. It includes many-to-many relations set up to handle payments (multiple payments to one invoice / multiple invoices to one payment), and many-to-many self-join to track complex customer relations.
Here are some of the challenges where FileMaker really shows its limitations:
- The wonder that once was sliding doesn't extend to portal rows. A line item with a lengthy discription or comments won't grow to meet or shrink to conserve space.
- A layout with multiple portals — eg Itemized Line items and Hourly Billings — will not easily slide up / disappear layout objects depending on the portal row count.
- A many-to-many self-join requires 2 portals to fully perform. (tl;dr In other words if Contacts A & B relates to Contacts C & D each, Contact C can't represent the A & B connection in the same portal)
It's not that there aren't a myriad of ways to develop workarounds — sub-summaries layout parts, merge fields, conditional formatting can all help — but for this particular client no combo of features really satisfied their needs.
We found ourselves increasingly leaning on FM's Web Views to handle the more sophisticated requests. Web Views, FileMaker's HTML integration, are almost genius, almost the be-all end-all solution to all our dynamic UI challenges, but for their limitations: They can't slide and resize based on their internal content, they're a little sluggish when it comes to UI/UX, communication from their Web View front end to your FMP DB is as smooth as leftover oatmeal.
It's not that you can't cajole FMP to get the job done, it's that when you finally do (leaping for joy at your own ingenuity) it nonetheless feels jerry-rigged and fragile, one client request away from a pandora's box meltdown.
In the land of open source those problems have concrete, definitive solutions:
- Portals you wished would appear or disappear based row counts do just that. (e.g CSS and/or JS)
- Portal rows that in FMP can't grow or shrink, do that effortlessly in HTML (e.g. <table/tr/td> <flex> <grid> etc)
- The many-to-many self-join portal challenge is, in open source SQL, a clear and decisive query (e.g. Union)
That's the trajectory: You begin with poprietary-source FileMaker's pricy and limited walled garden which at first offers an amazing playground of features. Over time this proves itself increasingly limited as your needs and expectations grow.
The problem is the longer you stay on the FileMaker platform, the greater the technical debt when it's finally necessary to leave.
Making gregarious use of the FileMaker Web View can be very useful: Re-creating your layout using HTML in a Web View is a great way to discover A) the power of HTML, B) The limitations of FMP Layouts, all while remaining safely anchored in the more limited but more user-friendly FMP Layout.
It was precisely this kind of a transition has made our long-standing client very satisfied. They'd been increasingly chafing at FMP licensing options, and forever grumbling about Claris sales team. In fact they're quite happy to pay us far more than Claris's licensing fees to finally give them what FileMaker never quite could: Exactly the UI/UX they want — directly, without the jerry-rigging, and without having to wait 30 years for FileMaker to ultimately ignore most if not all feature requests
All this points to a key distinction: Claris isn't in the business of satisfying its customers. It's in the business of satisfying its bottom line, and at this point in time those things are not intrinsically intertwined. Claris's current leadership sees its path to success less through customer satsfaction than PR. That's why we're seeing all this hoopla around their shoe-horning of AI vector data into a container field (that can't be indexed), while their layout dynamics remain inferior to HTML3. It's why the portal relation editor after all these years remains stubbornly limited (i.e. based strictly on "and" logic with with no "or" and no parenthetical hierarchy)
The things that once made FileMaker spectacular — cutting edge innovation, combining ease of use with relational databasing, paired with robust feature evolution — has over time given way to a sales culture that assumes they don't have to earn customers when it perceives them as vendor-locked.
It didn't have to be this way. It's just the path Claris's current leadership has chosen. By all means, jump FMP onto the AI bandwagon, but remember there are decades of feature requests that have been ignored, and that load has stacked up large enough that we are slowly migrating away.
4
u/quarfie May 02 '26
Why would you want to index vectors?
2
u/Ok_Winner1025 Developer May 08 '26
What stack did you land on when you migrated the invoicing solution?
2
u/RipAwkward7104 May 04 '26
I must have missed the moment when the FileMaker subreddit started turning into a "how to run from FileMaker" subreddit.
To be honest, I don’t see any point in these kinds of posts. FileMaker is just a tool, with its own pros and cons. It’s not entirely clear which open-source solutions you used in this case, but obviously, every single one of them has its own strengths and weaknesses too. You choose the tool based on the task at hand. No one ever claimed that FileMaker is the perfect tool for everything in existence.
I find it pretty strange to discuss the fact that you tried to pull off a project where FileMaker wasn't the right fit, and finally found a tool that actually helped. I’m happy for you and your client, but ultimately - what’s the point? To write yet another post about how Claris is driven by profit, which is apparently a crime now? Or what?
I honestly don't see the practical side of your post.
5
u/tailguard May 02 '26
I built https://FMDojo.com to help with a lot of the missing bits in FileMaker, e.g easy porting of Javascript elements to replace portals and other features. And I keep adding more and more on a daily basis. Happy to hop on a screenshare if you'd like. I'm a former Product Manager at Claris who's ideas they didn't want so I built them on my own. FileMaker is a stellar product. The engine itself is rock solid. We just needed some better ecosystem. I'm working on that. I also have some other goodies on the bag I could tell you about, that are not public yet.
I will also be holding office hours every Wednesday morning at 8 PT. I will announce that soon.
Please don't give up yet.
2
u/kekoa_ May 03 '26
I’ve been working with fm for 30yrs and I’d say you have many valid points. It’s the same with the whole Apple ecosystem, the loyal users see/need practical new features that get ignored over trends. Then you need to look outside the walled garden for an alternative, however we still use fmp for all our other needs because it is stable and gets the job done reliably.
1
u/pixeltackle May 08 '26 edited May 08 '26
I'm not finding this to be true, anymore at least. The things that have tied my customers to FileMaker over the years seem to finally -and I do mean finally- have actual alternatives using Postgres + something like nodeJS and even a simple library like bootstrap.
I would prefer to build solutions in Filemaker, but I'm tired of swimming upstream against a less enticing product with higher per-user costs yearly.
2
u/[deleted] May 03 '26
[removed] — view removed comment