Connector Content

• Assemblies
• Metadata Structure Tables
• Class tables
  • Class Table Columns
  • Class tables and their columns
  • MF ad hoc columns
  • Non‑Connector columns
  • Special columns
  • Default columns
  • Process_id values
  • Indexes on class tables
  • Object change history
  • Object Versions
• Utility Tables
  • MFDataType
  • MFDeploymentDetail
  • MFSettings
  • MFProcess table
• Logging Tables
  • Class Record Updates
  • Procedure Processing logs
  • Error logs
• Procedures and Functions
  • spMFCreateObjectInternal
  • Parameters
  • CLR and internal procedures
  • Naming Convention prefixes
  • Custom changes
  • Procedures and functions for applications
• M-Files Installation
  • Components
  • Availability
• Context Menu
  • Context Menu Procedures
  • Formatting result message for UI
• Supporting Applications
  • Custom tables, views, procedures and functions
  • Content
• MFSQL Connector Operations
  • Scope
  • Setup operations
  • Metadata structure operations
  • Metadata alignment
  • Class object operations
  • Monitoring, analytics, and exploration
  • Processing activity

The Connector components supplied as part of the deployment package include:

• Assemblies — proprietary assemblies (.dll) that enable interaction between M‑Files and SQL. They wrap the standard M‑Files APIs into classes that allow data to be extracted from M‑Files into SQL tables and updated back to M‑Files from SQL.

• Metadata Structure Tables — tables containing vault metadata, settings, and transaction logging data. Connector tables are prefixed with MF to distinguish them from non‑Connector tables. Metadata tables capture the structure of M‑Files (e.g., classes, properties, value lists, workflows). Related tables include ObjectTypes, Classes, Properties, ClassProperty, ValueLists, ValueListItems, Workflows, WorkflowStates, UserAccounts, and LoginAccounts.

• Utility Tables — supporting tables: DataTypes, Settings, Process, DeploymentDetail.

• Logging Tables — processing logs: MFLog, UpdateHistory, ProcessLog.

• Class tables — tables representing the data in the vault (e.g., Customers, Contacts). Class tables are created only for classes used by the application.

• Procedures and Functions — T‑SQL procedures and functions that operate on the tables and invoke the assemblies.

• Context Menu — controls user interactions with SQL from within M‑Files.

• Supporting Applications — utilities and sample files as add‑ons to the product.

• M-Files Installation — steps to install components in the vault, including the content package, vault applications, and UI extensibility applications.