Sharepoint List - Filter on multi-select name column always displays no results
Hi all, When trying to filter my sharepoint list, I am experiencing issues for one specific column. The filter displays options as expected, listing all of the individuals that are present in that column, but upon selecting any single one or multiple of them, the result swaps to 'We didn't find anything to show here'. Specifically, when filtering the issue-column on the option of (Empty), it does filter successfully, so it is clearly experiencing issues with the names themselves. From what I can tell, there are no settings applied to the issue-column that would prevent it from filtering, so I'm expecting this to be a bug of some sorts. Looking for people who have had the same issue and/or have found a solution for this. Context: - It is certain that the names used to filter should return multiple results - List does not contain many entries and does not expand beyond list limits - Column in scope is a multi-select column pulling the microsoft IDs from all individuals as options - Another exact duplicate of this same column is present (for a different purpose), for which filtering works without issue - All other columns filter as expected
How get a report where "everyone except external users" group is used in my site collections
Hi all, I'm searching a way to get a report, via powershell, to all sites collections that “Everyone except external users” group is existing Someone could help me to build an efficient script? every suggestion is appreciated MassimoRenaming a folder with too many files
One of our teams has a Team/SharePoint site with an archive folder. Everything in there is old files, and they'd like to rename the folder. However, we get the error that it exceeds the list view threshold. I've spent the afternoon trying to find out how to get this folder renamed and so far nothing has worked. The general consensus is to create a filtered view, but I'm not sure what to filter it based on, as all of the files have been there and untouched for some time, causing most of the columns I could index be fairly similar (they were moved to SharePoint 3 years ago from an on-prem fileshare). One of the options I'd seen was to sync it using OneDrive and rename it locally but that still gave me the same error. I also tried renaming the folder from within Teams without success. If someone could provide some guidance for how to get this done, I'd appreciate it. Right now, I'm thinking I'll just have to move a bunch of stuff out of some of the folders to temporary locations, but even that is challenging as I'm not aware of a good way to get a count of items in folders and subfolders in SharePoint to know which are the best ones to move out.
Trimming SharePoint Version History - Minor Versions
Hello, I am a SharePoint Admin at my organization and I have been asked to reduce our total storage usage by reducing the number of versions and minor versions in our environment on all SharePoint sites. I have written a simple PowerShell script that loops through a csv file with site addresses, and runs this command per site -> New-SPOSiteFileVersionBatchDeleteJob -Identity $site.siteURL -MajorVersionLimit 100 -MajorWithMinorVersionsLimit 5 It was my understanding that for all sites in the csv file, for all document libraries on the site, and for all files in the libraries this command will reduce the file to the last 100 Major versions, and the last 5 minor versions of each major version. Unfortunately, this command is not actually reducing the minor versions. It is working with the Major versions just fine, but all minor versions are being retained for each major version retained. Is my understanding of this command wrong, or is it not working? Are there other factors to consider? Does anyone know of an alternative that can fit my needs? The overall plan is to trim the current version history, then apply the automatic version setting to each library in our tenant. Here is the MS guide I referenced, maybe I missed something -> https://learn.microsoft.com/en-us/sharepoint/tutorial-queue-a-trim-job Any help is greatly appreciated, Cam
Sharepoint logo not changing
Hey everyone, Like many other users, I can't seem to change the logo on my SPO site. I created this site via Team -> go to Sharepoint site. I've tried the many solutions: change the look change logo in site information replaced logo file with __siteIcon__.png in site assets, gets automatically re-written by system I get this error when I try to upload the picture via site information. Does anyone recognize how to adjust this setting? Thanks!
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.PromotedState does not update anymore
I wish to update the promoted status to 0 (page), 1 (unpublished news) or 3 (published news). I was always doing this via SharePoints column formatting. See .json column formatting below. This worked perfectly fine until about this week. Now it doesn't seem to work anymore. Now I tried updating the PromotedState also via PowerAutomate. This also doesn't seem to work... How should I now change the PromotedState. Does someone have any clue how I can update the PromotedState or why the column formatting way of wokring, suddently doesn't work anymore? The json code for column formatting. { "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json", "elmType": "div", "style": { "flex-wrap": "nowrap", "display": "flex", "flex-direction": "row" }, "children": [ { "elmType": "div", "txtContent": "=if(@currentField == 0 ,'0 : Page' , if(@currentField == 1, '1 : News (Unpublished)' , if(@currentField == 2 , '2 : News','') ) )", "style": { "box-sizing": "border-box", "padding": "4px 8px 5px 8px", "display": "flex", "border-radius": "16px", "align-items": "center", "overflow": "hidden", "margin": "4px 4px 4px 4px", "border": "1px solid" }, "attributes": { "class": "=if(@currentField == 0 ,'ms-fontColor-themePrimary ms-borderColor-themePrimary ms-bgColor-white' , if(@currentField == 1, 'ms-fontColor-themePrimary ms-borderColor-themePrimary ms-bgColor-themeLighter' , if(@currentField == 2 , 'ms-fontColor-white ms-borderColor-themePrimary ms-bgColor-themePrimary','') ) )" } }, { "elmType": "div", "style": { "font-size": "18px", "cursor": "pointer", "padding": "10px", "border-radius": "50%" }, "attributes": { "iconName": "MoreVertical", "class": "ms-fontColor-themePrimary ms-bgColor-themeLighter--hover" }, "customCardProps": { "openOnEvent": "click", "directionalHint": "rightCenter", "isBeakVisible": true, "formatter": { "elmType": "div", "style": { "display": "flex", "flex-direction": "column", "align-items": "flex-start" }, "children": [ { "elmType": "div", "txtContent": "Change to Page (0)", "style": { "padding": "10px 20px 10px 20px", "cursor": "pointer", "width": "200px" }, "attributes": { "class": "ms-bgColor-themeLighter--hover" }, "customRowAction": { "action": "setValue", "actionInput": { "PromotedState": "0" } } }, { "elmType": "div", "txtContent": "Change to unpublished news (1)", "style": { "padding": "10px 20px 10px 20px", "cursor": "pointer", "width": "200px" }, "attributes": { "class": "ms-bgColor-themeLighter--hover" }, "customRowAction": { "action": "setValue", "actionInput": { "PromotedState": "1" } } }, { "elmType": "div", "txtContent": "Change to published news (2)", "style": { "padding": "10px 20px 10px 20px", "cursor": "pointer", "width": "200px" }, "attributes": { "class": "ms-bgColor-themeLighter--hover" }, "customRowAction": { "action": "setValue", "actionInput": { "PromotedState": "2" } } } ] } } } ] } The HTTP SharePoint call to update the PromotedStatus.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 Rule Send an Email created by Former EE fail
SP Rules created by a former employee are no longer sent. The Rule was created to email other current users when a field was modified. The Rule was not set to email the former ee, but other users. The only thing that changed is the person who created the rule is no longer with our company. Once the Rule was duplicated by a current user it started working again. Rules are sent via <email address removed for privacy reasons> so why should it matter who created the rule? I see this becoming a large problem as SharePoint Alerts retire and users are now using Rules. For business critical Rules, we've used a Service Account to create the rules to prevent failure in the future. I can certainly understand rules that are created to go to former ee to no longer work since their account is no longer active, but if it's set up to go to other users that are still active, it should remain active and not fail regardless of the status of the created by.
