// blog

From FileMaker to Your Own Web App: Layouts, Scripts and Container Fields

When a FileMaker solution becomes a web app, its layouts and portals become web screens with the same fields, its scripts and calculation fields become rules in code with results compared against FileMaker, its tables and relationships move to PostgreSQL, and files in container fields move with their records into file storage. Everyone works in a browser on any device.

Last updated 1 min read

A table: FileMaker layouts become web screens, scripts become written rules, container files are kept

FileMaker is how many departments built their own system without waiting for IT. Some of those solutions grew into the thing the business runs on, and outgrew the person who built them. Here’s what moving one to your own web app involves.

Layouts and scripts

Layouts and portals become web screens with the same fields in the same order. Scripts and script triggers are where the rules are: each one is written down as a plain sentence, checked by the people who use it, and built once on the server.

Calculations

Calculation and summary fields become rules in code. Their results are compared with FileMaker’s on your own records before anyone switches, so a total that was right stays right.

Data and files

Tables and relationships move to PostgreSQL, with the records counted and checked. Files and pictures in container fields move with their records into file storage.

For your people

A web app works in any browser, on computers, tablets and phones, each person with their own sign-in. It also connects to other systems through an API.

See how a FileMaker solution becomes a web app. The first call is free.