Skip to main content

The Top 5 Most Treasured Winter ‘20 Features


1.       The RECYCLE BIN is now in Lightning, and it’s even better
2.       The new Salesforce Mobile App is a game changer
3.       Printable View for Lists comes to Lightning
4.       Bye-bye Power of One fields. Hello Count Unique Values (Beta)
5.       Start a Flow on a Schedule

The RECYCLE BIN is now in Lightning, and it’s even better












Now we’ve View, Restore, Delete and The Tab for Recycle Bin.

Why people love it: Accidental deletions happen more often than most of us would like to admit, and having the ability to easily find and “undo the oops” without switching back to Classic is on the shortlist of the most highly anticipated “better in Lightning” features.

Printable View for Lists comes to Lightning



Why people love it: Even if we live mostly in a digital world, there are still those times when you just need that hard copy. The Printable view gives you only the parts you need from the screen.

Bye-bye Power of One fields. Hello Count Unique Values (Beta)

First, enable this feature from “Reports and Dashboards Settings” by selecting “Enable Unique Row Count Aggregate in Reports (Lightning Experience Only).”


Why people love it: Admins everywhere have struggled with this “counting conundrum” since the dawn of Salesforce, and the best way to accomplish this was to add the legendary “Power of One” custom formula field on every object you want to count. With this feature now built into the report options, you can reserve your custom fields for other things.

Start a Flow on a Schedule:

What it is: Now you can schedule an autolaunched flow to start on a particular date and time and set the frequency to once daily, or weekly. Scheduled flows can run on a set of records you specify. For example, send a weekly alert to the owners of Opportunities in the Prospecting stage that haven’t been updated in the last seven days.

Why people love it: Previously, the only way to schedule a flow was to use scheduled Apex to call the flow. Scheduled Flows lets Admins schedule flows to run with the same ease as setting up a meeting.


Comments

Popular posts from this blog

Platform Developer I Certification Maintenance (Winter '23)

 Maintain Your Platform Developer I Certification for Winter ’23 1. Field update actions have changed in API Version 54.0. Which record-triggered flows do field update actions now execute? Answer: Before-Save after After-Save 2. Which Apex class is used to determine the hostnames for the domains that Salesforce hosts for your org? Answer: System.DomainCreator 3. Which modules can be used for notifications in a Lightning web component instead of native APIs? Answer: LightningAlert, LightningConfirm, and LightningPrompt 4. What determines an org’s “shape” in Salesforce? Answer: Features, settings, edition, limits, and licenses 5. Which lightning-modal-* component is required to create a modal? Answer: Body 6. How do you call an invocable action from Apex code? Answer: Reference Invocable.Action Get Hands-On With Apex Assertions 1. Create Two Apex class: Copy and Paste below codes (A.) TestFactory @isTest public class TestFactory {    public static Account getAccount(String accountName, B

Custom Table In LWC

I'm assuming you've Basic understanding of Lightning Web Component, I'll be explaining you the syntax that will be generic. HTML: < template > <!-- Header Part -->      < lightning-card   title = "Custom Data table in Lightning Web Components" >          < div   class = "slds-grid slds-gutters" >              < div   class = "slds-col" >                  < span ></ span >              </ div >              < div   class = "slds-col" >                  < span > <!--A Button For extra feature-->                      < lightning-button   label = "Show Selected Contacts"   onclick = {showContacts}   style = "margin-left: 40%"   variant = "brand" > </ lightning-button >                  </ span >              </ div >          </ div >< br />

LWC js-meta.xml Configuration File Tags

Each Lightning web component folder must include a configuration file named <componentName>.js-meta.xml. The configuration file defines the metadata values for the component, including the design configuration for the Lightning App Builder and Community Builder. Some Standard Key metadata values: apiVersion : A double value that binds the component to a Salesforce API version. isExposed : If isExposed is false, the component is not exposed to Lightning App Builder or Community Builder. To allow the component to be used in Lightning App Builder or Community Builder, set isExposed to true and define at least one <target>, which is a type of Lightning page. Some Standard Optional metadata values: description : A short description of the component, usually a single sentence. masterLabel : The title of the component. Appears in list views, like the list of Lightning Components in Setup, and in the Lightning App Builder and in Community Builder. targets : Specifies wher

Translate