Custom Lookup Lightning Component

Custom Lookup Lightning Component

Lookups are very important components in Salesforce. Salesforce vide inputfield to handle the Lookup component out of the box. But they come with there own set of limitations. So today I have created a basic Lookup Lightning Component which we can easily use with our existing apps or component to make it work.


I tried to keep this component as simple as possible so I did not use any event to communicate data between component. Instead we have used two way binding to pass data between component. Also we have not used any third party library and only SLDS is used. So it will work in Locker service and can pass security review as well.

Here is the complete code.


Now this component support Dynamic Icon , Required, Dynamic Label. I will also add many other feature in this component to make it more better. You can also download complete code from Github repo as well.

Did you like this component or want to add any feature, report any bug. Just let me know in comments section. Happy Programming :).



Display Generic sObject in Lightning

Display Generic sObject in Lightning


In the last post we study how we can iterate map in Lightning. There is one more thing which we face many time is dynamic field binding. Visualforce wit dynamic field binding we can dynamically create field instance but in lightning this is a major limitation.

Today we will see how we can use dynamic sObject binding in visualforce. For this we will create a sample component to display dynamic fields.

Here we will create app to get Object details. for demo I have select Account object we can select any object here. We can also select any fields here including the parent fields(cross reference field).

Now we will pass the object and field name in another component. Where we will display them on UI.

So here we are using JavaScript to to get data from the field. This is similar of what we have done in Map Iteration post.

To display on UI I am using lightning:formattedText we can also use any other component as well.


You can find the complete code here as well.

DO you want to add anything let me know in comments section. Happy programming 🙂

Iterate Map In Lightning

Iterate Map In Lightning

Usages of Lightning is increasing day by day. We face many challenge while doing development in Lightning.  One of the challenge which I face recently is we can’t iterate map in lightning using aura:iteration.  Map is commonly used collection type which provide Key value pair to easy binding of data.

Today I will shae a code sample of how we can iterate map in Lightning easily.

First we need a Controller which will return Map to us.


Next we will create an APP to display It on UI.

We can easily iterate map in Javascript. So in App controller we will iterate this Map and will create a List. Now we can  easily iterate that List in the app.

This is the output which we will get.

Map Iteration

Do you like the post. Or want to say anything. Please let me know in comments section.

Deploy the Package Code using SFDX

Deploy the Package Code using SFDX

Hello Everyone, In the last post we have discussed  how we can quickly setup the SFDX. We also use the basic command to move code using SFDX, create scratch org and use them for development.

Today we will cover If we are an ISV partner so how we can best use the SFDX and how we can move our package code into scratch org to continue with development and effectively use the SFDX.

First we need to authenticate our dev hub org.  Then we will create a new project to store our project metadata.

sfdx force:project:create -n MyPkgProject

cd MyPkgProject

Now we need to authentic our package org to take a backup of code.

sfdx force:auth:web:login -a MyPkg

Now make a directory to store the metadata and fetch the data from source.

sfdx force:mdapi:retrieve -s -r ./dummy -u MyPkg -p TestData

SFDXV2 1.png

This will gives us a zip file. Which we need to unzip. Next we will convert this metadata into SFDX format.

sfdx force:mdapi:convert -r ./dummy

Next we will create a new scratch org to move our metadata there.

sfdx force:org:create -s -f config/project-scratch-def.json -a pkgscratchorg

And when our scratch org is created we are ready to push our code into new scratch org.

SFDXV2 2.png

sfdx force:source:push

And when we get the success message we can open the org and can continue with our development.

sfdx force:org:open

So within few steps we can easily move our packaging code to SFDX format and can use all the benefit of SFDX.

Did you have anything to add, Let me know in the comments section. Happy programming 🙂


SFDX: A New Way of Development

SFDX: A New Way of Development

In Dreamforce Salesforce announce a new development tool SFDX. It’s a new way of development where we create a temporary org for the development; In SFDX we call them Scratch org. The idea is similar with Trailhead org where we create new org for challenge and once completed we can delete them as well.


With recent Salesforce releases we are getting updates related to SFDX and as its GA now so I did a quick check to see how it works and how we can best use it. The main part SFDX cover is related to Source control. With SFDX and many VCS (like github) we can easily do version control. SFDX is a command line tool but we can also use Visual studio plug-in to do the development. Today we will cover how we can quickly setup the SFDX up and running.

First you need a Dev Hub org. You can signup for a trial org from here.

Windows 32-bit
Windows 64-bit
Debian/Ubuntu 64

Download the archive from one of the URLs in the manifest, extract the archive, then run the ./install script.

Debian/Ubuntu x86

Then we can download CLI from here and we need to make sure we have properly installed it.

Then first we need to do login in our devhub org and authenticate the SFDx  to use that.

sfdx force:auth:web:login -d -a DevHub


You can create alias for org so that it is easy to remember and can quickly type them in CLI. We can use sfdx force:org:list  to see all active org.

