.

Source (your FileShare) and target (your SharePoint Library) is specified in the File Transport component. You give the component a name and run it visually step-by-step or schedule it as a batch job on the built-in batch server. With Bidirectional support you can also copy files from SharePoint to FileShares as well. Folders can be copied 1:1 or created from metadata.

To synchronize the FileShare with document changes made in SharePoint, you just create another component, and set SharePoint as source and the FileShare as target – it is that simple!.
Note that you can specify custom include/exclude criteria and renaming rules.

Key features
  • Preserve timestamps. (Modified, Created)
  • Keep folder hierarchy or flatten hierarchy with folder names as calculated metadata.
  • Retrieve metadata from any databases or ERP/CRM data source. (on-premises/cloud)
  • Apply Managed Metadata with optional calculated values. And you can also use data from databases or CSV files for the metadata.
  • Incremental features to skips existing files. (multiple conditions).
  • Criteria for include/exclude files. (option to use multiple Regular expressions)
  • High performance without any additional software or azure services needed.
  • Move or delete files and Merge folder hierarchies.
  • With Bidirectional support you can also copy files from SharePoint to FileShares as well. Folders can be copied 1:1 or created from metadata.

Use 1:1 with all source folders created or flatten the hierarchy like shown below.

**

*

Fusion use cases.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment