SP PnP PowerShell/Core 5-31

2:38 – Announcements

5:31 – PnP Provisioning Schema

  • https://github.com/SharePoint/PnP-Provisioning-Schema
  • Resolved most of the issues reported in the Schema repo
  • Added information about when items were added to the schema
  • Added ability to define site webhooks, not currently available in the engine because no SharePoint support
  • Client-Side Pages
  • Template Culture Info for the site we are provisioning
  • Scope attribute allows us to understand what kind of target we have for template, root site, sub web
  • Enable tree view for navigation for the site.
  • Role assignment ability to remove out of the box role assignment and add new role assignments, implemented in the schema but not in engine. Schema changes need to come before engine updates
  • Added Key column attribute for data import to prevent duplicate items being added as part of the provisioning
  • Update behavior to define how to handle existing items
  • Can define custom webhooks when list is created, webhooks last on the list for 6 months then need to be re-applied.
  • IRM Settings to define IRM rules
  • No Crawl attribute to define that the items will not be crawled by search
  • List experience to define choice of modern, classic experience, or let SharePoint decide
  • Default display/new/edit forms URL
  • Is application list to define if it is a application specific list
  • Ability to add property bag values to a folder
  • Flag to clear list of content types for document sets
  • List instance field refs can be added to add or remove fieldrefs from lists
  • Target file name option to define the name of the file instead of going with the default name of what it exists as in the template site
  • Image renditions support added
  • Site collections term group update behavior to allow overwrite existing term groups
  • Two releases in June to help implement the schema items into the engine
  • After June 2017 release all of the -spo commandlets will be removed

     

33:53 – Office365 Dev CDN

  • Public and Private CDN

  • E3+, CDN is included in your subscription
  • Public CDN Logical Flow

  • Anonymous access for public CDN is not your content, it is JS/images/CSS. Shouldn’t normally contain confidential information
  • Private CDN Assets are security controlled
  • Private CDN Logical Flow

  • CDN functionality disabled by default
  • Instructions to enable CDN

  • Demo
  • Public CDN is validated by referrer

 

58:11 – Q & A

  • Public CDN only available for your tenant

     

 

Office Dev PnP – SPFx/JavaScript Special Interest Group 4/27/17

A friend of mine mentioned an idea to me that I really liked and I could definitely see the need for. He suggested that, at the moment, there is no good synopsis of what happens in the Office Dev Patterns and Practices calls that happen on a regular basis. He said he didn’t have the time to take this on but I was free to if I wanted, thank you Eric. I’ll do my best to get a synopsis published the same day as the calls. I’ll run a synopsis of all the calls for PnP.

What is Office Dev PnP?

The Office Dev PnP is an open source, community driven initiative that is backed by Microsoft and Microsoft resources. The goals are to provide tools, samples, and guidance on developing for SharePoint and Office365. There are a lot of samples in the PnP GitHub Repository. There are other repositories in this area as well if you want to contribute to the PnP.

 

Special Interest Group Calls

There are a few Special Interest Group calls relating to different areas of the Office Dev PnP. Eric Overfield does a pretty good job of explaining what these calls are and how to join them so check out his article, Participating in the SharePoint / Office 365 Dev Patterns and Practices (PnP) Community Initiative.

 

April 27, 2017 SPFx/JavaScript SIG Call

4:17 – Opportunities to Participate

  • Demo an SPFx Webpart
  • Demo sp-pnp-js in a Project
  • Contribute on GitHub
  • Provide Feedback

5:14 – PNP-Core Updates

  • 2.0.4 Released – Fixes SPFx blocking bug
  • Doing beta releases now – sp-pnp-js@beta
  • Checkout wiki and developer guide
  • Search Improvements
  • Updated React SPFx samples to work with sp-pnp-js
  • Report issues in the GitHub issues list with enough details
  • Graph support in process though early stages, discussion in issues list

11:58 – SharePoint Framework Updates

17:30 – What engineering is working on

  • New capabilities
    • Web part to web part connections – sending events
    • Modern UI extensions
      • Modern JSLink and UserCustomAction
      • Additional Yeoman templates
    • Workbench improvements
    • SPFx improvements
    • Numerous topics for both online and on-premise.
    • Working on on-premise for 2016, not 2013 at first depending on demand
  • Other
    • SharePoint document consolidation to single location eventually to docs.microsoft.com/sharepoint
      • MSDN docs will go away because the platform is super old
      • All MSDN SharePoint docs will be moved to dev.office.com/sharepoint then to final location

20:34 – Demo Vesa SPFx VS Extension http://aka.ms/spfx-vs-extension

  • Still using Yeoman for templating
  • Early alpha release available
  • Other releases coming soon
  • Template shows under the Office/SharePoint section for new project
    • Launches wizard
    • Can click generate or go to Advanced to see/modify the full yeoman command
      • -skip-install switch to skip the npm install
  • Can add more web parts
    • Add new item to project
    • Select Office/SharePoint – SharePoint Framework
    • SPFx Web Part
    • Prompted with smaller wizard
  • F5 launches gulp serve
  • Does not introduce any new templates, just uses the yeoman templating
  • Missing Features
    • Native debugging
  • This is for those that want to do SPFx in Full Visual Studio instead of VS Code

30:09 – Demo Sebastien RiotJS

  • List Viewer Web Part

Available in Github https://github.com/sebastienlevert/spfx-riot-list

  • Need riot and riot-typescript added to package.json
  • tsconfig.json add experimental decorators to true
  • Extend RiotClientSideWebPart
    • Handles the mounting to the DOM
  • Riot allows separation of view and component like Angular
  • Using await/async from TypeScript
  • Using PnP getAs ODataEntity
  • Must call update to update the ui after asynchronous calls
  • Riot also includes a router

46:08 – Open Discussion

  • Any headway with gov farm support for SPFx?
    • No dates
    • Wrong people to ask
    • Right way to find right people to ask would be to have the gov client to contact the gov farm people.

Guidance on calling external APIs, WebApi/Azure Functions early next week

Next Meeting May 11th.