This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

External sources Integration-Cloud Server

Former Member
Former Member
Hello guys, i have a question, our client have a cloud deployment, and they need to make an integration between M-Files and a HR system. Basically, they want to send files from the RH system to a folder in a web application like dropbox or google drive (no problems doing that) or maybe Azure Files. Once the documents are there, these files are required to be monitored by M-Files and imported with the respective metadata. I don't know if this is possible on cloud deployment, we can do it if we have installed M-Files in a local server (like our own machine), so we can put in the source path in external sources connections the dropbox, google drive or one drive folder as is showed in the attach.

If it is not possible to do it via cloud, do we have another option to monitor files sent by HR system to somewhere in the cloud and import it automatically like we can do it with a local server? Is possible maybe an integration like Outlook with M-Files? I really don't know if we have a custom support for this cases of integration.
15950.zip
Parents
  • Former Member
    Former Member

    Regarding the use of external repository connectors vs. external file sources in general, the first thing you should think in these cases is whether these files need to be stored in the M-Files vault or stay on the network drive (or other repository). External repository connectors such as the Network Folder Connector let you access files in their original location but they do not yet allow you to import the file data to M-Files. With external file sources you usually import the files to the vault and remove them from the original location after importing.

    On M-Files Cloud the use of external file sources is problematic since the cloud server cannot connect to the on-premises network shares without VPN. That's why in most cases we recommend using M-Files Importer instead like you already mentioned, it works the same with both on-premises and cloud vaults.

    I believe you are our reseller - there is some related information in the M-Files Cloud FAQ in Partner Portal.


    Excellent! Yes, we are the reseller and we'll work with importer because we need to auto populate metadata as well. I mean, external file source is easier to configure (on-premise case), but importer works as well. Now i'm sure about the next step, thanks!
Reply
  • Former Member
    Former Member

    Regarding the use of external repository connectors vs. external file sources in general, the first thing you should think in these cases is whether these files need to be stored in the M-Files vault or stay on the network drive (or other repository). External repository connectors such as the Network Folder Connector let you access files in their original location but they do not yet allow you to import the file data to M-Files. With external file sources you usually import the files to the vault and remove them from the original location after importing.

    On M-Files Cloud the use of external file sources is problematic since the cloud server cannot connect to the on-premises network shares without VPN. That's why in most cases we recommend using M-Files Importer instead like you already mentioned, it works the same with both on-premises and cloud vaults.

    I believe you are our reseller - there is some related information in the M-Files Cloud FAQ in Partner Portal.


    Excellent! Yes, we are the reseller and we'll work with importer because we need to auto populate metadata as well. I mean, external file source is easier to configure (on-premise case), but importer works as well. Now i'm sure about the next step, thanks!
Children
No Data