Slides supporting the session. Talking about SharePoint Framework, powerapps, flow, azure functions and much more

1. Migrate your custom
components to the
SharePoint framework
SharePoint Saturday Toronto 2018
By: Vincent Biret

2. GOLD
Thank You Sponsors!
BRONZESILVER

3. 3
SharePint
SharePint
The Drake & Firkin
6982 Financial Dr, Mississauga, ON L5N 8J4

4. Vincent Biret
Passionate about development, community and technologies
@baywet
bit.ly/vince365
MVP Office Servers and Services
Azure and Office 365 developer @ 2toLead

5. SharePoint Framework being GA and reaching on prem means it’s time for key decisions
making
Targeted audience
Seasoned
SharePoint
developer
Project manager New to SharePoint Dev Decision Maker

6. Agenda
• Introduction
• Demo – the pirates treasures
management solution
• History
• The new stack
• Branding
• Provisioning
• Accessing data
• Line of business applications
• Batch jobs
• Conclusion

7. Ready?

8. The Pirates Treasures Solution
Demo

9. Our history

10. • Code executing server side
• User or service Context
• Bad code would break/slow down
SharePoint
• Deploying meant downtime
• Very little unit tests
SharePoint Full trust model has been around for a while but for obvious reasons we need
to transition from that
SharePoint Full Trust

11. The sandbox model was an attempt at fixing some of the problems but it was bringing
other issues on board
SharePoint Sandbox
• Still running on SharePoint server
• User Context only
• Bad code would not impact SharePoint too much
• No downtime during deployments
• Still no unit tests
• Limited access to OM
• Bad throttling could happen
• No more batch jobs

12. Add-ins were a good attempt to change directions but it was not taking into account the
general motion of the web
SharePoint add-ins (SharePoint Hosted)
• Running client-side
• User Context only
• Bad code doesn’t impact SharePoint
• But wait, iframe!!
• No downtime during deployments
• Still no unit tests
• Incomplete REST API
• Still no more batch jobs

13. Provider hosted add-ins proved to be efficient but still required a great knowledge of
SharePoint and had some complexity during deployments
SharePoint Add-ins (Provider Hosted)
•Running Server Side (not SharePoint)
•User and App Context
•Bad code doesn’t impact SharePoint
•No downtime during deployment
•Unit tests got easier
•CSOM and REST API
•Batch-jobs « capable »

14. And the general feeling of an average SharePoint developer was either bitterness or
frustration, especially when we compared with other developers and the tools they had.
SharePoint Add-ins/Sandbox

15. Some developers felt the winds turning and started gearing for that as well as changing
their approach.
Workarounds
•Content Script
Editor Webpart
•Display templates
•JSLink
•ScriptLink
•PowerShell

16. SharePoint
Framework –
The New Stack
A modern toolchain

17. Have you already seen these slides?
Question!
•Who has never heard about the
SharePoint Framework before this
talk?

18. The Short Version
• New Tools!
• Front End only!
• Local And Remote Workbench
• Closed source relying on open source
• First and third party

19. The product team is working to get a good on premises story so you can develop
solutions working on both environments with little to no changes
On Prem 2016 feature pack 2
•Brings SPFX webparts support
•Few limitations
•Custom API /MS Graph access
•Version 1.1 of SPFX
•No application extensions

20. To start new projects for SharePoint 2019 use the 1.7.0 generator
On Prem 2019 RTM
•Hosts version 1.4.0
•Modern pages
•SPFX Webparts
• (without AAD/Graph Client, connected props….)
•Application customizer
•Command Set customizer
•Field customizer

21. The webpart project, the column formatter
Demo

22. Branding

23. Microsoft is finally providing us a way to customize branding with the modern
experience, however don’t expect to have a much control as we used to.
Modern experience custom themes
•Central gallery to host
custom themes for
entire organization
•PowerShell commands
to manage and hide
out-of-box themes

24. Provisioning

