(+) M-Files Importer - konzultační wiki - partneři - M-Files komunita

The page is only accessible by M-Files partners. If you are an end customer, you can request M-Files Importer via your representative.

M-Files Importer user guide: empower.m-files.com/.../mfiles-ka-314307

Would you consider making Importer public like you did with Property Calculator? I saw multiple similar requests over the time on the forum and I think this is a common task..

We recently had a similar task: creating a new object and class in M-Files, and subsequently importing several thousand entries into M-Files (starting from an SQL database). For this purpose, we used the self-hosted freeware version of n8n. We also use the same tool to synchronize our ERP systems with M-Files as sheduled tasks. (api access to M-Files: using custom M-Files nodes instead of http requests...)

We actually got our hands on an import tool, it is very tough to use but it does the job. Then we are writing VB Scripts on top in the different Workflow states that executes the needed changes. Something else we are concidering is using Event Handlers to modify our objects in case of needs, they are again tough for use but Gemini Pro writes pretty good scripts, not sure about the compute costs of these event handlers when all of them are turned on tho....

Looks cool, would be nice to get a look behind the scenes ;)

Nothing extraordinary behind it—we automatically prepare the data that comes from our ERP (or also new objects that need to be newly created), and transfer everything via the API into M-Files.

For automation, we use n8n because it's self-hosted and free even for enterprise use, standardized, and doesn't make you dependent on the expertise of a single programmer who creates individual solutions.

docs.n8n.io/.../

The M-Files nodes in n8n, made by a software vendor (they sell the nodes for little money), generate and send HTTP GET, POST (etc.) requests using given parameters. We also read data files/metadata/WF state out of M-Files, process, enrich and edit it, then update it back in M-Files. Thus, building even very complex workflows with data prep takes hours, not days/weeks.
Additionally, only basic technical knowledge is required, no programmer necessary.

Nothing extraordinary behind it—we automatically prepare the data that comes from our ERP (or also new objects that need to be newly created), and transfer everything via the API into M-Files.

For automation, we use n8n because it's self-hosted and free even for enterprise use, standardized, and doesn't make you dependent on the expertise of a single programmer who creates individual solutions.

docs.n8n.io/.../

The M-Files nodes in n8n, made by a software vendor (they sell the nodes for little money), generate and send HTTP GET, POST (etc.) requests using given parameters. We also read data files/metadata/WF state out of M-Files, process, enrich and edit it, then update it back in M-Files. Thus, building even very complex workflows with data prep takes hours, not days/weeks.
Additionally, only basic technical knowledge is required, no programmer necessary.