Lightning Data Service is used to load, create, edit, or delete a record in Lightning component, without using server side Apex code. Lightning Data Service takes care of sharing rules and field-level security.
Below are changes to LDS in Summer'17 Release
New JSON Format is:
{
"apiName": "Account",
"fields": {
"AnnualRevenue": {
"displayValue": null,
"value": null
},
"BillingCity": {
"displayValue": null,
"value": "Toronto"
},
"CreatedBy": {
"displayValue": "Admin User",
"value": {
"apiName": "User",
"fields": {
"Id": {
"displayValue": null,
"value": "005R0000000IXV3IAO"
},
"Name": {
"displayValue": null,
"value": "Admin User"
}
},
"id": "005R0000000IXV3IAO",
"recordTypeInfo": null
}
},
"CreatedById": {
"displayValue": null,
"value": "005R0000000IXV3IAO"
}
}
}
The following example shows the targetFields attribute within the force:recordData component.
<force:recordData aura:id="skss" recordId="{!v.recordId}" layoutType="{!v.layout}"
fields="{!v.fieldsToQuery}" mode="VIEW" targetRecord="{!v.record}"
targetFields="{!v.simpleRecord}" targetError="{!v.error}" />
For complete understanding of LDS along with code, refer Lightning Data Services : Way to perform operation on records without using server-side Apex class blog
PASSING LIGHTNING COMPONENT ATTRIBUTE VALUE FROM VF PAGE
FIRE LIGHTNING EVENTS FROM VF PAGE
DYNAMICALLY CREATING AND DESTROYING LIGHTNING COMPONENTS
RAISING AND HANDLING CUSTOM EVENTS IN sALESFORCE lIGHTNING
WHY TO USE DESIGN RESOURCE AND HOW TO ADD DYNAMIC OPTION TO DATASOURCE
PASSING LIGHTNING COMPONENT ATTRIBUTE VALUE FROM VF PAGE
PASSING INNER WRAPPER CLASS TO LIGHTNING COMPONENT
LIGHTNING COMPONENT FOR RECORDTYPE SELECTION FOR ANY SOBJECT
CUSTOM COMPONENT TO SHOW/HIDE SPINNER IMAGE
Below are changes to LDS in Summer'17 Release
- force:recordPreview has been deprecated. Now use force:recordData instead of force:recordPreview.
- targetFields attribute is added to force:recordData, which is populated with a simplified view of the record’s fields. targetFields is automatically updated a record changes.
- The targetRecord attribute of force:recordData, has been updated to return records in a new format.
Old JSON format was :
{
{
"AnnualRevenue": null,
"BillingCity": "Toronto",
"CreatedById": "005R0000000IXV3IAO",
"CreatedBy.Name": "Admin User",
"CreatedBy": {
"Id": "005R0000000IXV3IAO",
"Name": "Admin User",
"sobjectType": "User"
}
}
New JSON Format is:
{
"apiName": "Account",
"fields": {
"AnnualRevenue": {
"displayValue": null,
"value": null
},
"BillingCity": {
"displayValue": null,
"value": "Toronto"
},
"CreatedBy": {
"displayValue": "Admin User",
"value": {
"apiName": "User",
"fields": {
"Id": {
"displayValue": null,
"value": "005R0000000IXV3IAO"
},
"Name": {
"displayValue": null,
"value": "Admin User"
}
},
"id": "005R0000000IXV3IAO",
"recordTypeInfo": null
}
},
"CreatedById": {
"displayValue": null,
"value": "005R0000000IXV3IAO"
}
}
}
The following example shows the targetFields attribute within the force:recordData component.
<force:recordData aura:id="skss" recordId="{!v.recordId}" layoutType="{!v.layout}"
fields="{!v.fieldsToQuery}" mode="VIEW" targetRecord="{!v.record}"
targetFields="{!v.simpleRecord}" targetError="{!v.error}" />
For complete understanding of LDS along with code, refer Lightning Data Services : Way to perform operation on records without using server-side Apex class blog
More Blogs>>:
LIGHTNING DATA SERVICES
PASSING LIGHTNING COMPONENT ATTRIBUTE VALUE FROM VF PAGE
FIRE LIGHTNING EVENTS FROM VF PAGE
DYNAMICALLY CREATING AND DESTROYING LIGHTNING COMPONENTS
RAISING AND HANDLING CUSTOM EVENTS IN sALESFORCE lIGHTNING
WHY TO USE DESIGN RESOURCE AND HOW TO ADD DYNAMIC OPTION TO DATASOURCE
PASSING LIGHTNING COMPONENT ATTRIBUTE VALUE FROM VF PAGE
PASSING INNER WRAPPER CLASS TO LIGHTNING COMPONENT
LIGHTNING COMPONENT FOR RECORDTYPE SELECTION FOR ANY SOBJECT
CUSTOM COMPONENT TO SHOW/HIDE SPINNER IMAGE
This was a lovely blog post
ReplyDelete