25. You currently four options, limited feature, code, PNP template or site script in preview.
Microsoft is working on filling the gaps around those scenarios.
Provisioning options
• Most SPFX samples include code provisioning
• SPFX provides limited « feature framework » support for provisioning
• Pattern and Practices has made awesome work
• PnP Provisioning far better than code
• Site script to be executed based on templates
• Limited functionalities, can call a flow
• which can call a function and apply a PNP template

26. The provisioning template for Pirates Treasure App, and the site script for Pirate
Community
Demo

27. Accessing data

28. Integration with house made or third party systems was one of the key requirements in
building SPFX
Multiple API’s
• SharePoint REST API’s
• TypeScript libraries available, use those! (@pnp/sp, @types/SharePoint)
• Microsoft Graph
• Get access to much more data
• (no demo on that today, too much content)
• (Microsoft working on improving auth story)
• Or your own API (next slide)

29. Microsoft has wants to enable SPFX developers to build complex LOB applications
backed by MS or custom API’s
Custom API & Graph Access from SPFX
• SPFx components access custom Web APIs or MS Graph
• Additional permission scopes can be requested
• Bakes in the auth for you and provides a ready to use client
• Web APIs and Permission Scopes managed by Microsoft still available
• Admins can control additional access through per tenant AAD Service Principal
• Managed by SharePoint Online infrastructure
{
"WebApiPermissionRequest": {
"ResourceId": “GUID goes here",
"Scope": “GUID goes here",
}
"WebApiPermissionRequest": {
"ResourceId": “GUID goes here",
"Scope": “GUID goes here",
}
"WebApiPermissionRequest": {
"ResourceId": “GUID goes here",
"Scope": “GUID goes here",
}

30. Event receivers were some kind of predecessors of the modern webhooks, SharePoint
developers won’t be un-familiar with those.
Reacting on data events
• We used to have Event Receivers
• SP Provider Hosted Add-ins have RER’s (same thing
over HTTP)
• SharePoint API /MS Graph provides webhooks
support
• GA: Better integration between Azure Functions and
Microsoft Graph

31. Getting treasure Data
Demo

32. Line of business
applications

33. Azure Functions is also a valid approach for smaller processes, Flow is the most user
friendly, Logic Apps the most complete and Functions are simple for developers
Workflows
Azure Logic Apps

34. Prefer PowerApps for more complex corporate apps and Forms for simple forms or you
want to expose it to external users
Entry forms/simple apps

35. PowerApps Form
Demo

36. Flow workflow
Demo

37. Batch jobs

38. Azure functions are becoming Microsoft’s default answer to backend processing for cloud
enabled solutions
Azure functions

39. Azure function computing
Demo

40. Conclusion

41. Things are going really fast demonstrating Microsoft’s desire to close the gaps with on
premises solutions and provide modern solutions at every level
Modern tools reference
Purpose Workflows LOB Batch Events
Old tool SP Designer Front end
Components
TimerJob Event Receivers
New tool Flow/
Logic Apps
SPFX Azure Function RER’s
WebHooks
Purpose Augmentations Provisioning Branding Data Forms …
Old tool JSLink/ScriptLink/
Custom Actions
Feature Framework Design manager SSOM/
JSOM
InfoPath …
New tool SPFX Extensions:
Application,
Command Set, Field
customizers,
Column Formatting
PnP Provisioning / Site
Scripts
Custom Themes CSOM/
PNP-Core/
REST/
Graph/
Custom API
PowerApps/
Forms
…
We’re still
missing
custom page
layouts 

42. Conclusion
• We have a modern tooling
• The SharePoint Framework is one item of our pirate gear
• Add-ins are still relevant in some scenarios
• Leverage other tools to have a full spectrum
• SharePoint dev cost will decrease because bigger community
• SharePoint devs’ life just became better
• Happy coding 

43. Bit.ly/vince365 @baywet slideshare.net/VincentBIRET
Thanks!/Questions?
Vincent Biret
Office 365 and Azure
Developer, 2toLead
@baywet
Bit.ly/vince365