Is possible to hide elements of course, but not to adapt the behavior for the rest of the elements. When a layout (page) needs to have a dynamic interface, which means conditionals for show/hide elements and adapt the rest of the elements, you just can't. You only can build scripts and crazy relations as workarounds to simulate a kind of constraint on the layouts, but that is not efficient at all for developing and you reach the limitation in the UI soon.įilemaker a decade ago was like a mule to plow the field in the 18th century, powerful and efficient, and nowadays it is still basically the same mule, just that the ecosystem possibilities and necessities changed.Ī) UI: the interface engine is completely outdated for a modern app, is not that you can't build beautiful UI, you can, as far it does not require real responsiveness and conditionals. If you have 40k records in a table, you cannot easily allow in a page, search or element just to show a part of those records.

There are privacy settings for the database of course, but the problem is that when building the UI you cannot make lists, search, and in short, any access to the records, to be really constrained by different criteria. Also the data constrain is a problem when you are building a complex app that requires either internal or external users, to access different data in a clean and easy way. But as the world is changing to web and dynamic UI, Filemaker has not made any step on this, and is getting completely outdated. It was really great few years ago, powerful and clean for database, easy enough to build the interface. Great for database and scripts, a dinosaur for a modern app with complex data relation

What is filemaker pro