Forum Widgets
Latest Discussions
SPFx Debug Manifests Not Loading localhost - Debug Query String Not Recognised
Hi everyone, We are currently facing an issue with debugging an SPFx solution in SharePoint Online. Previously, we were able to debug our solution using the standard debug query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js However, recently this has stopped working in our development environment. Current Behaviour When we paste the debug query string into the SharePoint page URL, the page loads normally but the debug manifests are not recognised or loaded. The “Allow debug scripts” warning banner does not appear on the page as expected. Even after clicking “Load debug scripts”, the browser still does not load the debug manifests. The browser does not attempt to load https://localhost:4321/temp/build/manifests.js. Because of this, our local debug build is not injected into the page, making it impossible to debug the solution. Additional Observations There are no console errors at the moment. The issue occurs across multiple machines (Windows and Mac). Tested on multiple browsers: Microsoft Edge Google Chrome Safari The SPFx solution itself has no issues and previously worked correctly with the same debugging method. Troubleshooting Already Attempted We followed the recommended steps, including: Allowing the browser permission to access local network devices Running gulp trust-dev-cert Verifying the debug query string format Confirming the manifest path: https://localhost:4321/temp/build/manifests.js Checking browser console logs Testing with CSP parameters Allowed to run custom scripts in the site from the SharePoint Admin centre. None of these resolved the issue. Microsoft Support Response We also contacted SharePoint Technical Support through the Microsoft Service Hub, and the response we received was that this behaviour is now "by design" and that serving debug manifests through the debug query string is no longer supported. The workaround suggested by Microsoft Support was to package the solution and deploy it to test changes instead of using the debug query string. Potential Impact If this change is indeed by design, it could have a significant impact on development workflows for organisations building SPFx solutions. The ability to load debug manifests from localhost is a core part of the SPFx development and debugging process. Without it, developers would need to package and deploy the solution for every small change, which would introduce a considerable amount of additional time, effort, and overhead during development and testing. Questions Has anyone else recently experienced this issue with SPFx local debugging? Has the debugManifestsFile query string approach been deprecated or restricted in SharePoint Online? If so, what is the recommended approach for debugging SPFx solutions locally now? Any insight from the community would be greatly appreciated. Thanks.Top 4 NEW SharePoint Features You MUST Try in 2026 | Approvals, Quick Steps, PDF Tools & More
🚀 The 4 Most Important SharePoint Updates You Shouldn’t Miss in 2026 Q1! In the past weeks I deep‑dived into some powerful new SharePoint and Microsoft 365 capabilities — and today I’ve put everything together in one recap video. These improvements boost automation, simplify approvals, and enhance document workflows for every team working in Microsoft 365. 🔍 Included in the recap: Default Approvers in Lists & Libraries Quick Steps to automate processes New PDF editing capabilities in SharePoint & OneDrive Productivity enhancements across Microsoft 365 If you work with SharePoint as an IT admin, power user, or content manager, these features will save you time and streamline collaboration. 🎥 Watch the full recap here: 👉 https://youtu.be/RTT-Kg_vrMQ #SharePoint #Microsoft365 #M365 #Collaboration #Productivity #Automation #DigitalWorkplace
SharePoint: site Quota threshold exceeded, but no notifications received
I am looking at setting site quotas across our tenancy, to control storage growth by prompting users to think about what they're uploading, and whether old files can be deleted. I set a low quota (1GB) on a test site, with "Allow notifications" checked, and a threshold set. I then stared copying files to the site. The site is currently shown to be at 87% of its quota in SP Admin centre, and above 98% according to the storage metrics, with the threshold set at 80%. If I go to Site Settings, I see a very narrow banner informing me that the site is out of storage space. This is not displayed anywhere else, though, I (as site owner and primary site admin) haven't received any email notifications, nothing is shown outside the settings pages - I can upload another file with no warning. It is now over 72 hours since I started the testing. If site owners need to go to a settings page to see a warning, it is unlikely to achieve the desired effect and will be disruptive to users when sites do unexpectedly run out of space. Is there something else we can (or need to) do to enable notifications to site owners?
In a PnP search how long does the crawl take
In an Education tenant using SharePoint online if you add a new mapping into the PnP search because the crawled property was unpopulated how long do you have to wait before it is fully populated? Copilot chat suggested 30 minutes to 48 hours. At 48 hours and it managed to find about 45 items. I was anticipating about 900 items. 10 hours later it is still showing 45 items. How do I know if it finished the crawl or just abandoned it, whether it is actually still going or it can genuinely only find 45 items. Thank you.
Sharepoint Sync Onedrive - Long File Name issues
I need move some file from sharepoint to onedrive . i have add sharepoint folder to shortcut one drive . but when update on this device. , prompt up file long file name , need rename shorted after can sync . a lot of files. I tried using PnPShell to try search long file name files . but the scripts does not work .Pls share other solution to solve out the isseus.
Broken SharePoint list indexes across multiple tenants
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Hello everyone, I’m looking for community input on an issue we are seeing with SharePoint list indexes across multiple tenants. Over the past two weeks, we have received many reports of views, search, CSOM, and REST queries missing items. After investigation, we found that the root cause appears to be broken list indexes. This is not isolated to a single list or tenant. We are seeing the same behavior on multiple lists, across multiple sites, in multiple tenants. In all cases, indexed columns stop behaving correctly. The only workaround we have found is to remove and recreate the index. However, this becomes very problematic when “Enforce unique values” is enabled. If a list contains more than 5,000 items, this option cannot be re‑enabled without drastic steps, such as temporarily removing items from the list. Example scenario We have a list with about 25,000 items and a Text column called Identifier, which is indexed and has Enforce unique values enabled. This list has worked perfectly for years but started failing last week. Users are now seeing the following issues: Duplicate Identifiers can be added without any warning, even though unique values are enforced. Filtering or searching by Identifier does not return results. CSOM and REST queries filtering on Identifier fail to find existing items. Previously, all of this worked without issue. Main question My understanding was that indexed columns should work correctly, even when the total list size exceeds 5,000 items, as long as the result set is below the list view threshold. However, Microsoft support has indicated that once a list exceeds 5,000 items, correct results cannot be guaranteed, even when filtering on indexed columns. If this is truly “by design,” it would severely limit the usefulness of SharePoint lists and libraries, as exceeding 5,000 items is very common. I’d really appreciate hearing: Whether others are seeing the same behavior If this is truly expected / by design Any better workarounds or official guidance If you know of clear documentation on this topic, please share it. At the moment, our only reliable fallback is retrieving all items and filtering in memory, which is far from ideal. Thanks in advance!Avoid two search modes (modern, classic) in Sharepoint Subscription Edition (SE)
We are using SharePoint Subscription Edition (SE) and seem to have two search experiences: modern and classic. I want to avoid confusing users and make search behave consistently across the site. Scenario 1: site search box uses modern search When users search from the “Search this site” box outside a document library, SharePoint opens the modern search page with a URL like: https://domain.org/sites/site/_layouts/15/search.aspx/siteall?q=test If I change Site Settings > Search Settings, it has no effect on this behavior. Question 1: Is it possible to change the URL used by the built-in “Search this site” box, so it opens a different page? Scenario 2: Search Settings works for classic results, but not for modern URL When users search inside a document library and click “Expand search”, SharePoint uses the value from Search Settings. However, if I configure “Send queries to a custom results page URL” and enter the modern search URL above, SharePoint does not use it correctly. It appends results.aspx?k= and the result is a 404. Question 2: Can Search Settings be used with a modern search URL such as: https://domain.org/sites/site/_layouts/15/search.aspx/siteall without SharePoint appending results.aspx?k=? I did not find any setting in Central Administration that seems to control either behavior. My goal is not to customize the results layout (not possible in OOTB modern search page as far as I know), but to make users land on a single, consistent search experience.
Add a heading or column containing instructions for New Item in SharePoint List
I'm working in a SharePoint List in Modern View. I need to add a heading or a column that contains a set of instructions. I need the instructions to be there when adding a New Item. Everything that AI has suggested fails because it is not valid in the Share Point Modern View. Thanks, for your help.
Using meta data from a MS form created in SharePoint in Email
Hi, I've created a Form within SharePoint and I want to add the results to 1) An Approval 2) To Body of Email This is the main part of the Flow and I'm using Compose actions The Names column is a People or Group type. Field = Names The Building Ward Access is a Choice type Field = Building_x002d_Ward_x0020_Access Both have 'Allow Multiple Selections' I'm try just to add the Name or Names and Building / Ward or plural into the body of the Approval and Email. I seem to be getting additional data including @odata I've been using Join expressions, if Statements and nothing seems to be working?? Can someone please assist???
