OfficeDevPnP

OfficeDev.PnP is a cool Microsoft-curated community effort to take the Office development to the next level.

The Shortest Debugging Article For SharePoint’s Taxonomy Fields Ever

SharePoint is not broken - it just does't work

Are you getting an error like “The SPListItem being updated was not retrieved with all taxonomy fields” when you try adding or modifying values in a TaxonomyField of a list item in SharePoint? Then read ahead, I’ve got a quick and dirty solution!

Reason

After quick googling and some frustration, I figured the probable reason for the issue. SharePoint went and broke the link between the internal Note-field and the actual TaxonomyField you’re supposed to be using. And this causes SharePoint to return slightly confusing errors.

Term Store Management Tool

Term Store Management Tool for managing (for example) the termsets associated with your Taxonomy Fields

In my case, my app actually just got a simple JSON response {“The SPListItem being updated was not retrieved with all taxonomy fields.”} I’d see this error any time I was trying to modify or create any values of a field of type TaxonomyField. I used OfficeDev.PnP’s TaxonomyExtensions to achieve this, but also tried the “normal” CSOM libraries – and the result was always the same. No amount of ctx.Load(item) -calls would help 😉

Like so many times with SharePoint, the solution’s simple, yet frustrating.  Continue reading

Related Posts:

How to solve errors about missing PnP Cmdlets on PowerShell

SharePoint PnP logo

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).

Symptoms

When trying to run some PnP-related cmdlet, you get an error similar to 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 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

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

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

Related Posts:

Fixing the “For security reasons DTD is prohibited in this XML document.” issue

"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."

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 in the code behind relies on .NET Framework, you get an error like this:

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.

Continue reading

Related Posts: