{"id":5796,"date":"2017-07-22T02:28:32","date_gmt":"2017-07-22T02:28:32","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=5796"},"modified":"2017-07-22T02:31:01","modified_gmt":"2017-07-22T02:31:01","slug":"lightning-data-services-standard-controller-for-lightning-components","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/lightning-data-services-standard-controller-for-lightning-components\/","title":{"rendered":"Lightning Data Service – Standard Controller for Lightning Components"},"content":{"rendered":"

If you have worked on Visualforce and started playing with\u00a0Lightning Component<\/strong>, you must have identified one important missing feature, which is\u00a0standard Controller.<\/strong><\/p>\n

Lets assume a scenario, you have two Lightning Components on Account page. One Lightning Component is used to show some fields and other component is used to edit same record.<\/p>\n

Problem 1 :<\/strong><\/p>\n

To achieve this, both Lightning components would invoke Apex method separately at the cost of performance, by issuing duplicate server calls. Below image depicts problem, where multiple Lightning component requests same content by making separate server calls.<\/p>\n

\"Lightning
Lightning Components – Duplicate Server Calls<\/figcaption><\/figure>\n

<\/p>\n

Problem 2 :<\/strong><\/p>\n

If data gets changed because of any component, Other component needs to be informed with the help of\u00a0Lightning Events.\u00a0<\/strong>Again, it would cost performance, as every Lightning component may listen that event.<\/p>\n

Problem 3 :<\/strong><\/p>\n

Data Inconsistency. It is quite possible that field updated but because of some defect \/ issue data not reflected everywhere.<\/p>\n

Problem 4 :<\/strong><\/p>\n

Developer needs to write Apex code and handler many scenarios like SOQL, Field level security, writing test classes and many more.<\/p>\n

To fix all of above problems, Salesforce introduced\u00a0Lightning Data Service\u00a0<\/strong>in Winter 17 as a pilot program and in Summer 17 (currently) its in Beta and expected to be GA in Winter 18.<\/p>\n

Advantages of Lightning Data Service<\/strong><\/p>\n

    \n
  • No need to write any Apex class<\/li>\n
  • No need to write SOQL<\/li>\n
  • Field level security and record sharing is inbuilt<\/li>\n
  • CRUD operation supported<\/li>\n
  • Shared cache is used by all standard and custom components<\/li>\n
  • Auto notification to all components<\/li>\n
  • Supports offline in Salesforce 1<\/li>\n<\/ul>\n

    In summer 17, we can use\u00a0force:recordData\u00a0<\/strong>Lightning component to declare\u00a0Lightning Data Service.\u00a0<\/strong>Following are important attributes<\/p>\n

      \n
    • RecordId<\/strong> – represents record to be loaded, deleted or updated. If its null then it indicates record to be inserted<\/li>\n
    • LayoutType<\/strong> – Layout from which field needs to be loaded. Currently it supports Full<\/em> or Compact<\/em><\/li>\n
    • Fields<\/strong>– If Layout does not contains field, we can use this attribute. Either one of\u00a0LayoutType\u00a0<\/em>or\u00a0Fields\u00a0<\/em>is mandatory.<\/li>\n
    • Target*<\/strong> – attributes starting with\u00a0target\u00a0<\/em>indicates values to be returned from Data Service. It can return record or error.<\/li>\n
    • Mode<\/strong> – Indicates Data Service should be used in View or Edit mode<\/li>\n
    • RecordUpdated<\/strong> – edit mode does not updates record by default, to update\u00a0target*\u00a0<\/em>attributes, use this method handler<\/li>\n<\/ul>\n

      Read record using Lightning Data Service<\/strong><\/p>\n

      Lets jump to source code, that could be used to read record with the help\u00a0Lightning Data Service<\/strong> without writing single line of Apex code.
      \n