SharePoint Online - Issues Saving Site as Template and Activating .wsp Solutions
Hello everyone, Recently I have been experiencing issues when saving a SharePoint site as a template and activating .wsp files within the Solution Gallery. This appears to be a recent change, as the same process and templates have worked successfully in the past. I wanted to see whether anyone else has recently experienced issues with SharePoint site templates (.wsp) in SharePoint Online. Findings: Site type is a Classic Team Site. Custom Script is enabled (DenyAddAndCustomizePages = Disabled). The .wsp file is successfully generated and appears in the Solution Gallery. The .wsp file does not activate. Activation fails with the error: "Activation of solutions with sandboxed code has been disabled." - Prior to this, SharePoint was only displaying a generic "Sorry, something went wrong" error. (All I did was turn content approval on and off in the Solution Gallery Library) Previously working .wsp files also fail to activate. The behaviour has been reproduced across multiple Microsoft 365 tenants. A Microsoft support ticket has already been raised. Has anyone else encountered this behaviour recently, or is aware of any changes affecting .wsp template activation in SharePoint Online? Thank you in advance for any insight or suggestions.
Sharepoint versioning bug with tables
Hi, So i have discovered a bug with the versioning in my sharepoint sitepage. When i edit a random piece of text ie. the title, in a text webpart with a table inside. The table shows up as changed in the version history of the sitepage. Below is an example of the issue. Here i've changed the title from "TitleChange" to "Title" and nothing else. The tables however still show as if they were changed. The first 2 tables are created with the built in tool in the text webpart, but the bottom 2 tables were created in word and then copied over to sharepoint. And as you can see the last table does not change as its suppose to, but the 3. table does. I figure its because something happens when you merge cells. So sharepoint does some sort of formatting that changes nothing but shows as changed. It only affects the table either when its made in sharepoint (1. & 2. table) or have merged cells (3. table), but not when its copied from word and has no merged cells. I've tried taking the html out and compared the before and after using powershell, but theres no change there. So can i stop this from happening or is there perhaps some sort of work around, so the tables dont show up as changed when they're infact not?
SharePoint Library Help Needed
I have a SharePoint Library where I would like to implement these requirements below and would appreciate your advise: Folders were created at the library level, which looks like the image below. I do not want people to be able to create any folders or upload documents or folders at the library level, but rather only when they open the folders. I have disabled folder creation and created a PowerApps form, so that users can only upload document, edit documents, view details of the documents when they open any of the folders., but I cannot seem to find the Power Apps form when I open any of the folders and try to upload a document or view a document or edit the document details. 2. I have a choice column called Fiscal Year which has options as = FY22, FY 23, FY24, FY25, FY26. By March 2026, I would like to create an automate flow which will auto create FY27 and remove FY22 from the choice, so that the choice column is always limited to only 5 years.
Can move SharePoint list items to folders in a list, but not back to root of list with Move To
Does anybody know if this is by decision or bug..? I created a SharePoint list for inventory and created 2 folders for private items (unique permissions on folders) to hide list items at certain times of the year. I tried to move them back OUT of the folder to the root of the list, but it does not allow me to do so. See screenshot on the bottom shows Move Here button is disabled on root of list.. attached is screenshot only when in folders.. My workaround would be to create another folder called public and inherit permissions from a list, set all views to show No Folders and move from private to public, but thought I 'should' be able to move back out to root of list...I don't want 100 different SharePoint sites. How to create private teams w/o a new site?
Guys. WTF. I've inherited a problem where a company of 50 people has 100 sharepoint sites - because users created different Teams for different projects, and Microsoft makes it incredibly opaque what this actually means. Now we have 100 SharePoint sites, many of which are unused, but all of which appear in the list of sites in 365AC. The structure we WANT is 1 Sharepoint site for our 1 org, but multiple locations within that site, and multiple groups for multiple projects. I THOUGHT what could work was converting the excess Teams into Private Channels. But I have now learned that private channels ALSO create SharePoint sites, because _______. Most confusingly, all of these sharepoint 'sites' DO exist within our main SharePoint website - they're just pages (but not 'pages') pretending to be a fresh sharepoint website. This confuses the **** out of people, the way they've redefined what a 'site' is, what a 'team' is, etc. This is genuinely hot garbage, and it's suddenly clear to me why people always push back on using SharePoint over OneDrive. Recommendations for... not having this disaster? Making a structure that is intuitive and doesn't redefine what a site and page are, and allows you to have private locations for management or projects, but DOESN'T create a 'site' within the main 'site', with it's OWN 'documents', and it's own 'Notebook' (which isn't a document) and it's own 'Conversations' (which are NOT conversations), and it's own 'pages'? I don't work with dumb people - these are very technical people. But even our main SharePoint guy is mystified by these interactions. Does it make more sense in another language? If anyone at Microsoft is reading - the english term 'site', comes from the word 'website', which generally refers to a distinct web service with a distinct domain name. These contained different webPAGES.. When websites started existing off a shared domain name, like company1.sharepoint.com and company2.sharepoint.com - this confused people, but they put up with it, because it was relatively easy to explain the tech behind this - having websites under a single site, that wasn't too hard to understand. But what SharePoint seems to do, is extend this practice into absolute hysteria, where a particular webPAGE of a webSITE is ALSO a site, but also is a TEAM, or COULD be a CHANNEL. OR it could be a PAGE - WHO knows? If it's a TEAM, that TEAM could have CONVERSATIONS, which aren't actually Team Conversations - they're EMAILS. But this is fine, because all CONVERSATIONS of a TEAM done in TEAMS are actually stored as EMAILS so really those, CONVERSATIONS should be CONVERSATIONS... So why aren't these conversations in Teams between a Team that are stored as Emails not showing in the Conversations which show emails within that Team? aefggaddadsfasdHow 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?Accessing External Sharepoint Site
I am able to access internal Sharepoints within my company and have up until now been able to access Sharepoints outside the company. When I now try to access an external Sharepoint, I get the following message on the external company's landing page. "Your account has been locked. Contact your support person to unlock it, then try again...." The external company states they have not made changes any access protocols. Likewise, my company says nothing has changed with respect to the rules/ability to access external Sharepoints. Someone indicated that the Microsoft “federation” settings/setup of the two companies may (now) be incompatible. Has anyone encountered this issue?
