December 11, 2017

SharePoint Online: Hide content type on list


Hide Content type on SharePoint Online document library.


Requires PnP-Powershell, installation instructions here.

Connect-PnPOnline –Url “”
$ctx = Get-PnPContext

$web = Get-PnPWeb

$doclib = Get-PnPList -Identity "<DOCLIBNAME>" -Includes ContentTypes,RootFolder.UniqueContentTypeOrder

$rootFolder = $doclib.RootFolder

$ct = $doclib.ContentTypes | where {$_.Name -eq "<CT TO BE HIDDEN>"}
$ct2 = $doclib.ContentTypes | where {$_.Name -eq "<CT TO BE HIDDEN, USUALLY FOLDER>"}

if($rootFolder.UniqueContentTypeOrder -eq $null)
     $contentTypesInPlace = New-Object -TypeName 'System.Collections.Generic.List[Microsoft.SharePoint.Client.ContentTypeId]'

    #$contentTypesInPlace = $doclib.ContentTypes | where {$_.Id -ne $ct.Id}
     foreach($ct in $doclib.ContentTypes | where {$_.Id -ne $ct.Id -and $_.Id -ne $ct2.Id})
     $contentTypesInPlace = [System.Collections.ArrayList] $rootFolder.UniqueContentTypeOrder
     $contentTypesInPlace = $contentTypesInPlace | where {$_.StringValue -ne $ct.Id}
#Set the UniqueContentTypeOrder to the collection we made above
$rootFolder.UniqueContentTypeOrder = [System.Collections.Generic.List[Microsoft.SharePoint.Client.ContentTypeId]] $contentTypesInPlace
#Update the root folder

November 13, 2017

Azure Stream Analytics job Query IoTHub.ConnectionDeviceId null


Having connected Azure Stream Analytics job to IoT Hub, and trying to get hold of IoTHub.ConnectionDeviceId in the Stream Analytics job Query, you just get NULL value. Several instructions on the net just say that query such as below should return the device id, but no.

SELECT IoTHub.ConnectionDeviceId AS DeviceId

Posts such as this almost made me open a support ticket as I was suspecting some platform related issue.


This one was rather trivial once I used SELECT * to find out what is really coming from the IoTHub, so changing the query to

SELECT IoTHub.IoTHub.ConnectionDeviceId

will do the trick and you can get hold of the Device ID without explicitly passing it from the IoT device to IoT Hub.

And further searching got me to this article that has clear example with query such as in my example.

August 1, 2017

UNMS on Azure

Below are the bare minimum steps to install Ubiquiti’s Network Management System on a Docker container on Azure Ubuntu VM. After adding my ER-X-SFP v 1.9.7 to UNMS, I can now see it on the UNMS console.

  1. Create new VM "Docker on Ubuntu Server"
  2. clip_image001

    1. For VM Size, I used Basic A1, which nearly corresponds with the requirements for RAM (1.75GB vs 2 GB)
  3. Connect to VM using Putty
    1. Username and pwd are the ones you typed in when creating the VM
  4. Update Ubuntu to 16.04.1 (or newer)
  5. $ sudo apt-get update
    $ sudo apt-get dist-upgrade

  6. To check upgrade succeeded, run
  7. $ lsb_release -a

  8. According to UNMS installation steps at run commands
  9. $ curl -fsSL > /tmp/ && sudo bash /tmp/

  10. Add HTTP endpoint to Azure VM, optionally allowing it only from your IP address
  11. Connect to UNMS using browser at
  12. In UNMS Settings, I changed the “Ping Address” to as suggested at

Optional modifications

In addition I changed UNMS Inform port using the following command, and added endpoint to Azure to allow it from my home IP.

$ sudo bash /tmp/ --ws-port 8444

I also added CNAME to my DNS provider to access UNMS using my my own domain name. In UNMS settings at Settings –> UNMS I added this custom domain name to “UNMS Hostname/IP”.


May 2, 2017

Office Online Server on Windows Server 2016: 'InkandHandwritingServices' was not found


When installing Office Online Server on Windows Server 2016, and using the Add-WindowsFeature script provided on all of the installation instruction articles, such as this, you will get error

Add-WindowsFeature : ArgumentNotValid: The role, role service, or feature name is not valid: 'InkandHandwritingServices'. The name was not found.


Windows Server 2016 doesn’t contain Ink And Handwriting Services, so omit that from the Add-WindowsFeature command. So, working script for WS2016 is:

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,NET-Framework-Features,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-HTTP-Activation45

March 31, 2017

SharePoint: Workaround for Script Editor and Chrome ERR_BLOCKED_BY_XSS_AUDITOR


In recent Chrome browser, it has become little annoying to work with SharePoint tool due to Chrome throwing ERR_BLOCKED_BY_XSS_AUDITOR error when working with the Script Editor web part. This is due to XSS auditor on Chrome blocking JavaScript included in the Script Editor Web Part. Issue occurs on SharePoint Online and on-premises SharePoint 2016 and 2013 and occurs regardless if site is accessed via HTTP or HTTPS.

Steps to repro:
  1. On SharePoint publishing page, add Script Editor web part to content area or web part zone
  2. Add the following code to the web part (any JS will do the trick): 


  3. Click Insert at the bottom of the Script Editor content dialog
    --> Chrome throws you to page saying

    This page isn’t working

    Chrome detected unusual code on this page and blocked it to protect your personal information (for example, passwords, phone numbers, and credit cards).
    • Try visiting the site's homepage.


You can disable the XSS Auditor by appending the following value to web.config on your on-premises SharePoint 2013 or 2016 web site.

        <add name="X-XSS-Protection" value="0" />

For SharePoint Online, there is no workaround at the moment.

March 21, 2017

SharePoint: Getting list items with SPFx and CamlQuery


When fetching SPList items using SPFx and REST combined with CAMLQuery, you need to use However, the following code wasn’t working:

const options: ISPHttpClientOptions = {
	body: `{'query': {
		'__metadata': {'type': 'SP.CamlQuery'},
		'ViewXml': '<View><Query><OrderBy><FieldRef Name="ID"" /></OrderBy></Query></View>'

return + '//' + window.location.hostname + ( +
	.then((response: SPHttpClientResponse) => {
		return response.json();

But instead it was throwing errors such as:

The property 'query' does not exist on type 'SP.Data.PagesItem'. Make sure to only use property names that are defined by the type.


An entry without a type name was found, but no expected type was specified. To allow entries without type information, the expected type must also be specified when the model is specified.


First of all make sure you use the “odata-version: 3.0”, but more importantly, as you’re using POST, change the REST URL from …/items to …/GetItems.

Final working code:

const options: ISPHttpClientOptions = {
	headers: {'odata-version':'3.0'},
	body: `{'query': {
		'__metadata': {'type': 'SP.CamlQuery'},
		'ViewXml': '<View><Query><OrderBy><FieldRef Name="ID"" /></OrderBy></Query></View>'

return + '//' + window.location.hostname + ( +
	.then((response: SPHttpClientResponse) => {
		return response.json();

Oh, and no need to use JSON.stringify() when building the ISPHttpClientOptions body query, just use ` around the code and it will already be a string.