As your Salesforce implementations become more complex, working with multiple orgs becomes a standard hurdle. Connecting with the correct data, at the correct time, when you have multiple orgs can be very difficult. Join us as we explore the new Lightning Connect: Salesforce Adapter. We'll examine how Admins can connect multiple orgs together, how data can be shared between those orgs, and how you can continue to build a complete view of your customers.

1. Blurring the Boundaries Between Salesforce Orgs
Jay Hurst
Director, Product Management
jhurst@salesforce.com
@extraidea
Alexey Syomichev
Architect – Messaging & Integration
asyomichev@salesforce.com
@asyomichev

2. Safe Harbor
Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize
or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the
forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any
projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding
strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or
technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for
our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate
of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with
completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability
to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our
limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential
factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year
and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are
available on the SEC Filings section of the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and
may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are
currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

3. Jay Hurst
Director - Product Management, Salesforce
jhurst@salesforce.com
@extraidea

4. Alexey Syomichev
Architect – Messaging & Integration, Salesforce
asyomichev@salesforce.com
@syomichev

5. Connecting Salesforce Orgs
Many customers are facing a set of challenges around sharing data
between orgs.
Raise your hand if you:
• Have multiple Salesforce orgs and are trying to share data between
them
• Have tried to integrate between orgs, but have had data consistency
issues
• Have a need to keep a single source of truth for your shared records

6. Sharing Data between Orgs

7. Many Attempts to Solve the Problem
Custom Integrations
• Partners and integrators have developed synching tools to replicate data through the API
• Generally very customized and may result in time spent in data reconciliation
Salesforce-to-Salesforce (S2S)
• Built to provide customers a reliable way to share data with their partner resellers
• Initially focused on Lead sharing
• Records are copied from the provider org to the subscriber org
• This results in multiple copies of the same records
Cross-Org Data Sharing (XOrg)
• Built to allow orgs to define a package with which objects they wanted to share
• Package could be versioned and distributed
• Records were virtualized at run time and accessed by a single user per connection
• Virtualization was very custom, and support for all Salesforce SObjects was slow to develop

8. Lightning Connect: Salesforce Connector

9. Lightning Connect: Virtualizing External Data in Salesforce…
Lightning Connect Data Virtualization FrameworkMetadata
Store
Custom
Connectors
OData
Connector
Data Source in Cloud
Object
UI
Apex VF Page SOQL SOSL
Report
Analytics
Salesforce.com Environment
Secure Agent
Apex External Data Connector Framework
Salesforce Connector
for Lightning
Connect
API
…Including data from other Salesforce Oganizations

10. Salesforce Connector - Cross-Org data access by reference
Allows one Salesforce org (consumer) to read data from another (provider)
• Data completely resides in the provider org and is virtualized on the consumer when viewed
• Setup for the connection is entirely declarative
• Consumer admin determines what objects are referenced from the provider
• Provides the ability to create a single data source for multiple orgs

11. Salesforce Connector Features
• External Data Source Definition
• Through the UI, the consumer org can create a connection to the provider org
• Consumer provides the instance to connect to, the authentication type, and the user to authenticate as
• External Object Definition
• The consumer org chooses which objects they want to connect to from the provider org
• All objects that are readable to the running user are available to be used as an external object
• Consumer Syncing
• The consumer org can choose when to sync with the provider.
• All fields are synched during the Validate and Sync process
• UI Access
• The consumer can create page layouts and list views against the external objects
• API Access
• Once the metadata is synched, the consumer can access the provider data through the API

12. Supported Features
• All API visible Salesforce SObjects are supported
• The connection user determines which SObjects can be seen at sync and at runtime
• Records are Read Only
• Most Field Types are supported
• Rich Text Area, AutoNumber, and Encrypted Text Fields are not supported
• List Views, Page Layouts, and Related Lists for synched External Objects
• Create Chatter Feeds in the subscriber org for synched objects
• External Objects and Records are available through Salesforce1
• External Object Records are available through Global Search
• API support for synched objects
• SOQL and SOSL support
• Apex and Visualforce Support for synched objects

13. Salesforce Connector vs. Salesforce to Salesforce
Salesforce to Salesforce
• Feature is GA
• Data is copied between orgs
• Data is access directly in each org separately
• The receiving org can write to their data copy
• Once the data is copied, they may become out of
sync (requires two way sync)
• Custom and Standard SObjects are supported
• Most fields types are supported
• All platform features are supported (the records
exist in the subscriber org)
Salesforce Connector
• Feature is GA
• Data is accessed by reference
• Data access is through the API
• Synched objects are read only in subscriber
• Provider can control the state of the data (the
provider is the only true copy of the data)
• All SObjects are Supported
• Most field types are supported
• Some platform features (Workflow, Triggers,
Validation Rules) are not supported

14. Demo

15. Roadmap
CRUD Operations on external data
• Enable consumer orgs to be able to Create, Update and Delete data
in the producer org
Custom Report Type
• Enable consumer orgs to be able to run custom reports against
records in the producer org
Workflows, Triggers and Validation
• Enable consumer orgs to fire Workflow, Triggers and Validation Rules
against records in the producer org

16. What did we Learn?
Past strategies
Info on current GA
Demo
• Showed the setup
• Showed the layouts
• Showed indirect Lookup
• Showed external lookup
• Showed data is accessed real time
Roadmap

17. Q & A

18. Share Your Feedback, and Win a GoPro!
3
Earn a GoPro prize entry for
each completed survey
Tap the bell to take a
survey2Enroll in a session1

19. Thank you