The Data Separation Model

Beginner

Separate your UI file from your data file to simplify deployments, protect data, and enable schema-level security.

What you'll learn

  • What the data separation model is and why it matters for security
  • How to implement data separation with external data sources
  • Securing the data file against direct access
  • User authentication in a separated solution

The data separation model splits a FileMaker solution into two files: a UI file (layouts, scripts, relationships graph on table occurrences) and a data file (tables, fields, actual records). Users open the UI file; it connects to the data file via external data source. This has significant security implications: the data file can be completely locked down, and you can deploy UI updates without touching the data.

1/4
1

Architecture overview

UI file: contains layouts, scripts, value lists, table occurrences pointing to the data file's tables, and all user accounts. Data file: contains the actual tables, fields, and records -- no layouts, no user accounts. Users never open the data file directly; the UI file handles everything.

Least Privilege Design PrinciplesCredential Storage in FileMaker Solutions

Sign in to track your progress and pick up where you left off.

Sign in to FM Dojo