This is a follow up from my previous post on Creating SharePoint Online Document Set in Microsoft Flow.
We’ve created the document set, and now we want to update some of the properties for the document set, one of which is a single value taxonomy field.
Assuming add-in only authentication has been set up and the access token has been obtained with a HTTP action and parsed into JSON, as per the previous blog post.
We now have actions after creating our document set to update the document set.
As of the time of writing this, Microsoft Flow does not include any SharePoint connector actions to create a document set in a document library, which is quite inconvenient.
Instead, we are left to deal with this using SharePoint’s REST API, which is not straightforward and proves to have a few gotchas to watch out for.
This is the overview of a Flow that will create a new document set in the Documents library, on trigger from a list item, just for the sake of a demo.
We will go through each action step by step below.
Below are simple extension methods for copying managed metadata field values from one field to another, using CSOM, assuming both fields are referencing the same term set.
Recently we were trying to update our company’s SharePoint Online intranet’s top navigation into displaying as a mega menu. As part of the change, there was also a need to clean up the links currently being displayed to be more usable to the staff users.
Because the current top navigation was using Structural Navigation, and we weren’t prepared to overhaul the entire site structure to accommodate the new navigation’s information architecture, we decided to switch to using Managed Navigation, and use a Navigation term set to define the links.
However, by default, new pages created under Managed Navigation will be added to the navigation automatically, and will be using Friendly URLs. This is set in the Navigation Settings for each site.
Because we’re trying to keep the structure of the top navigation controlled, and because the users are used to fully structured URLs as opposed to having friendly URLs, we would want both those options switched off across all our sub sites.
EDIT (2/02/2017): Added ability to specify the name of the navigation term set to connect to for Managed Navigation.
The PowerShell script below achieves that: Continue reading