The M-Files Importer and the M-Files Connector for Network Folders may be enough for many import/export projects. However, using MFSQL Connector in conjunction with these tools can greatly lower the time and cost of complex projects while providing greater functionality.
Here are five reasons you should use MFSQL Connector:
- You want to speed the development cycle by using pre-built functions and capabilities
- You have large volumes of files to import
- Your file import require requires advanced data manipulation and alignment before or during the importing process
- Importing related data into an object as text, rather than valuelists or objects reduces the effectiveness of views in M-Files
- You already use Microsoft SQL Server databases and want to extend that use with M-Files data
Eliminate Custom Coding for Large Volume Data Manipulation
There are many examples of M-Files import and export projects where MFSQL Connector saves the time and cost of custom development. Some examples of data manipulation that can be done without custom coding include:
- Manage import of large volumes of files using batch processing
- Export files from one object type and import file to another object type
- Import files from database Blobs
- Import files from explorer with a match to the external system data structures
- Assemble and validate import data from various sources and match it with associated files, ready for import
- Export files to folder structure for permanent records
Let’s look at three real-world examples of these projects.
Importing Large Data Volumes
One client needed to import 6 million files from an external source into M-Files. To do this, they needed to analyze the folder, align the files with external source data, assess what needed to be imported and then prepare the data for the importing tool.
All of this was completed using MFSQL Connector to update tables using a batch mode. The updates were performed in smaller batches to improve throughput and reduce the impact of failures.
Moving Files to a New Object Type
MFSQL Connector can be used to move files to a new object type. In one situation, data files were originally saved as a non-document object type. However, the company needed to change the files to a document type to implement a PDF Processor. Using the special tools already available in MFSQL Connector, the company was able to make this exchange without a major development project.
Creating Dependent Objects on File Import
In another example where complex data manipulation was required, MFSQL was used to create dependent objects on file import to M-Files. Originally, the file import properties were related to other objects. These objects had to be created in the right order to ensure the document file object was correctly attached to all the objects.
Getting Started with MFSQL Connector for M-Files Import and Export Projects
There are two related MFSQL Connector Modules that are used for these types of projects:
- MFSQL Data Exchange and Reporting Connector to move your valuable business information in and out of M-Files.
- MFSQL Integration Connector to integrate and synchronize information from other business systems with M-Files.
If you have any questions about whether MFSQL Connector is a good fit for your M-Files import/export project, or which modules you need, please contact us. Or are you ready to start your project? Then download MFSQL Connector and learn more here: