The Lightning Data Service is a centralized data broker and data caching framework for record data in lightning components. By using the Lightning Data Service, components share a single copy of the record data and eliminates the need to refresh other components when a record is updated. The service is also pre-integrated into the Aura Storage Service for automatic offline caching. Come meet the team responsible for the service and learn how to integrate Lightning Data Service into your component.

1. Loading data without Apex/SOQL
in Lightning Components
Lightning Data Service: Eliminate Your Need to Load Records Through Controllers
​ Carolyn Grabill
​ SMTS Software Engineer
​ cgrabill@salesforce.com
​ @CarolynCodes
​
Kevin Venkiteswaran
PMTS Software Engineer
kvenkiteswaran@salesforce.com
@kevinv11n

2. ​ 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.
Safe Harbor

3. Agenda
• The Problem
• The <force:record> Component
• Demonstration + Code
• <force:record> in the Lightning Experience
• Roadmap
• Questions

4. The Problem
Many components need access to the same data

5. Data re-use across components
​ Highlights and Details
components display data
from the same Opportunity
record

6. Multiple SOQL calls for the same data
Highlights cmp
Name: Acme Anvils
Phone: (123) 456-7890
Details cmp
Name: Acme Anvils
Phone: (123) 456-7890
Address: 123 Main St
Amount: $500
Owner: Wile E. Coyote
Component
controller
Apex
controller SOQL
Component
controller
Apex
controller
SOQL
Client Server

7. Multiple SOQL calls for the same data
Highlights cmp
Name: Acme Anvils
Phone: (123) 456-7890
Details cmp
Name: Acme Anvils
Phone: (123) 456-7890
Address: 123 Main St
Amount: $500
Owner: Wile E. Coyote
Component
controller
Apex
controller SOQL
Component
controller
Apex
controller
SOQL
Client Server
Lots of custom code!

8. The <force:record> component

9. <force:record>
Standard component in “force”
namespace
(#SafeHarbor)

10. Shared
Record
Cache
<force:record
recordId=“001x00123”
fields=“Id,Name” />
Client
Server
Fetches record
Auto
SOQL
Automatic record loading

11. Multiple SOQL calls for the same data
Highlights cmp
Name: Acme Anvils
Phone: (123) 456-7890
Details cmp
Name: Acme Anvils
Phone: (123) 456-7890
Address: 123 Main St
Amount: $500
Owner: Wile E. Coyote
Component
controller
Apex
controller SOQL
Component
controller
Apex
controller
SOQL
Client Server

12. <force:record> handles loading records
Highlights cmp
Name: Acme Anvils
Phone: (123) 456-7890
Details cmp
Name: Acme Anvils
Phone: (123) 456-7890
Address: 123 Main St
Amount: $500
Owner: Wile E. Coyote
force:recordcontroller
force:record
controller
<force:record>
Shared
Record
Cache
Consolidated
requests
Client Server
<force:record>

13. <force:record>
No server trip on cache hits!
Highlights cmp
Name: Acme Anvils
Phone: (123) 456-7890
Details cmp
Name: Acme Anvils
Phone: (123) 456-7890
Address: 123 Main St
Amount: $500
Owner: Wile E. Coyote
force:recordcontroller
force:record
controller
Shared
Record
Cache
Client Server
<force:record>

14. ​
<aura:component controller="MyApexController">
​ <aura:attribute name="recordId" type="String" />
​ <aura:attribute name="record" type="SObject" />
<aura:handler name="change”
value="{!v.recordId}”
action="{!c.getRecord}"/>
​
<ui:inputText label="Record Name"
value="{!v.record.Name}"/>
​ </aura:component>
Simple refactor - BEFORE
​ Lightning Component Apex Controller
​
public with sharing class MyApexController {
​ @AuraEnabled
​ public static <SObject> getRecord(String recordId) {
​ return [SELECT Id, Name FROM <SObject>
WHERE Id = :recordId];
}
​ }

15. <aura:component>
​ <aura:attribute name="recordId" type="String" />
​ <aura:attribute name="record" type="SObject" />
<force:record recordId="{!v.recordId}"
targetRecord="{!v.record}"
fields="Id, Name"/>
​ <ui:inputText label="Record Name"
value="{!v.record.Name}"/>
​ </aura:component>
Simple refactor - AFTER
​ Lightning Component No Apex Controller Needed

16. • No Apex or SOQL
• Performance boost from client cache
• Data available offline
• Data consistency across components
• Automatic record refresh from server
• Automatic notification when record
changes
• Components can be entity-agnostic
Benefits of <force:record> over custom record loading

17. Demonstration

18. Campground custom object
​ Two important fields:
• Name
• Location

19. <force:record> in
Lightning Experience

20. ​ Opportunity List ​ Opportunity Record
+ hover on parent Account
​ Account Record
<force:record> in record browsing flow
​ Same Opportunity record in
list view and highlights
Same Account record in
preview and highlights
components

21. Page load time improved
​ Experienced page time (milliseconds) before and after highlights component
refactored to use <force:record>
0
200
400
600
800
1000
1200
1400
1600
Opportunities Accounts Users
Before <force:record>
After <force:record>
EPT(ms)

22. • No Apex or SOQL
• Performance boost from client cache
• Data available offline
• Data consistency across components
• Automatic record refresh from server
• Automatic notification when record
changes
• Components can be entity-agnostic
Benefits of <force:record> over custom record loading

23. Roadmap

24. • More optimizations to record
loading
• Proactive loading of records
• Advanced record loading with Aura
method load()
• Deleting records with Aura method
delete()
Future of <force:record>
• Saving records with Aura method
save()
• Securely storing draft records when
offline
• Supporting lists of records

25. Thank you

26. Questions?