Praveen's Salesforce Diaries

 Summer 21 Release Updates.  Salesforce already published summer 21 Release notes. ( Click here ) In this blog, I listed few key details which are important in my view 😁 Key Dates for Summer 21  By Jun 12 all Orgs are now on Summer 21  General or Admin Summer 21 Changes  Download Dashboard as a PNG file.  Now after the summer 21 release, we will get an option to download the dashboard as a PNG file. Previously there was no provision available for us to download the Dashboard. Only we relied on a snipping tool to capture the dashboard images.   Record Access Reason in Lightning  Experience.  In summer 21 Onwards we can see the Record Access Reason. Prior to Summer 21, we need to switch to classic to know the record access reason. In the below screenshot you can see a button Sharing Hierarchy this facilitates the record access reason view.   Track Your Active Licenses Now we can see a lightning app called Lightning usage App. So...

Publish Subscriber model in LWC  The publisher-subscriber model or Pub/Sub model will help us establish a communication between the components which are not in the same DOM hierarchy.  Is it too technical?  I will try to explain simply. If the components are not related to one another in any way with each other using parent-child relationship then we can use the Pub / Sub model to establish a connection between two-components  What is Pub - Sub Model? We are seeing pub sub-model in our daily life. Nowadays everyone using Whatsapp. In one or another way you will be part of at least one of whats app group. If you are broadcasting any message in Whatsapp to a group you will be the publisher and people who listen to your messages are subscribers.  The pub sub-model is similar to the application event in Aura.    In the above diagram, the publisher publishes messages via Pub/Sub Channels and is consumed by the various subscribers. How to user Pub- Submodel ...

👀Trouble Shooting Lightning Web Component (LWC)  👀 .  Lightning Web Component is Compiled and Minified. This means the javascript code in minified format. Mininfcation leads to faster rendering of components on the web page. Since the code is minified it will be very difficult for the developer to debug the code on browser tools in case of any error. When minified code renders on the browser javascript codes will not be in a  beautified format and there will be a replacement of the variable we defined on the original JS file. This makes the developer job tedious on debugging.  So what is the Solution? Enabling Debug Mode  Enabling debug mode makes the developer's job easy on troubleshooting the error.  Once the Debug mode is enabled in Org for a specific user JS code won't render in Minified format. So the variable names will remain unchanged and the code will render in a beautiful format. This makes it easy for a developer to debug the issue.  Note:...