Monthly Archives: October 2017

Are you looking for a way to open a lightning component in a new tab/window on detail page button click?

While working on a lightning component development, I found that there is no standard way to open a lighting component in a new tab. You can find the same problem being asked on developer forums. So, to be honest there is no standard way to achieve this behavior. I used a workaround to get this done in a project. I… Read more »

Jquery Datepicker in Lightning Components for better control on behaviour of Datepicker

Having trouble with and components? Then why don’t you use Jqyery Datepicker? Jquery datepicker gives a lot of flexibility and freedom to developers to let them use a datepicker as per business needs. A developer can enforce validation on dates and date range which is very hard to impose using these out-of-the-box components as they rely on HTML5 input element. Following… Read more »

Salesforce Cookies #3

      No Comments on Salesforce Cookies #3

If there is a need of scheduling an apex job or schedulable apex class after each hour then cron expression is the best way. Cron expression allows you to schedule a job on a specific time. Following cron expression runs a job after each hour of the day. Cron expression is built with following parameters –  Seconds Minutes Hours Day_of_month… Read more »

Salesforce Cookies #2

      No Comments on Salesforce Cookies #2

Now using Lightning Design System in Lightning Application is easier – No static resource is required to include CSS files. An application automatically gets Lightning Design System styles and design tokens if it extends force:slds. Same behaviour can be accomplished in Visualforce pages with the help of apex:slds component. Include  in a Visualforce page to use Lightning Design System stylesheets in the… Read more »

Salesforce Cookies #1

      No Comments on Salesforce Cookies #1

Accessing record ID in the Lightning component is very simple. Just use following things. Implements force:hasRecordId interface in the component as follows. <aura:component implements=”flexipage:availableForRecordHome,force:hasRecordId” access=”global”> Define an aura:attribute as follows. <aura:attribute name=”recordId” type=”String” description=”The ID of the record to be displayed. Provided by force:hasRecordId interface.”/> Naval SharmaI am certified Salesforce Developer with Sales and Service cloud certifications. I am a true… Read more »