First you need to create a local project where you will store all your metadata.

sfdx force:project:create -n MyOrg

mage 2.png


Next we will create a new scratch org where we do all our development.

sfdx force:org:create -s -f config/project-scratch-def.json -a MyScratchOrg

mage 3.png

  • The -s option indicates that we want this scratch org to be the default org for this project.
  • The -f option is the path to the project scratch org configuration file.

We can also export data using SFDX to populate our new org with data.

sfdx force:data:tree:export -q "SELECT Id,Name FROM Account" -d ./data

To Import this data we can use import command.

sfdx force:data:tree:import --sobjecttreefiles data/Account.json

We can also create classes, pages, lightning component using SFDX

sfdx force:apex:class:create -n AccountController -d force-app/main/default/classes

sfdx force:lightning:component:create -n AccountLocator -d force-app/main/default/aura

To Push and Pull data from,to scratch org we use Push and Pull commands.

sfdx force:source:pull

fdx force:source:push

We can use sfdx force:org:open -u OrgAlias command to open any org in browser

To generate password for any scratch org we use the password generate command

sfdx force:user:password:generate -u OrgAlias

We can also get list of all org using list command

sfdx force:org:list

mage 4.png

To get current org details we can use org:display command.

sfdx force:org:display -u MyScratchOrg (OrgAlias)

mage 5.png

So these all are basic steps using which we can easily configure SFDX in no time. In next post we will cover How we can use Git with SFDX and How we can use Visual Studio to develop the SFDX

Did you like the post or want to add anything. Let me know in comments section. Happy Programming. 🙂




Lightning Data Service: Loading Data without Apex Continue

Lightning Data Service: Loading Data without Apex Continue

In the last post we study about Lightning Data service and how we can use that for Load the data and Save records.


In previous post we learn about few new tags force:recordData which is base tag for LDS.  We also get saveResult in controller using that we can get State of the operation and can display different message to user based on different state. LDS also support Data caching so if user lost the connection while process data LDS save that in cache with status Draft. In this part we will continue with creating a new record using template.

Creating a Record

To create a record using Lightning Data Service,We need to declare force:recordData without assigning a recordId. Next, load a record template by calling the getNewRecord function on force:recordData. Finally, apply values to the new record, and save the record by calling the saveRecord function on force:recordData.

  1. Call getNewRecord to create an empty record from a record template. We can use this record as the backing store for a form or otherwise have its values set to data intended to be saved.
  2. Call saveRecord to commit the record. This is described in Saving a Record.

Create an Empty Record from a Record Template

To create an empty record from a record template, we don’t need to set a recordId on the force:recordData tag. Without a recordId, Lightning Data Service doesn’t load an existing record.

In our component’s init or another handler, call the getNewRecord on force:recordData.

Example: Creating a Record


<aura:component implements="flexipage:availableForRecordHome, force:hasRecordId">

<aura:attribute name="newContact" type="Object"/>

<aura:attribute name="simpleNewContact" type="Object"/>

<aura:attribute name="newContactError" type="String"/>

<aura:handler name="init" value="{!this}" action="{!c.doInit}"/>

<force:recordData aura:id="contactRecordCreator"




targetError="{!v.newContactError}" />
<div class="slds-page-header" role="banner">
<p class="slds-text-heading_label">Create Contact</p>

<!-- Display Lightning Data Service errors -->

<aura:if isTrue="{!not(empty(v.newContactError))}">
<div class="recordError">

<ui:message title="Error" severity="error" closable="true">



<!-- Display the new contact form -->
<div class="slds-form_stacked">

		<lightning:input aura:id="contactField" name="firstName" label="First Name"

value="{!v.simpleNewContact.FirstName}" required="true"/>

		<lightning:input aura:id="contactField" name="lastname" label="Last Name"

value="{!v.simpleNewContact.LastName}" required="true"/>

		<lightning:input aura:id="contactField" name="title" label="Title"

value="{!v.simpleNewContact.Title}" />

		<lightning:button label="Save contact" onclick="{!c.handleSaveContact}"

variant="brand" class="slds-m-top_medium"/></div>

This component doesn’t set the recordId attribute of force:recordData. This tells Lightning Data Service to expect a new record. Here, that’s created in the component’s init handler.



