This post will contain whatever handy information I come across for utilizing the SharePoint REST APIs with Microsoft Flow.
Next in this series on the SharePoint Framework are extensions. According to docs.microsoft.com, SPFx Extensions allow for the customization of multiple facets of the SharePoint experience. I’ll focus on differences I made while following the online tutorial and my observations on capabilities and impacts of SPFx Application Customizer extensions.
So, you have multiple projects and one or more of them have dependencies (or just plain don’t work) on certain versions of node? What to do? Node Version Manager (NVM) allows you to install and switch between them “with ease” (quotes added as I’m writing this blog post as I get it installed for the first time myself… lets see just how easy it is!).
Today I decided that it was time I learned how to build SharePoint Framework (SPFx) webparts. Easy enough right? Find the right tutorial online, follow instrucitons, hello world! Let’s get started.
- SharePoint 2013
- You’ve created some site columns, added them to a content type, then added that content type to a list/library.
- You add some test data.
- Run a full crawl.
- Create managed properties, mapping them to the crawled properties.
- Run another full crawl (to populate the managed properties)
- Managed properties on search results are missing.
What do you do now?
We ran across an issue in a test environment where we were unable to add items to a list, or a document library. However, you could use Windows explorer view to upload a document.
The specific error message seen was:
The server was unable to save the form at this time. Please try again.
Ran across an error while proving out a new Muhimbi PDF Converter Services install. I haven’t seen it’s like anywhere online, but managed to find a resolution.
In two scenarios, errors wer observed when using K2 designer within SharePoint 2013.
Working with K2 support, a resolution was found to this.