A SharePoint “page” is not synonymous with a Windows “folder”.  Our “path” value points to a Windows folder, and TFT can only interact with a Windows folder – not with a SharePoint page.

BUT SharePoint does have the option to map a traditional Windows drive/path to a SharePoint location.  Having done that, you can access the files stored in SharePoint either via SharePoint’s “page” paradigm or Windows’ “folder” paradigm.  That mapping, though, would have to be done on the client’s end, not by TFT.  Once done, the client tells TFT the mapped path, just as they ordinarily would if it were not a SharePoint location.

Another way to say it:  SharePoint stores files in a location, and you can either access those files via a “page” interface or a “folder” interface.  Mark is accustomed to the page interface (and I think he’s in the majority), but other people using SharePoint might be more accustomed to the folder interface.  But SharePoint supports both interface modes simultaneously.  TFT users would just need to make sure to map a drive to the SharePoint location so that they can tell TFT a path.

Actually this is a common scenario, where the user uses Onedrive as the local file repository, since File Explorer, Word, etc, cannot easily access online locations without some local Onedrive tool that is syncing the files and providing a static local path.

If you do not take that last step, of providing each user a common static path, like “\\here” or “T:\here”, or best yet, C:\here, you'll be forcing them to manually reassign everyone’s doc path is a chore; we'll feel your pain.

To rectify their situation, you can either:

• take the strategy of relocating the onedrive location path to C:\Onedrive\Here (I personally prefer this approach, since it requires no extra steps), then everyone gets a common C:\onedrive\path
  or
• you can take the old school method of providing a traditional drive letter. Younger folks usually hang up on this step in this particular situation because creating a dfrive letter for a drive-path is an entirely different then “net use” (which unfortunately only works for \\paths); though it accomplishes the same goal of providing a drive letter. You can cause this to occur by using “Subst” command to map a “%appdata%\Onedrive” folder path to a common path such as “Q:”; so that everyone sees the same path. “Subst %appdata%\onedrive Q:” for instance, works like a charm at providing Q:\Here.

For more on virtual servers and DMS, https://service.theformtool.com/hc/en-us/articles/360049325533-Organizing-a-More-Sophisticated-Network