Lightning URL Hacks/ Predefault fields in lightning

Remember those days when you showed off the non-code solutions to the clients and felt really awesome with their reactions... and you did this after the demo.




.. And we proudly called them URL Hacks... even though its not much of a hack, 😉, it was just passing parameters.

But it's all gone with Lightning. Boy, did they hate it when those URL buttons didn't work in lightning? I mean, it was so convenient for the users, defaulting certain fields is what they wanted, they have it on so many related lists.

... And then there were Quick Actions, Salesforce promoted them heavily for replacing custom buttons, javascript buttons etc... But it quite didnt hit the spot, I meant, they were fine. Still they are useful in some places.

Then, just to give the users more productive tools, we ended up overriding the new button or creating a custom component etc... We have this force:createRecord actions in aura components, without having to create a lot of code, we can use the existing framework and predefault some of the fields that the users want!

But No more of that! Now Salesforce is giving us this cool feature, I believe they are exposing the same force:createRecord through UI, This is Admin-friendly.

I mean all you have to do is simply put the API names and default values. Pls check this update:

https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_general_lex_navigate_to_record_dfv.htm

Example:
/lightning/o/Vehicle__c/new?defaultFieldValues= Name='System Will Populate it', OwnerId={!Opportunity.OwnerId}, Description__c={!Opportunity.Description},
Special__c={!IF(Opportunity.eligible__c, true, false)}

Well, We still have users switching back and forth between Classic and lightning, so this gave me an Idea to use one button for both classic and lightning.

Stay tuned!

Comments

Post a Comment

Popular posts from this blog

Lightning spinner inside Button

I just came across this idea when I looked at some of the standard components by salesforce, for some reason they look way cooler. I thought of sharing this with you... We many a times try to use the spinner different ways, like, on the entire component, by blurring the whole area out, when I compare salesforce's components, they don't ALWAYS do that, they just show the spinner somewhere at the bottom/ top or just next to the button or disabling / replacing the button etc... Well, when I cracked it, it looked amazing. here is a simple component: <aura:component > <aura:attribute name="boooo" type="boolean" default="false"/> <lightning:buttonGroup> <lightning:buttonIcon iconName="utility:email" variant="brand" disabled="{!v.boooo}" onclick="{! c.handleClick }" alternativeText="Click to send Email" /> <lightning:button variant="brand" title
Read more

Passing URL parameters to controller in Lightning components/ AURA

Image
The following example helps you understand how to pass parameters from URL to components. In AURA/ Salesforce1 platform, it is made easy to pass the parameters to the controllers. We know that we can create attributes in the components as variables and they are meant for the scope of the components. So we create application attributes for the entire scope of application. So when we need to get the values from the URL, it is easy to pass them to application attributes, in other words, application attributes can take the values from URL directly. Here is a simple example: 1. Create an application - 'URLApp' 2. Create an attribute in the application XML. <aura:application> <aura:attribute name="fromURL" type="String" default="this is default value"/> Value in Attribute: {!v.fromURL}! </aura:application> Save the XML and run it, your output should be: Now, If you just pass a value to the url the
Read more

Nested AURA:IFs in Lightning Components Salesforce

Image
You can use use the nested IFs on the framework. Go to Developer Console>>New>>Lightning Application Give it a name, Submit Here is a sample code: <aura:application >  <aura:iteration items="1,2,3,4,5" var="item">  Iteration {!item} -  <aura:if isTrue="{!item=='1'}"> <b>In The First IF </b> <br/> <aura:set attribute="else"> <aura:if isTrue="{!item=='2'}"> <b>In The Second IF </b> <br/> <aura:set attribute="else"> <aura:if isTrue="{!item=='3'}"> <b>In The Third IF </b> <br/> <aura:set attribute="else"> <aura:if isTrue="{!item=='4'}">
Read more