Connector for M-Files in processes

1. User switch action

Since no interactive user authentication to third-party systems is possible in processes, logging in to M-Files must occur before M-Files actions can be initiated. For timer-controlled processes, the user can be defined directly in the timer properties. Another option is the User switch action. This makes it possible to switch to the M-Files user from within a process.

2. Metadata synchronization

In contrast to files, the metadata of a document saved to M-Files via Intrexx is saved to the Intrexx data group fields. If metadata for a document is changed directly in M-Files, it cannot be automatically synchronized in Intrexx without performing some additional steps. For this reason, Intrexx automatically refreshes the metadata for an M-Files object as soon as the record is opened on a view or edit page. To save the current metadata in Intrexx as well, the user must then click on the Save button. This procedure can also be automated with an Intrexx process, which enables the metadata for an Intrexx data group to be synchronized with the objects in M-Files in regular intervals. To do so, create a new process and create a new timer event.

In the timer configuration, select the M-Files data group on the Data group tab and define a filter if needed. Next, select a user that will have its login details saved to the M-Files configuration on the Select user tab. Now add a new Data group action to the Timer event handler and select "Update record" on the General tab. Select the same data group as in the timer for the target data group, then select both ID fields as the Simple filter. In the next step, Field assignment, you can now assign the fields from the source data group to the target data group, for which the M-Files metadata will be read again and saved. When doing this, please note that the file fields cannot be synchronized here, since otherwise a new version would be created in M-Files. After closing the dialog, the process can be saved and run. By reading the records from the source data group, the metadata is read again from M-Files, then saved to the assigned data fields in Intrexx again.

3. File transfer between Intrexx and M-Files

Usually, files and documents are only saved physically to the M-Files server, then loaded by Intrexx at runtime when a user accesses an M-Files file in the portal. In some cases, it can also be useful to transfer files from M-Files to Intrexx or to copy existing files from Intrexx portals to M-Files. Additionally, in the data group actions, file fields can be assigned between Intrexx and M-Files data groups. If an M-Files data group is read from and written to an Intrexx data group, the files are copied from M-Files to the Intrexx portal server. In reverse, files can be copied from Intrexx applications to M-Files by reading from an Intrexx data group and writing to an M-Files data group. By using filters on the source data group, you can define which records (and therefore files) should be transferred to the corresponding target system. The following example makes clear how to transfer files from Intrexx to M-Files:

First, the records are read from an Intrexx data group timer-controlled. Next, a user switch action is used to log on to the M-Files server. Afterwards, the files and metadata are transferred from the Intrexx data group fields to M-Files using an M-Files data group action.

More information

Connector for M-Files
Consume M-Files data
M-Files in applications
Export / Import
Troubleshooting