Frequently asked questions

A collection of frequently asked questions about MFSQL Connector

What is MFSQL Connector

MFSQL Connector is a developer platform of tools and capabilities to connect M-Files with SQL Server bidirectionally without having to master the M-Files APIs. Introducing MFSQL Connector

Why use the Connector

The Connector liberates M-Files metadata to use the power of SQL to explore it, change it and link it with external applications and systems

What is the top 5 use cases

  1. Extract data from M-Files for reporting and analysis

  2. Exchange M-Files metadata with other systems

  3. Reorganize and reclassify metadata in bulk

  4. Remove objects and object versions

  5. Reprocess complex data to align it with M-Files properties and structure

Why use MFSQL Connector for reporting

The reporting functionality of the Connector does everything the reporting tool of standard M-Files does, plus more. Customers often replace the reporting tool with the Connector when the reporting tool no longer meet their needs.

  • Exploring the data and its relationships is simpler and exploring available data is much easier to do

  • The data table structures of the Connector is simpler to use and reduces the complexity and requirement to join multiple tables to obtain a simple extraction of data from M-Files

  • Changes in M-Files can be included in reports - near real time.

  • There is no need to replace the entire data set to update data from M-Files to SQL for reporting.

  • Multiple extracts of data is maintained in a single database, rather that a database for each exported dataset.

  • Combining the M-Files event log information for other metadata to create more meaningful reports

Learn more about it in Reporting

Why use MFSQL Connector for vault Archiving

The functionality of the Connector to export files and save them to a folder allows for you to pick the properties set as the folders (up to 3 levels deep) and either copy, mark as deleted or destroy the files in the vault.

Why use MFSQL Connector for integration

One of the core pillars of MFSQL Connector is the capability of using the tool to integrate between M-Files and any third party system using SQL as their backend.

This is particularly relevant when the connection is complex, must be flexible, and the business has skills with SQL capabilities.

Learn more about the it in the Integration whitepaper

What is the rules for licensing

  1. Each M-Files Server requires a separate MFSQL Connector license

  2. The license is issued for the specific M-Files Serial nr and for the subscription period (a year)

  3. The number of M-Files user licenses (named and concurrent) on the M-Files server determines the MFSQL licensing bracket (e.g. 1-49; 50 – 200 etc). Read only licenses are excluded in the count.

  4. The usage of specific functions and features in MFSQL Connector (as outlined in the functional overview) determines the module (e.g. data exchange, integration or database file connector)

  5. The number of vaults on the M-Files server is not restricted.

  6. Separate M-Files servers that is used for replication, backup or any other vaults, are not taken into account as long as no MFSQL Connector connection to the vaults on these separate servers is used.

  7. The number of users assigned to the vaults (irrespective if the vaults are using MFSQL Connector or not) are not relevant.

  8. The number of SQL servers connected to the M-Files Server is not restricted

  9. One MFSQL Connector license for a separate M-Files Server and serial nr, exclusively used for testing and prototyping, is included at no additional cost.

Is it compatible with M-Files Cloud

The M-Files Cloud vault can interact with MFSQL Connector database on premise or in another cloud. From the MFSQL database to M-Files is a HTTPS secure connection. Optionally, action SQL operations from M-Files using webservices.

What can the Connector do with the Metadata in M-Files

MFSQL Connector allows for working with M-Files metadata by executing SQL procedures and exploring the underlying tables in SQL. It provides full CRUD (Create, Read, Update and Delete) bi-directionally between an M-Files vault and the Connector Database. Metadata Management and data cleansing

Can the Connector remove redundant object versions from an object history

The connector allows for the removal of specific object versions from the object history in M-Files. spMFDeleteObjectVersionList

How to get support

To get support send an email to support and include the following:
  • screenshot of the error

  • details of the actual error from the MFlog table. Copy and past the result of the query below to your email to show the full text

SELECT TOP 5 ErrorMessage, CreateDate FROM MFlog ORDER BY logid desc

Can the connector change or update the display id of an object in M-Files

The column ‘’External_ID’’ in the class table represents the display_id of the object. This column can be updated from SQL to M-Files. This is particularly useful when a external system made changes to the unique identifyer of an object and these changes need to be update into M-Files.

What file operations can be performed

  • /blogs/import-files-into-m-files-from-explorer/index

  • /blogs/importing-files-from-a-database/index

  • spMFExportFiles

How to count to number of objects in the vault

Use spMFObjectTypeUpdateClassIndex to get all the object versions in the vault, and view the result with MFvwAuditSummary