Have you ever noticed that your SharePoint site just gets slower and slower? That’s probably because the performance of Structural Navigation is absolutely horrible, especially vs. Managed Navigation. This blog post includes our findings about the issue, and I also include some explanation of the reasons behind the difference and a simple comparison to Search-based navigation.
This post explains how to fix the “errorCodeTeamsDisabledForTenantForbidden” error when trying to add guest users to Microsoft Teams channel. This issue might arise when a user is invited to a channel in your organization’s Microsoft Teams for the first time. Fixing it usually just requires a flip of a switch, but might also include some waiting.
You get an error screen like this, when trying to join a Teams channel as a guest user.
Teams Guest access error
No fear, though – likely an easy fix!
This post describes one possible scenario for SharePoint-Teams -integration, how to achieve that, and what kind of issues there might be.
At Blue Meteorite, we at the Valo team have been leveraging Teams since early 2017 as our main communications channel. For us, it complements Yammer, email and Skype for Business quite nicely, although to be fair, it’s not always 100% clear which channel would be optimal for a certain piece of communication… 🙂
The Redmond Magazine calls Teams Microsoft’s response to Slack, and for someone who has used both, the source of inspiration is rather obvious. Built for “high-velocity teams”, it’s yet another collaboration/communication tool, but in a way more flexible than either Skype for Business or Yammer. First and foremost I’d position it as a challenger to services like Slack – and hence at least partially a new addition to Microsoft’s ecosystem.
Teams – the corporate, yet cheeky chat app for millenials… 🙂
This blog posts briefly describes how to solve some of the most typical errors about missing PnP Cmdlets when using Windows Powershell (or SharePoint Online Management Shell).
When trying to run some PnP-related cmdlet, you get an error similar to ones below:
|
1 2 3 4 5 6 7 8 9 10 |
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 name, or if a path was included, verify that the path is correct and try aga in. At C:\Users\koskela\Downloads\Import-Valo-With-Content\Import\New-Valo.ps1:46 char:5 + Connect-PnPOnline -Url $AdminUrl + ~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Connect-PnPOnline:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException |
|
1 2 3 4 5 6 7 8 9 10 |
Get-PnPTenantSite : The term 'Get-PnPTenantSite' is not recognized as the name of a cmdlet, function, script file, or o perable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try aga in. At C:\Users\koskela\Downloads\Import-Valo-With-Content\Import\New-Valo.ps1:51 char:23 + $SiteCollection = Get-PnPTenantSite -Url $Url -ErrorAction Silent ... + ~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Get-PnPTenantSite:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException |
|
1 2 3 4 5 6 7 8 9 10 |
New-PnPTenantSite : The term 'New-PnPTenantSite' is not recognized as the name of a cmdlet, function, script file, or o perable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try aga in. At C:\Users\koskela\Downloads\Import-Valo-With-Content\Import\New-Valo.ps1:60 char:7 + New-PnPTenantSite -Title $Configuration.SiteCollection.Title ` + ~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (New-PnPTenantSite:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException |
Usually, this is luckily a simple fix! Continue reading
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).
When running any piece of code, whether in PowerShell, .exe console or anything else than in the code behind relies on .NET Framework, you get an error like this:
|
1 2 3 |
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method. |