Documentation
DownloadPricingRelease Notes
English
English
  • Introduction
    • Welcome to Devin 👋
    • DevOps for Claris FileMaker
    • Why Devin When You Have Otto?
  • Features
    • Version Control
      • Advanced Version Control
    • Regression Testing
    • Deployments
      • Default Environments
      • Workflows
      • Under the Hood
    • Server & File Monitoring
  • Setup & Maintenance
    • Prerequisites
      • System Requirements
      • Network Considerations
    • Installation
      • Install Devin App
      • Install Devin Server
        • Install Devin on Your Own Server
        • Devin through a Hosting Provider
        • Upgrading from 1.0 Beta
  • Updates
    • Update Devin App
    • Update Devin Server
      • In-App Update Guide
      • Manual Update Guide
  • Uninstallation
    • Uninstall Devin App
    • Uninstall Devin Server
  • Server Mangement
    • Starting, Stopping and Restarting Devin Server
  • Guides
    • Getting Started
      • Create an Account
      • Connect to Development Server
    • Projects
      • Create a Project
      • Delete a Project
    • Modules
      • Add a Module
      • Branch a Module
      • Edit a Module
      • Delete a Module
    • Deployment Environments
      • Connect a Deployment
      • Update a Deployment
      • Disconnect Deployment
    • Branches
      • Create a Branch
      • Delete a File from a Branch
      • Delete a Branch
    • Versions
      • Save a Version
      • Compare Versions
      • Release a Version
      • Delete a Version
    • Tests
      • Load Test Scripts
      • Run Test Scripts
    • Releases
      • Create a Release
      • Deploy a Release
    • Servers
      • Add a Server
      • Change Development Server
      • Remove a Server
    • Team
      • Add Team Member
      • Remove Team Member
      • Manage Subscription
  • Support
    • Known Issues
    • Feedback
    • Release Notes
  • Legal
    • Privacy Policy
    • Terms of Service
Powered by GitBook
On this page
  • Overview
  • Guide
  • What Changes Are Tracked?
  • Hardware Requirements
  • Current Limitations and Known Issues
  • Empty XML Catalogues
  • Analysis Performance: Linux vs. Windows
  • System Locale and Version Type Behavior

Was this helpful?

  1. Guides
  2. Versions

Compare Versions

Track changes with the built-in XML Analysis API

PreviousSave a VersionNextRelease a Version

Last updated 20 days ago

Was this helpful?

Overview

The Compare Versions feature provides FileMaker developers with a powerful way to track changes in their FileMaker solution files. By comparing the Active Branch File with the latest saved version on the same branch, this tool highlights changes in a clear, summarized format. Detailed code diffs for Scripts and Custom Functions are currently supported, with broader change tracking in development.

Guide

1

Select Branch File

In the Branches view, select a file from the left branch file list.

2

Highlight the Active File Version

In the Version List, click the Active File Version.

3

Run Analysis

Manually: In the right sidebar, click the Run Analysis or refresh button. Automatically: Automatic change tracking can be enabled in Project Settings -> Versions.

4

Browse Changes

In the right sidebar, browse between different catagories and discover detailed code changes of Scripts and Custom Functions.

This video shows how the Devin App can track changes made to a development file:

What Changes Are Tracked?

This table shows what is currently tracked and displayed.

Category
Level
XML Catalogues

Code

Detailed

Line-by-line code diffs of Scripts and Custom Functions

Database

Summary

Names of Tables, Table Occurrences and Relationships

Layouts

Summary

Name of Layouts

Security

Summary

Names of Privileges Sets and Extended Privileges

Other

Summary

Names of Value Lists, Custom Menus, Custom Menu Sets and Themes

Hardware Requirements

The Compare Versions feature is exclusive to Development Server installations and requires significant memory resources for optimal performance:

  • Solo Developers: 8GB of memory.

  • Teams with Concurrent Development: At least 16GB of memory.

Built-in safeguards prevent memory overload, but enabling auto-tracking for teams with heavy activity may demand higher server capacity.

Current Limitations and Known Issues

In Devin 1.3.0, comparisons are limited to the Active Branch File versus the latest saved version on the same branch. This is currently a UI limitation and will be expanded in a future release to support comparing any version across any branch.

While powerful, this feature has a few current limitations and best practices to ensure it works correctly. If the App Sidebar shows an Analysis Error, it may be due to one of the following reasons.

This feature is actively being improved, and upcoming releases will eliminate the need to consider backup type when analyzing XML changes. Using a non-recommended backup type only affects XML analysis results — all other functionality remains unaffected.

Empty XML Catalogues

Comparisons might fail if either the Active Branch File or the Reference File it's compared to has empty XML catalogues, such as if the file has no Scripts, Custom Functions, Custom Menu Sets etc. Therefore, this feature works best with existing fmp12 files since new files by default has empty XML catalogues.

Discovering error logs such as An error occurred: 'custom_menu_sets_xml' or Error running operation: 'custom_menu_sets_xml' in the {opt/Program Files}/Devin/Logs/service.log file indicates that no Custom Menu Sets exist in the file. To resolve temporarilly, create an empty Custom Menu Set, or equivalent, for other XML catalogues.

Analysis Performance: Linux vs. Windows

This feature is compute-intensive, both in its core analysis logic and through concurrent use of several FileMaker CLI tools. Performance is typically 5–10 times faster on Linux servers compared to Windows Server.

System Locale and Version Type Behavior

The accuracy of XML change detection in Devin Server is affected by both the system locale settings, field storage options and the type of FileMaker backup used. If the system locale differs between FileMaker Pro and FileMaker Server, or if fields use a default storage language that doesn’t match the server’s configuration, false table changes may be detected. Depending on the server platform, either Clone or Full Backup versions may be more reliable. Using the non-recommended backup type may result in incorrect change detections, particularly in tables and scripts involving language or decimal formatting.

Platform
Recommended Version Type
May Detect Incorrect Changes

Windows Server

Clone

Full Backup

Linux

Full Backup

Clone

Track changes made to a development file