Long story short:
This way, the next time I encounter the same issue, I’ll be able to find the solution easier by googling.
This category contains assorted tips, tricks and solutions regarding all the different workarounds and solutions related to technology pretty much in general.
This article describes an interesting feature of the Multilingual User Interface in Classic SharePoint. So, in short, I encountered another, very interesting feature of Classic SharePoint Publishing sites, where multiple display languages were in use. When changing the web part title on a web part on a Classic SharePoint page, it seems like SharePoint saves the changes for you. In reality, only some users see the changes. So, in short:…Continue reading How to resolve Webpart title changes not reflecting for some users?
With the usual configuration of Office 365 and Azure, there might be multiple Azure AD (AAD) instances associated with your subscription. When creating registrations to whatever SharePoint-related apps that you might be using, if you create the registration to the wrong Azure AD, it can’t access the data in your SharePoint. Or at least without further configurations, it probably won’t get any data from your Office Graph API or whatever…Continue reading How to use the Azure AD associated with your SharePoint Online
This blog post briefly describes how to solve some of the most typical errors about missing PnP Cmdlets when using Windows Powershell (or SharePoint Online Management Shell). Symptoms When trying to run some PnP-related cmdlet, you get an error similar to the ones below: Connect-PnPOnline : The term ‘Connect-PnPOnline’ is not recognized as the name of a cmdlet, function, script file, or o perable program. Check the spelling of the…Continue reading How to solve errors about missing PnP Cmdlets on PowerShell
This post describes a couple of ways to fix the issue “For security reasons DTD is prohibited in this XML document”. At least for me, it appeared when trying to access SharePoint Online using Powershell or a console program using OfficeDev.PnP (which in turn uses CSOM). Error When running any piece of code, whether in PowerShell, .exe console, or anything else than the code behind relies on .NET Framework, you get…Continue reading Fixing the “For security reasons DTD is prohibited in this XML document.” issue
If you’re working on SharePoint deployments, and aren’t familiar with the SharePoint Search Query Tool, you’re probably doing something wrong. Or you’ve got a really troublefree tenant and simple requirements.. :) At least for technical issues, it’s the #1 tool for debugging what’s in the index and what isn’t. This blog post describes how to use it to investigate SharePoint Online Search index issues. First of all, you can get…Continue reading Using SharePoint Search Query Tool
This post describes a few different ways of fixing the “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.” error. One can encounter this issue when trying to package/publish a SharePoint solution, web site, or an Azure Webjob. Symptoms Visual Studio throws the following error when packaging a…Continue reading Fixing the error: “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.”
SharePoint Server 2013, 2016, and 2019 versions don’t have that old and familiar “sign in as a different user” option in the site menu, and for the time being, nor does SharePoint Online. However, sometimes it’s very useful functionality to have, so it’s a bit weird Microsoft chose to get rid of the option. This post outlines a method that I’ve found to work quite well for making SharePoint ask…Continue reading How to log into SharePoint as a different user
