Home

Sharepoint file previewing not working under specific curcumstance

%3CLINGO-SUB%20id%3D%22lingo-sub-800806%22%20slang%3D%22en-US%22%3ESharepoint%20file%20previewing%20not%20working%20under%20specific%20curcumstance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-800806%22%20slang%3D%22en-US%22%3E%3CP%3EDuring%20the%20process%20of%20linking%20our%20documentation%20SharePoint%20to%20our%20Microsoft%20TEAMS%20channel%2C%20we%20noted%20after%20reproducing%20the%20issue%20multiple%20times%20that%2C%20regardless%20of%20the%20indication%20on%20the%20TEAMS%20Known%20Issues%20(%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fknown-issues%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fknown-issues%3C%2FA%3E%3C%2FFONT%3E)%2C%20there%20is%20a%20pattern%20to%20all%20of%20our%20non-working%20previews%20%3B%20the%20file%20path%20is%20always%20too%20long%20-%20probably%20more%20than%20260%20characters%20-%20in%20those%20specific%20cases%20and%20has%20to%20be%20reworked%20(renaming%20of%20file%20and%2For%20parent(s)%20folder)%2C%20which%20instantly%20solves%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhile%20it%20is%20obvious%20in%20our%20case%20that%20the%20file%20structure%20that%20SharePoint%20uses%20allows%20path%20names%20greater%20than%20the%20usual%20limit%20-%20our%20library%20was%20entirely%20built%20online%20-%2C%20it%20seems%20that%20TEAMS%20doesn't%20in%20the%20case%20of%20previewing%2C%20which%20causes%20an%20error.%20Please%20note%20that%20the%20file%20is%20still%20accessible%20and%20may%20also%20be%20opened%20directly%20through%20TEAMS.%20Only%20the%20previewing%20is%20affected.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-800806%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Interface%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-801432%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20file%20previewing%20not%20working%20under%20specific%20curcumstance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-801432%22%20slang%3D%22en-US%22%3EYep%2C%20in%20general%20I%20have%20seen%20that%20files%20in%20Teams%20behaves%20worst%20compared%20with%20the%20experience%20we%20have%20in%20SPO...for%20instance%2C%20in%20SPO%20we%20have%20a%20400%20path%20limit%20and%20as%20you%20say%20in%20Teams%20we%20are%20not%20still%20there...same%20happens%20with%20special%20characters%20support...SPO%20behaves%20better%20than%20Teams%20in%20this%20regard%3C%2FLINGO-BODY%3E
FrancisSarrazin
Occasional Visitor

During the process of linking our documentation SharePoint to our Microsoft TEAMS channel, we noted after reproducing the issue multiple times that, regardless of the indication on the TEAMS Known Issues (https://docs.microsoft.com/en-us/microsoftteams/known-issues), there is a pattern to all of our non-working previews ; the file path is always too long - probably more than 260 characters - in those specific cases and has to be reworked (renaming of file and/or parent(s) folder), which instantly solves the issue.

 

While it is obvious in our case that the file structure that SharePoint uses allows path names greater than the usual limit - our library was entirely built online -, it seems that TEAMS doesn't in the case of previewing, which causes an error. Please note that the file is still accessible and may also be opened directly through TEAMS. Only the previewing is affected.

1 Reply
Yep, in general I have seen that files in Teams behaves worst compared with the experience we have in SPO...for instance, in SPO we have a 400 path limit and as you say in Teams we are not still there...same happens with special characters support...SPO behaves better than Teams in this regard