doInit: function(component, event, helper) {

// Prepare a new record from template


"Contact", // sObject type (objectApiName)

null, // recordTypeId

false, // skip cache?

$A.getCallback(function() {

var rec = component.get("v.newContact");

var error = component.get("v.newContactError");

if(error || (rec === null)) {

console.log("Error initializing record template: " + error);



console.log("Record template initialized: " + rec.sobjectType);




handleSaveContact: function(component, event, helper) {

if(helper.validateContactForm(component)) {

component.set("v.simpleNewContact.AccountId", component.get("v.recordId"));

component.find("contactRecordCreator").saveRecord(function(saveResult) {

if (saveResult.state === "SUCCESS" || saveResult.state === "DRAFT") {

// record is saved successfully

var resultsToast = $A.get("e.force:showToast");


"title": "Saved",

"message": "The record was saved."


} else if (saveResult.state === "INCOMPLETE") {

// handle the incomplete state

console.log("User is offline, device doesn't support drafts.");

} else if (saveResult.state === "ERROR") {

// handle the error state

console.log('Problem saving contact, error: ' +


} else {

console.log('Unknown problem, state: ' + saveResult.state + ',

error: ' + JSON.stringify(saveResult.error));






Deleting Record

To delete a record using Lightning Data Service, we need to call deleteRecord on the force:recordData component, and pass in a callback function to be invoked after the delete operation completes.  deleteRecord takes one argument, a callback function to be invoked when the operation completes. This callback function receives a SaveRecordResult as its only parameter. SaveRecordResult includes a state attribute that indicates success or error, and other details we can use to handle the result of the operation.



<aura:component implements="flexipage:availableForRecordHome,force:hasRecordId">

<aura:attribute name="recordError" type="String" access="private"/>

<force:recordData aura:id="recordHandler"




recordUpdated="{!c.handleRecordUpdated}" />

<!-- Display Lightning Data Service errors, if any -->

<aura:if isTrue="{!not(empty(v.recordError))}">
<div class="recordError">

<ui:message title="Error" severity="error" closable="true">


<div class="slds-form-element">


label="Delete Record"


variant="brand" /></div>

For minimum delete process we don’t need any other fields but if we want to display data as well that we can pass them as parameter.



handleDeleteRecord: function(component, event, helper) {

component.find("recordHandler").deleteRecord($A.getCallback(function(deleteResult) {

// NOTE: If we want a specific behavior(an action or UI behavior) when

this action is successful

// then handle that in a callback (generic logic when record is changed

should be handled in recordUpdated event handler)

if (deleteResult.state === "SUCCESS" || deleteResult.state === "DRAFT") {

// record is deleted

console.log("Record is deleted.");

} else if (deleteResult.state === "INCOMPLETE") {

console.log("User is offline, device doesn't support drafts.");

} else if (deleteResult.state === "ERROR") {

console.log('Problem deleting record, error: ' +


} else {

console.log('Unknown problem, state: ' + deleteResult.state + ', error:

' + JSON.stringify(deleteResult.error));





* Control the component behavior here when record is changed (via any component)


handleRecordUpdated: function(component, event, helper) {

var eventParams = event.getParams();

if(eventParams.changeType === "CHANGED") {

// record is changed

} else if(eventParams.changeType === "LOADED") {

// record is loaded in the cache

} else if(eventParams.changeType === "REMOVED") {

// record is deleted, show a toast UI message

var resultsToast = $A.get("e.force:showToast");


"title": "Deleted",

"message": "The record was deleted."


} else if(eventParams.changeType === "ERROR") {

// there’s an error while loading, saving, or deleting the record




When the record is deleted, navigate away from the record page. Otherwise, we see a “record not found” error when the component refreshes. Here the controller uses the objectApiName property in the SaveRecordResult provided to the callback function, and navigates to the object home page.

Record Changes

If we want to perffrm any action other then rerendering we need to handle the recordUpdated event. We can handle record loaded, updated, and deleted changes, applying different actions to each change type.

For example, different actions apply to opportunities at different stages of the sales cycle.

Note: Lightning Data Service notifies listeners about data changes only if the changed fields are the same as in the listener’s fields or lawet.


<force:recordData aura:id="forceRecord"






<strong>recordUpdated="{!c.recordUpdated}" </strong>/>

Implement an action handler that handles the change.


recordUpdated: function(component, event, helper) {

var changeType = event.getParams().changeType;

if (changeType === "ERROR") { /* handle error; do this first! */ }

else if (changeType === "LOADED") { /* handle record load */ }

else if (changeType === "REMOVED") { /* handle record removal */ }

else if (changeType === "CHANGED") { /* handle record change */ }


When loading a record in edit mode, the record is not automatically updated to prevent edits currently in progress from being overwritten. To update the record, use the reloadRecord method in the action handler.

<force:recordData aura:id="forceRecord"







recordUpdated="{!c.recordUpdated}" />


recordUpdated : function(component, event, helper) {

var changeType = event.getParams().changeType;

if (changeType === "ERROR") { /* handle error; do this first! */ }

else if (changeType === "LOADED") { /* handle record load */ }

else if (changeType === "REMOVED") { /* handle record removal */ }

else if (changeType === "CHANGED") {

/* handle record change; reloadRecord will cause we to lose wer current record,

including any changes we’ve made */




So we have cover all the operation which are possible using LDS. But there are still few use case where we need Apex as well. For eg:

  1. For bulk data process we need apex. So we can’t use it as StandardsetController replacement.
  2. If we need to fetch data of more than 3 level or need to display child records then we need apex for that.

Let me know what you like most about Lightning Data Service in comments. Happy programming 🙂