Large-File-Handling-Posters

Large Files, Special Characters & Long File Names in NetDocuments Sync

Large-File-Handling-Posters
Large Files, Special Characters & Long File Names in NetDocuments Sync

Sync Reliability

Large File Handling, Special Characters & Long File Names During NetDocuments Sync

Sync failures rarely show up as a single dramatic error - more often it's the one file in ten thousand that won't move, probably because it's oversized, has a special character in the name, or exceeds a path-length limit. This article covers how netDocShare Sync is designed to handle these cases without silently dropping content.

The Challenge

NetDocuments and SharePoint each enforce their own limits and conventions: SharePoint has historically restricted certain characters in file and folder names, both systems cap total path length, and individual file sizes can run far larger than older sync tools were designed to handle. A sync engine that isn't built for these edge cases either fails the entire job or quietly skips the problematic files - and the worst outcome is the second one, because nobody finds out until someone goes looking for a document that was never actually synced.

How netDocShare Sync Handles It

netDocShare Sync addresses these edge cases through four connected capabilities:

Special character handling

Characters that SharePoint restricts in file or folder names are detected and handled automatically, rather than causing the sync job to fail outright.

Long file name and path support

netDocShare Sync is built to handle long file names (250+ characters) and folder names and deep folder structures within the limits each platform supports.

Large file support

Larger files sync without arbitrary size cutoffs that would otherwise leave big documents (like drawings, transcripts, exhibit bundles) out of the mirrored content.

Visible error reporting

When a file genuinely can't sync due to a platform-level limit, the job reports it explicitly rather than failing silently, so IT can address it.

Frequently Asked Questions

netDocShare Sync detects and handles these cases automatically rather than failing the entire sync job.

netDocShare Sync is designed to handle large files without an arbitrary low cutoff, within the underlying platform limits of NetDocuments and SharePoint.

Yes. Sync issues are reported explicitly rather than silently skipped, so IT can investigate and resolve them.

netDocShare Sync is built to handle long file names and deep folder structures within each platform's supported limits.

Quick Answer

netDocShare Sync is built to handle the edge cases that break naive sync tools: special characters in file and folder names, long file names and deep folder paths, and large file sizes. When a file genuinely can't sync due to a platform-level limit, the job reports the issue explicitly instead of silently skipping it.

Key Takeaways

  • Special characters in file or folder names are handled automatically rather than failing the sync job.
  • Large files sync without an arbitrary low size cutoff.
  • Long file names and deep folder structures are supported within each platform's limits.
  • Sync issues are reported visibly rather than silently skipped.

See how netDocShare Sync handles your firm's largest and messiest files.

Request a Demo