Lightning Components Developer Guide

What is the Lightning Component Framework?
Quick Start
Creating Components
Using Components
Communicating with Events
Creating Apps
App Overview
Designing App UI
Creating App Templates
Developing Secure Code
Styling Apps
Using JavaScript
JavaScript Cookbook
Using Apex
Lightning Data Service (Developer Preview)
Loading a Record
Saving a Record
Creating a Record
Deleting a Record
Handling Record Changes
Handling Errors
Considerations and Limitations
Lightning Data Service Example
force:recordPreview
SaveRecordResult
Controlling Access
Using Object-Oriented Development
Caching with Storage Service
Using the AppCache
Distributing Applications and Components
Debugging
Reference
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Considerations and Limitations

Lightning Data Service is simple to use, and quite powerful. However, it’s not a complete replacement for writing your own data access code. Here are some considerations to keep in mind when using it.

Lightning Data Service is available as a developer preview. Lightning Data Service isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. You can provide feedback and suggestions for Lightning Data Service on the IdeaExchange.

Note

During the developer preview, you can only use Lightning Data Service in a Developer Edition org. You can’t package or deploy code that uses Lightning Data Service.

During the developer preview Lightning Data Service is accessed using the force:recordPreview tag. This tag name is temporary, and will change in the future. And, although it’s not planned, we reserve the right to make other backwards-incompatible changes with Lightning Data Service.

Lightning Data Service is only available in Lightning Experience and Salesforce1. Using Lightning Data Service in other containers, such as Lightning Components for Visualforce, Lightning Out, or Communities isn’t supported. This is true even if these containers are accessed inside Lightning Experience or Salesforce1, for example, a Visualforce page added to Lightning Experience.

Lightning Data Service supports primitive DML operations. That is, create, read, update, and delete (or CRUD). It operates on one record at a time, which you retrieve or modify using the record ID. There’s currently no support for relationship traversal, working with collections of records, or for querying for a record by anything other than the record ID. If you need to support higher-level operations, or multiple operations in one transaction, you’ll need to use standard @AuraEnabled Apex methods.

Lightning Data Service shared data storage provides notifications to all components that use a record, whenever any component changes that record. It doesn’t notify components if that record is changed on the server, for example, if someone else modifies it. Records changed on the server aren’t updated locally until they’re reloaded.