document library
3242 TopicsContainer tree - PnP Modern Search
Hello everyone, I am trying to create a page on one of my SP sites dedicated to search. Specifically, I want to use tags/labels as filters. So far, I have managed to do this using the PnP Modern Search filter tool on one level (I create a column, map the crawled properties with a RefinableString, and configure the filter). Now I would like to do the same thing, but this time on multiple levels with a tree structure. I've created a TermSet and in the filter configuration, I saw this “Container tree” option, but nothing works, and I can't find any help or documentation on the subject. Does anyone have any information? Or a way to use this option and have tree view on the filter? Thank you in advance, any help will be greatly appreciated. Kind regards227Views0likes4CommentsHow are you creatively working around the SharePoint List View Threshold
Hi community I'm looking for outside-the-box approaches to dealing with the SharePoint List View Threshold (5,000 item limit). I'm familiar with the standard guidance, indexed columns, filtered views, folders, but I'm curious how others have solved this more creatively, especially in M365/SharePoint Online environments where you can't raise the threshold from the admin side. Additionally, if you've tackled this in a healthcare, government, or other highly regulated environment where you couldn't just move to an external database easily. Would love to hear what's worked (and what's blown up) in practice. Thanks in advance!32Views0likes0CommentsHow to show folder path for documents in a flat SharePoint library view
I have a document library with a multi-level folder structure that is somewhat complex. I created a view that removes folders and displays all documents in a flat structure (no folders shown). How can I display or indicate the folder path (or location) for each document in this flat view, so users can understand where each file is stored within the original folder hierarchy?Solved63Views0likes2CommentsNEW SharePoint & Purview Feature: Protect Files After Download!
🚀 New in SharePoint + Microsoft Purview: Extend Permissions Beyond the Cloud One of the biggest challenges in Microsoft 365 has always been this: 👉 What happens to your data when it leaves SharePoint? With this new feature, Microsoft finally closes that gap. You can now use Sensitivity Labels to extend SharePoint permissions to downloaded files — meaning protection doesn’t stop when a document is downloaded. 🔐 Here’s what that enables: Files remain protected even outside SharePoint Access is still enforced based on SharePoint permissions Changes in permissions are reflected in real-time Access can be revoked — even after download 💡 In other words: Your SharePoint security model now travels with the file This is a huge step forward for: ✅ Data Loss Prevention (DLP) ✅ Compliance & Governance ✅ Secure external collaboration ⚠️ Especially relevant if you're working with: Sensitive documents, external sharing, or regulated environments. 📖 I’ve just published a video where I break it all down: 👉 https://youtu.be/G6XvyU5GAqk Curious to hear your take: 👉 Would you trust this model over traditional access control? 👉 Where do you see the biggest impact in your organization? #Microsoft365 #SharePoint #MicrosoftPurview #DataProtection #CyberSecurity #Compliance #InformationProtection #M365 #ITSecurity #CloudSecurity34Views0likes0Comments404 error downloading file versions via CSOM (SharePoint 2013 On-Prem)
I need to download historical versions of a document from a SharePoint 2013 On Premises document library using a C# console application, so I can migrate them chronologically to SharePoint Online along with their column properties. While downloading the current latest version works perfectly, downloading older historical versions always fails. Standard CSOM methods fail because ListItem.Versions does not exist in the SharePoint 2013 v15 SDK. Reverting to direct HTTP endpoints consistently throws an error. Here is the exact exception message I receive: System.Net.Http.HttpRequestException: Response status code does not indicate success: 404 (Not Found). Below is the minimal reproducible code example demonstrating how the connection is initialized, how properties are loaded, and where the download fails on historical versions: using System; using System.IO; using System.Net.Http; using Microsoft.SharePoint.Client; using SP = Microsoft.SharePoint.Client; class Program { static void Main() { string siteUrl = "https://example.com"; using (ClientContext sourceCtx = new ClientContext(siteUrl)) { sourceCtx.Credentials = System.Net.CredentialCache.DefaultCredentials; List sourceList = sourceCtx.Web.Lists.GetByTitle("MyLibrary"); CamlQuery query = CamlQuery.CreateAllItemsQuery(); ListItemCollection items = sourceList.GetItems(query); sourceCtx.Load(items, ic => ic.Include( item => item.Id, item => item.File, item => item.File.Versions, item => item.File.ServerRelativeUrl )); sourceCtx.ExecuteQuery(); foreach (ListItem item in items) { if (item.File == null || !item.File.Exists) continue; foreach (FileVersion ver in item.File.Versions) { string absoluteVersionUrl = siteUrl.TrimEnd('/') + "/" + ver.Url.TrimStart('/'); using (var handler = new HttpClientHandler { Credentials = sourceCtx.Credentials }) using (var client = new HttpClient(handler)) { client.DefaultRequestHeaders.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f"); client.DefaultRequestHeaders.Add("User-Agent", "Mozilla/5.0"); // CRITICAL FAILURE HERE: Always throws 404 Not Found HttpResponseMessage response = client.GetAsync(absoluteVersionUrl).Result; response.EnsureSuccessStatusCode(); using (Stream fileStream = response.Content.ReadAsStreamAsync().Result) { // Upload logic to SPO goes here } } } } } } The version URL returned inside the property matches the following virtual folder layout format: _vti_history/512/Folder/Doc.docx My specific environment queries are: Why does navigating to the absolute history folder URL over an authenticated HttpClient trigger a 404 Not Found error in SharePoint 2013 on premises, even though the path token is extracted directly from the version url metadata property? Is there an alternative legacy REST endpoint routing structure or an alternative file stream extraction method available in the SharePoint 2013 (v15) SDK that allows an external client application to fetch older version binaries successfully?36Views0likes0CommentsHow to hide the Modify this view and Create View as per users available in groups
Hi All, I have classic view of SharePoint in list/libraries. I have group(for Managers). I just want want to show and hide the Create View/Modify View/Modify this view depends on users available in group. If user available in group(for Managers) then they can do anything like Create View/Modify View/Modify this view but if user is not a part of the group(for Managers) then they can not modify any Public views but the can create Personal view. Is there any way how I can achieve this functionality?117Views0likes1CommentBulk cleanup of content / documents in SharePoint
Hi, We currently have a few SharePoint sites that have old content / documents in document libraries. These are outdated and some are more than 5 years old. To delete these, we currently need to go to each document library / page (and its subfolders), sort by the date created / modified and then manually delete, which would take some time. Is there a way to bulk delete older content/ documents based on date, either within SharePoint admin or a third party program? (e.g. maybe run a query on a site to list any older content and then check off which page / document to delete). Jason72Views0likes1CommentSharePoint Video Playback Quality Defaults to 480p – Horrendous
I manage multimedia training for over 600 locations and two distribution centers, supporting nearly 10,000 team members. We have made a significant investment in producing high-quality training content through professional equipment, structured scripting, and dedicated production and editing time. However, once videos are uploaded to SharePoint, the default playback quality often degrades the experience to what appears to be approximately 480p. As a result, professionally produced content can look noticeably poor on initial playback. Many of our store-level team members are not in a position to manually adjust playback settings, so the default experience matters. The source files are high resolution, but the default playback does not reflect that quality. This also creates issues when leadership reviews training content, because the playback quality can reflect poorly on the production even though the original video is clear. We moved away from third-party hosting due to ad exposure during onboarding and the need for a controlled internal platform. We are intentionally using SharePoint and Stream as part of our existing Microsoft 365 ecosystem for scalability, governance, and centralized access. Introducing additional paid hosting platforms or external streaming solutions is not a direction we are pursuing. From an enterprise training standpoint, defaulting to low-resolution playback undermines engagement and credibility. Are there plans to allow administrators to define a default playback resolution for SharePoint or Stream videos? Are there recommended encoding settings that influence the initial playback quality more reliably? Are there roadmap updates around improving adaptive streaming behavior or default resolution selection? Any guidance or insight would be appreciated.100Views0likes1CommentSharePoint Creates a New Document Version After Printing
Hello All, We're experiencing an issue with version control in SharePoint. Here is the scenario: Our users are in SharePoint Online major/minor version controlled document libraries. They are opening Office 365 documents (Word, Excel, etc.) in the web app in view-only mode. They are making no changes to the files — just selecting File > Print. The action of printing is creating a new version of the file (ex: 3.0 to 3.1). This is causing issues with the document statues. After a new version is created, the file status is updated from Approved to Draft. But there was no change to the file to warrant a new version. Lastly, the new version is only created if the user is printing from the web app (Word, Excel, etc.). If they open the file in their desktop app, the document is not marked as modifed. After reaching out to Microsoft, we were informed this is a new "expected behavior". Quote from Microsoft: "From SharePoint’s perspective, printing = modifying, so this is not considered a bug but expected product behavior. When a document is printed from Office for the web (Word/Excel/PowerPoint Online), SharePoint treats this action as a file modification." Is anyone else experiencing this issue? Have you discovered a way to prevent this from happening?95Views1like1Comment