Integrating Salesforce and SharePoint 2013


Published on

Today a number of organizations are working with both and SharePoint. There are several integration points between the two products to allow the seamless use of both technologies and increase end user experience.

While might be best for customer related information, SharePoint is suitable for unstructured customer intelligence types of information.

Learn from the experts at Netwoven who have been working with both technologies and have been busy integrating them for customers.

Presentation Preview:
• Review of scenarios for integration between and SharePoint 2013

• Registration process of users between salesforce and SharePoint

• Integration of leads, contacts and opportunities

• Review of Chatter integration with SharePoint search

Published in: Technology
1 Comment
  • You can see how to complete a Salesforce - SharePoint integration in less than 4 minutes with Documill Explorer at
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Integrating Salesforce and SharePoint 2013

  1. 1. Integrating Salesforce and SharePoint 2013 Netwoven Inc.
  2. 2. Audience Background • How many have some experience with: – basic Sales or other Apps – SharePoint 2013 Apps (SP or Cloud hosted) – Development on and SharePoint platforms: REST, OAuth, .NET, Apex
  3. 3. Inbound Integration Approaches • Inbound call to Salesforce from SharePoint: – Use SOAP or REST APIs • Leverage using toolkits such as the.NET / Java / PHP / Adobe Flex Toolkits, Mobile SDK – Authentication Pattern • Use password and security token to set up the connection (e.g. Secure Store) • Use OAuth 2.0: – Define a Remote Access app or Connected App in Salesforce – Use Consumer Key and Secret and one of the supported OAuth Flows to get access token
  4. 4. Inbound Integration Approaches • Web Server OAuth Authentication Flow:
  5. 5. Inbound Integration Approaches Sample REST request and JSON response:
  6. 6. Inbound Integration Approaches • Create custom web services in SFDC using Apex • Apex classes as REST web services m|StartTopic=Content%2Fapex_rest.htm|SkinName=webhelp
  7. 7. Demo: Inbound Integration • Scenario 1: – Create a Lead in Saleforce from SharePoint • Web Part leveraging SOAP APIs • Scenario 2: – Display Opportunities from Salesforce in SharePoint • SP Hosted App leveraging REST APIs
  8. 8. Outbound Integration Approaches • Outbound call from Salesforce to SharePoint: – Invoke external web services from Apex • Feed WSDL to "Setup“ -> "Apex Classes" -> "Generate from WSDL" – Outbound messaging to send SOAP-based messages to an external web service endpoint • Typically triggered by workflow rules on persisted objects • allows easy callbacks to the platform using the Soap API, as outbound messages contain the enterprise/partner endpoint URLs, as well a session ID token. • Retry feature • HTTP/S and X.509 certificate based security – Email integration for inbound and outbound messaging
  9. 9. Outbound Integration Approaches Outbound Messaging Flow
  10. 10. Outbound Integration Approaches • Setting up Endpoint on SharePoint – External Topologies for SharePoint • us/library/cc287908%28v=office.12%29.aspx • – E.g. Edge Firewall topology using Forefront UAG
  11. 11. Demo: Outbound Integration • Demo Scenario: – Create a new project site in SharePoint when a new Lead is created in Salesforce • Other Useful Scenarios: – Launch SharePoint Workflows based on defined changes in Salesforce – Keep Tasks / Contacts / User Profiles in sync
  12. 12. Search Integration • Surfacing Salesforce content in SharePoint search results – Crawl Salesforce (e.g. Chatter) using custom crawl connector – User mapping and attaching ACLs for non-public content non-trivial – Map managed properties to crawled properties and optionally specify other settings (e.g. refinable) • Demo: Search of public Chatter feed
  13. 13. Appendix Background Information
  14. 14. Salesforce Introduction • On-Demand, Multitenant Applications that Run in the Cloud • Variety of APIs to integrate – SOAP API and REST API, Bulk API, Streaming API, Metadata API, Chatter API – htm&language=en_US • Sign up for Developer Editon account at – Simple Point and Click application tm
  15. 15. SharePoint 2013 Apps Introduction • Provide fully immersive experience and optionally extend existing UI or provide embeddable parts for pages • Apps vs classic Farm or Sandbox Solution – Future SharePoint upgrades, integrate cloud resources , easy discovery and installation process, leverage alternate standards like MVC or Java/PHP
  16. 16. SharePoint Apps: Hosting Options • Apps cannot contain custom code that runs on the SharePoint server – Not a significant limitation - custom business logic moves either "down" to the client device or "up" to the cloud • Cloud Hosting Option(Provider Hosted or Autohosted) – App uses SharePoint CSOM or REST endpoints to connect to SharePoint – Use STS’s OAuth support to access SP resources on behalf of the user – Perform CRUD operations on SharePoint content and Leverage SP capabilities (Docs, Search, Taxonomy, Workflow, Social) – Server side code
  17. 17. SharePoint Apps: Hosting Options