Hi,
Set-PnPView seems to create a bug in Document Libraries through which we can't open Office documents in Online View anymore and after a while documents can only be downloaded but not opened in the desktop version. Even when deleting all views and creating new ones it does not fix the problem.
This problem only occurs from within the Document Library.
If we open the document through a direct link, share link, Teams, another systems through embed code - then everything works as expected.
I created a ticket at Microsoft some weeks ago when I didn't knew it was because of the cmdlet.
After some testing I was able to recreate the problem every time I used Set-PnPView.
After waiting for 3 weeks MS Support was still not able to understand what I wrote and always being told that escalation Team is working on it... so I'm here.
Steps to reproduce behavior
Create document library
Use Set-PnPView -Identity "All Documents" -List "Document Library" -Fields "Name", "Modified"
PnP PowerShell for SharePoint Online
3.23.2007.0 (also with an older version which I used before)
Installed through the PowerShell Gallery with Install-Module
Can someone help us?
Does someone know how we can fix it in our current document libraries?
I used it on 24 document libraries which are now broken with no fix in sight.
If we cant fix it I will need to change the OneDrive mapping on 400+ computers and move their existing data to new document libraries.
Hi, Set-PnPView seems to create a bug in Document Libraries through which we can't open Office documents in Online View anymore and after a while documents can only be downloaded but not opened in the desktop version. Even when deleting all views and creating new ones it does not fix the problem.
This problem only occurs from within the Document Library. If we open the document through a direct link, share link, Teams, another systems through embed code - then everything works as expected.
I created a ticket at Microsoft some weeks ago when I didn't knew it was because of the cmdlet. After some testing I was able to recreate the problem every time I used Set-PnPView. After waiting for 3 weeks MS Support was still not able to understand what I wrote and always being told that escalation Team is working on it... so I'm here.
Steps to reproduce behavior
PnP PowerShell for SharePoint Online 3.23.2007.0 (also with an older version which I used before) Installed through the PowerShell Gallery with Install-Module
Can someone help us? Does someone know how we can fix it in our current document libraries? I used it on 24 document libraries which are now broken with no fix in sight.
If we cant fix it I will need to change the OneDrive mapping on 400+ computers and move their existing data to new document libraries.