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.
Classic SharePoint features appearing on a Modern Site
I have a modern SharePoint site, with a modern list that has never been associated with classic SharePoint features. But today, two users have experienced intermittent instances of the list appearing in the classic interface. They have not accessed this site before now so I do not believe there should be a cache issue. Does anyone know why this is happening and how it's possible when this site has no association with Classic features? They are using the same browser, same permissions across the site but sometimes the list opens in Classic mode, sometimes it opens in Modern. It also is happening in incognito mode. They are unable to use the site while in Classic Interface at all - the people pickers deny them access ("Error: Sorry, you do not have permission to query for users" and they cannot edit anything because of this error.
SharePoint List Web Part - major caching issues
Hi All, I've spent a lot of time building a List based company calendar in our SharePoint Intranet Portal, and the calendar itself is working great, however I'm having no end of headaches with the List Web Part. (not just for this calendar, but all list web parts for that matter) The calendar has a Start and End field - both are Date and Time fields. A custom view is created for use with the List Web Part to embed an "upcoming week" view, this is based on a filter which checks both Start and End dates to see whether an event exists within or spans the date range from today to 7 days in the future, so it is a rolling 7 day window. This is based on a number of filter criteria which include [Today] and [Today]+6. The view also has a sort criteria to sort based on the Start (Date/Time) field. This all works fine when previewing the view within the list itself - at midnight the results update to include events from the day that is now 7 days in the future which were previously excluded. So the view itself is working fine. However the same view in a List Web part on another page suffers from a ridiculous amount of browser side (?) caching, to the point that it is basically broken and unusable. When I open the page the next day in a browser (even if the browser was closed) one of three things happens, somewhat at random: The events 7 days in the future (which just came into filter scope today) just don't appear until a forced page reload is done. The events 7 days in the future do appear but they are sorted incorrectly, appearing at the TOP when the date sort order should show them at the BOTTOM. Sometimes 2 happens but the event is shown with the Start and End Date/Time fields empty - so not only is it at the wrong end of the list it doesn't even show a date at all until the page is refreshed. Here is a picture showing the sort order being incorrect as in case 2: When these various problems happen a full CTRL-F5 browser refresh always updates the list to be complete, up to date and sorted correctly, however, if after that you click away from the page and follow a link to return to it OR press a regular F5 refresh it goes back to being incorrect! It takes many page reloads or a lot of time to pass (hours) before it finally settles down and gives the correct results every time. Then the next day the same caching problems happen again. If you go to a new browser or PC the same problems happen again, suggesting this is browser side caching not something at the servers. While the actual content of the list items update in real-time if you edit the list content in another page (which is pretty cool) the "result set" of list items (which items should or should not be seen) is heavily cached, and the sorting is unreliable. Has anyone else found a solution to this ? I have already done things like disabling offline mode for the list, (this only seems to affect caching of the actual data in the list items, not caching of filter results) etc and I cannot find a solution. The only thing I know which would probably work, as I have had to use this approach on another list is to extend the date range of the filter criteria for the view further into the future, then filter out the extra days using json code in "format view - however AFAIK you can only selectively hide rows like this if you use a custom rowFormatter, which means you have to fully re-implement the standard view including hard coding all the columns you want and it still won't look quite the same. This is a lot of work and maintenance overhead in the future to work around a caching problem that shouldn't exist in the first place. Any thoughts appreciated as a lot of time and effort has gone into building an entire calendar system around a SharePoint List, only to find that the list web part just doesn't work properly.Is it possible to add a Power Automate button to Form view
Hello! Is it possible to add a Power Automate button from the list view in a SharePoint list to the Form view? I was hoping that when a line item is open to view, we may be able to add this button onto the Form view as well somehow? Even just as a hyperlink and not a button? Just something clickable.
Document libraries added programmatically as tabs to Shared Channels are not visible
With the recent Teams UX updates, any document libraries added programmatically to Shared Channels no longer appear in the Teams interface even though they do show up when queried through PowerShell. Following the guidance in https://learn.microsoft.com/en-us/graph/teams-configuring-builtin-tabs%22https://learn.microsoft.com/en-us/graph/teams-configuring-builtin-tabs%22https://learn.microsoft.com/en-us/graph/teams-configuring-builtin-tabs%22https://learn.microsoft.com/en-us/graph/teams-configuring-builtin-tabs%22as well as the approaches I outlined in my blog post https://reshmeeauckloo.com/posts/powershell-teams-add-documentlibrary-as-tab/%22https://reshmeeauckloo.com/posts/powershell-teams-add-documentlibrary-as-tab/%22 using Microsoft Graph or PnP PowerShell, the tabs still fail to surface in the new Teams experience. The behaviour is inconsistent: The same tab‑creation methods work perfectly in standard channels. They also work for users who haven’t yet received the new Teams UX. And if the document libraries are added manually, they appear as expected in shared channels. At the moment, I’m trying to determine whether there is a supported way to add document library tabs to shared channels programmatically so that they remain visible in the new Teams interface. Any insights or confirmed workarounds would be appreciated.
Random error popping up in Search Center
Hey everyone, I joined this org earlier this year and am getting around to building a custom search center, the site was a lift and shift from SP2010 to SPO prior to my starting here, and as a part of that, there a lot of random things I need to clean-up. This error pops up on the search results page, but I can't tell where it's coming from or what triggers it. It appears after mousing-over a result, as shown in the screenshot below. I've tried fiddler and Chrome dev tools to determine where this is coming from, but no luck yet. After clicking Ok, I do get the normal search results and no longer receive an error message for any of the results on this page. Thanks, Eric
Page Redirection
Hello, I am trying to simulate a migration scenario in SharePoint Online and am running into a limitation I cannot resolve. For demo/testing purposes, I have two SharePoint Online sites (e.g. Old and New). I would like to redirect a small number of individual pages from the old site to corresponding pages in the new site, while the rest of the old site remains unchanged. Example: Redirect https://ps3c.sharepoint.com/sites/Old/SitePages/Test.aspx to https://ps3c.sharepoint.com/sites/New/SitePages/Test.aspx The page is a modern SharePoint page, and the URL itself is fixed for the purpose of the demo (i.e. users or tools open the page directly on *.sharepoint.com). All documentation I could find only describes redirecting entire SharePoint sites, not individual modern pages. Client-side approaches (JavaScript, HTML meta refresh, etc.) also appear to be blocked in modern SharePoint. Is there any supported or recommended way in SharePoint Online to implement page-level redirects for modern pages, or is this currently not supported by design? Kind regards
User Accounts Not Populating with Filters in Directory with PnP V4
I'm working on building a staff directory for my org. I'm leveraging the PnP Modern Search Web Parts for this directory. I am having issues with 5 user accounts not populating in the Search Results Web Part with the department or office filters applied to the SearchTerms box. I have RefinableString03 set to People:Department and People:SPS-DEPARTMENT. RefinableString09 is set to People:OFFICE and People:SPS-Location. If I set the SearchTerms box to *, the 5 missing user accounts populate along with other accounts that needed filtered out. The location/office and department attributes are set for each of these accounts. They show in the hovercard for each account. It seems that the department and office/location attributes are not being picked up by the SearchTerm filter when the RefinableString03 and or RefinableString09 are applied to the Search Results Web Part. User account attributes are synced from our on-prem AD environment. What piece am I missing here?
PNP Search Results sort by title
Hi. I have a PNP Search results webpart, that brings me all the Document Libraries in SharePoint site (that are not the standard ones Like site assets, pages etc) I want the results to be sorted, but i tried with sort column and it does not work, I want it to show in alphabetical order If i use "edit sort order" and select by title, it gives me an error I added a RefinableString where i have the title but it is still not sorting it How can i get this list sorted without having to add another column for the Title (with out the link) THank you
