Syncing Files to Network folder | Link files option

This happens if the the M-Files user group All internal users or All internal and external users does not have edit access to a linked document. See the note in step 12 in the user guide for more information and how to modify the behavior on on-premises servers: Creating a New Connection to an External Source

In general I would recommend using Network Folder Connector instead of the linked files if the plan is to keep the files available on their original location. Network Folder Connector is more robust and also works from cloud vaults via Ground Link.

This is the permission on the document. For testing, I changed the NACL of the class.  It is still deleteing.

.

If this is an on-premises server, I would try the registry setting mentioned in the user guide just in case it helps. Otherwise you can raise this with M-Files Support or your reseller for further investigation.

Yes.  this is an on premise service.  Thanks Joonas Linkola 

 Joonas Linkola , one more thing....

The feature works for taking files from the Network Drive and sycnging/duplicating them in M-Files.  After the sync, the docs could be edited from either location and sync.

However, the initial transfer only syncs one way (from network drive to M-files) and not both ways.  What I mean is that If I put a document in the network folder, it syncs to M-Files, but When I put a document in M-FIles it does not sync to the network folder.

Is there a feature that will sync both ways?

None of our official solutions can create new files on network folders as far as I know, they are intended to make existing files accessible via M-Files. New documents are created in the M-Files vault.