OnemoreInCloud

We have looked on some basic code for Loading and Updating a record using Lightning Design System in my last blog post. Here we are going to work on creating and deleting a record in Lightning Component using Lightning Design System. 1. Creating a Record: For creating a new record using LDS we declare force:recordData without assigning a recordId unlike what we use to do with Load and Update record. And then we load a record template by calling the getNewRecord function on force:recordData and finally we handle saving data using saveRecord in our 'handleSaveRecord' function. Lightning Components Developer guide already have some basic code on creating a Contact record ( Reference Link ). We are going to extend that code a bit to first create a new Account record and then create a new Contact record by linking it to the Account that we created all in one single shot. Below we are going to create a new Lighting Component from Developer Console by navigating to File...

Lightning Data Service which is currently in Beta are Salesforce new alternative of using Apex in Lightning Components. Basically we can perform View, Save, Update, and Delete of any sObject record in Lightning Components without using Apex Code! Lightning Data Service also respect org sharing rules and FLS settings, records that are loaded in LDS are cached and shared across components and components accessing same record see significant performance change, since the record is loaded only once and it doesn't matter how many components are using it. When one component updates a record, the other component using it are notified and refresh it automatically. Resource Link: Lightning Data Service Lets have a look at how Lightning Data Service works in Lightning Components. 1. Loading a Record: This is the foremost simplest that we can do using LDS. Here force:recordData tag is what we use in our component and that is the key for our component to load record. Every force:...

Platform Events are new Salesforce publish-subscribe modal available from Summer '17 release. Salesforce platform is already powerful having Outbound Messaging, REST API, and Streaming API available and with this new Platform Events it makes it even better and reduces need of having point-to-point integrations. Resource Links: 1. Platform Events Developer Guide Link 2. Here is an awesome blog post Link from Christopher Marzilli with detailed explanation about Platform Events Lets see how platform events work with a small implementation: Step 1: In Lightning experience Platform Events can be accessed using Setup-->Data-->Platform Events and here we are going to create a custom Text_Message platform event which is very similar on how we create custom objects, the only difference that we see in the API name is that all platform events end with '__e'. Also I have two custom fields (Message_Id__c, and Message_Type__c) to process message related call. Pub...

With new Summer '17 release Salesforce introduced some new cool features for Lightning, I really liked below two features and they are my top pick for this blog posting 1. Standard Action Overrides 2. Lightning Data Service (Currently in Beta) Here is the Link for the article from Salesforce that has detailed explanation on each of these new features . Standard Action Overrides: Until Summer '17 release we only had an option to override standard actions with visualforce page but now we have an new option to override any of these four standard actions (New, View, Edit and Tab) with a custom lightning component, just by using one powerful line of code "lightning:actionOverride" . Lets just create a sample Lightning Component to override Account standard actions. Below is my Lightning Component Code: <aura:component implements="lightning:actionOverride,force:hasSObjectName,force:hasRecordId"> <aura:if isTrue="{!v.sObjectName...

Often we have a business use case from sales users to be able to capture Hours of Operation from their customers. Here we are going to build a reusable Lightning Component that we can place on any Object (Standard or Custom) detail page . Below are Code blocks that assembles to form our Lightning Component! Controller Class: Note** Just make sure to create a custom field with Api "Hours__c" on any sObject that you want to place this Component and update Hours. public class HoursOfOperation { @AuraEnabled public static String getUpdtHrs(String sObjName, String sObjId, String hrs) { try { //query string to pull specific record to update hours String qry = 'Select Id, Name, Hours__c From ' + sObjName + ' Where Id=\'' + sObjId +'\'' + ' Limit 1'; List<sObject> lstRcds = Database.query(qry); //check if above query returns atleast one record if (lstRcd...

Here in this blog, we are going to build a Lightning Component to display some standard field's data (Like Id, Name, CreatedByName, etc.,) for any given sObject that we are going to dynamically retrieve based upon record detail page on which our Lightning Component is placed! First we create a Class with a method to fetch records using sObject Name..... Below is the Controller Class to return sObject rows: 1: public class DynamicSObjectResults { 2: @AuraEnabled 3: public static List<Object> getObjRslts(String objName) { 4: String qry = 'Select Id, Name, CreatedBy.Name From ' + objName + ' Limit 6'; 5: List<Object> lstRcds = Database.query(qry); 6: return lstRcds; 7: } 8: } Now we create our Component and Component Controller Below is the Component Code: 1: <aura:component controller="DynamicSObjectResults" implements="force:hasRecordId,force:hasSObjectName,flexipage:availableForAl...

We looked at some basic attribute types in my last post . Now lets look at other attribute types that are available for Lightning Components development Object Types: This attribute type is declared as a type 'Object' and used for passing any type of event parameter's like Array of String, Array of Integer, etc.,           Object Type Attribute: <aura:attribute name="objTypeAttr" type="Object" default="['Test1', 'Test2']" /> Standard and Custom Object Types: This extends above attribute types in order to be able to use both Standard and Custom Objects           Standard Object Attribute: <aura:attribute name="standObj" type="Account" />           Custom Object Attribute: <aura:attribute name="cstmObj" type="Expense__c" /> Collection Types: We have Four collection attribute types for use [Type[], List, Set, and Map] Custom Apex Class Type...