TL;DR: These scripts in the post use PnP.PowerShell to enumerate document libraries and compare file URLs against Search result to determine whether files are searchable. The plan was to show whether those files were indexable successfully, however the Get-PnPSearchCrawlLog is deprecated, see Deprecate Get-PnPSearchCrawlLog cmdlet for more details. This is because the underlying CSOM endpoint GetCrawledUrls has been deprecated. Use the first script when you want a quick list of files that are present in a library but do not appear in Search results.

Summary Investigates missing search results despite crawl entries with no errors. Correlates SPItemModifiedTime blank entries with unsearchable files (while noting some blanks still indexed, so additional checks are required). Provides a PnP PowerShell script to detect affected items at scale. Shares remediation and prevention guidance. Table of Contents Background Symptoms Investigation Tenant-wide Detection Script How the Script Works Results Root Cause Fix Prevention Tips References Background A particular document library stopped returning many files in SharePoint search, even though the crawl log showed entries without errors.

Problem Statement When using the KQL query ContentClass:STS_List_DocumentLibrary without additional filters, some document libraries (like “Shared Documents”) are not appearing in search results, even though they exist and contain content. Initial Troubleshooting Steps Taken 1. Hidden Site-Level Visibility Setting Action: Visited https://<your-site>/_layouts/srchvis.aspx and enabled “Always index all Web Parts on this site” Status: ✅ Enabled - Monitoring for 24-48 hours to see if this resolves the issue Result: No effect on bringing the shared documents search result

Table of Contents Problem Statement Solution Overview Prerequisites Implementation Guide Step 1: Get Site and List IDs Step 2: Test with Graph Explorer Step 3: Initial Search Implementation Step 4: Handle Pagination Complete Code Examples Performance Considerations Conclusion Problem Statement After importing 10,000+ records into SharePoint using Power Automate bulk import techniques, we encountered Power Apps delegation limits that prevented effective searching and filtering of large datasets. There is the option of using Power Automate to get the results, however it adds more artefacts to a simple app designed for search.

Introduction When building Power Apps with SharePoint lists, you may encounter delegation warnings especially when using the Search function on large datasets. This post explains why delegation matters, how it affects your app, and practical workarounds to enable effective searching. The Delegation Problem By default, if you create an app using the built-in template connected to a SharePoint list, the gallery’s Items property might be set to: Search([@FolderMappingDetails], SearchInput1.Text, Title, Title) This triggers a delegation warning because the Search function is not fully delegable to SharePoint.

Introduction Filtering and searching data in a Power Apps gallery is a common requirement for building user-friendly business apps. This post shows how to combine a dropdown filter (with an ‘All’ option) and a search box to create a flexible, responsive gallery experience. Scenario Suppose you have a collection called colFolderMapping with a field named Database and a gallery displaying items. You want users to: Select a database from a dropdown (or ‘All’ to show everything) Search for items by title using a search box See results update instantly in the gallery PowerFx Formula Here’s the formula for the gallery’s Items property:

Introduction Searching for files using the Document ID field in SharePoint can be challenging, especially when the ID contains hyphens (-). Hyphens are interpreted by SharePoint Search as a “NOT” operator, which can unintentionally exclude results and make it difficult to locate documents by their full ID. Why Is This Happening? The Document ID is a unique identifier for files, but by default, searching for an ID like M3DJHK53YMAX-2114042065-47 using the standard search box (with or without quotes) may not work as expected due to the hyphen’s special meaning in search queries.

Introduction SharePoint search is powerful, but searching by date ranges can be surprisingly tricky. Many users struggle with date-based queries, especially when trying to find documents modified or created within specific timeframes. This guide provides tips to use SharePoint/M365 search capabilities with date fields: write, LastModifiedTime, Created. The Challenge with Date Searches Date searches in SharePoint have several gotchas that can frustrate users: Format requirements - SharePoint expects specific date formats (American format UTC , i.

Introduction Microsoft Teams provides a unified platform for end users to collaborate on files stored within SharePoint. However, there are notable differences between the two platforms that can influence your decision on when to use SharePoint and when to use Teams. Search Functionality Contextual Search Contextual search on libraries does not exist within Teams, while SharePoint offers richer contextual search at library, site, organization, and hub levels. Issue with Results from Shared Channels There is an issue searching contents within shared channels where the shared channel name is shown as Mock Team Name which is not helpful identitying the source of the search results without opening the file.

Introduction Have you ever encountered a situation where the search results in SharePoint show incorrect document titles and modified dates? This can be frustrating, especially when you rely on accurate metadata for document management. In this blog post, we’ll explore why this happens and how to resolve it. Problem Statement A business user reported that the search results for a particular document displayed the wrong name and modified date. Upon investigation, we found that the title and modified date were being pulled from the document properties rather than the metadata shown in the SharePoint library.

SharePoint Online offers the useful feature of news links to avoid duplication of news articles and promote existing posts across different sites. This is especially beneficial when news creation is enabled for various departments or directorates, allowing them to share significant news organization-wide. However, the News WebPart might display both the news links and the original articles, resulting in duplicated content. To manage this, you can utilize the OriginalSourceUrl column, which stores the link to the source news article.

SharePoint Search: Excluding Columns from Search Results SharePoint empowers users to manage and organize vast amounts of data efficiently. However, not all data within a SharePoint site might need to be searchable. Do you miss the functionality to control visibility of sensitive or irrelevant information in column. The Challenge You might have encountered instances where you need certain columns in your SharePoint lists or libraries to be excluded from search results.