All News
You've heard the name in passing from your IT provider, or read that a neighboring company had "its own FileMaker" built to run its production. But what actually is it? Off-the-shelf software, like Excel? A programming language reserved for developers? An online service like so many others out there today?
The answer is a bit of all three, without being reducible to any of them. This guide is for executives, administrative managers, or project leads who have no IT background, but who need to understand what they're buying — or what's being proposed to them — before committing.
Having naming conventions is essential: they help you find your way around your own work over time, and let you share your code with colleagues without them having to rediscover everything from scratch. They also reflect the developer's personality, and already hint, in a way, at how future development will be carried out.
So here are the naming conventions and a few development tips that I want to share with you. Naming conventions, yes, but also a way of developing — principles I bundle together as the basic development practices we follow. They're not absolute truth. Their purpose is to share our way of doing things. You'll be able to adapt them to your own needs if you don't have any yet, or compare them with what you already have. "Oh, that's better than what I do." Or, "ugh, that's no good — I've tried that and it didn't work for me." Or, "cool, that's just like me."
Excel crashing, a shared spreadsheet nobody can find, off-the-shelf software that no longer fits your processes… If any of this sounds familiar, you're not alone. Most growing companies eventually run into the limits of "ready-to-use" tools. The question isn't whether these tools are bad, but whether they're still suited to your business, your scale, your processes.
A custom business application isn't a luxury reserved for large corporations. It's software designed specifically to reproduce, automate, and make reliable the way your company actually works — not the way a generalist vendor imagines every company should work. Here are five concrete signs it's time to seriously consider one.
JSON : Using the dot "." as a key element with FileMaker's JSON functions
In FileMaker's JSON function the dot "." is used as a delimiter to navigate between a JSON structure's elements.
But how to use the dot "." inside a key without having FileMaker interprates it as a delimiter ?
Ex :{"a.b":1}

