twitter linkedin facebook instagram
  • Home
  • LWC
    • LWC Tutorial
    • LWC Tricks
  • Lightning(Aura)
    • Lightning Tutorial
    • Lightning Tricks
  • Apex
    • Triggers
  • Integration
  • LowCodeLove
  • Interview Q's
  • Misc

Salesforce Socrates


Lightning Web Components are Custom HTML elements built using HTML and modern JavaScript. It is a Programming model based on modern web standards

LWC  Vs  Aura

 

Lightning Components can be built using two programming models: Lightning Web components and Aura Components. Lightning Web Components use core Web Components standards, whereas Aura is a Framework. Although there is a functional difference, LWC can co-exist and interoperate with Aura Programming. To the end-user components built by these two different models appear to be the same.

In the below example we have built two lightning cards, one by LWC and the other by Aura. We notice there is practically no difference between the two.




Why did we need frameworks and what changed now?

 

Until recent year’s web standards were not evolving at a rapid pace, they offered only limited features, which developers needed to build a large scale web application i.e.
rendering engine - It parses HTML, XML, and CSS documents, and the final layout is generated & displayed on the User Interface. In other words, it takes HTML code and interprets it into what you see visually.
standard elements - just as the name implies they are the standard reusable elements,
events -JavaScript's interaction with HTML is handled through events that occur when the user or the browser manipulates a page, and
a core language (ECMAScript 5). An application could not be built on web Components because of the following shortcomings:

  1. Rendering wasn’t optimized for continuous UI transformation.

  2. Standard UI elements were scarce and the standard didn’t support the creation of custom elements.

  3. The core language lacked modern constructs to write large and modular enterprise-class apps at the client-side (modules, classes, promises, decorators, etc).

Multiple Frameworks came up to fill the gap Aura, Angular, and React are to name some. They provided language extensions to support development i.e. modules (AMD and CommonJS), promises, classes, and other general utilities. Different frameworks introduced different component models and HTML templating approaches. Frameworks became different languages; as a result, skills were not transferable. Components written in different Frameworks are not interoperable.

Web Stack of 2019 - more standards, less framework

The need for coexistence, interoperability, and standardization led to the invention of a new set of standards in the community, the idea was to get rid of the layer of abstraction provided by the frameworks and the new task of the framework was to no longer to fill the gap but to provide a thin layer of specialized services for User Experience.

Take a look at the picture below to compare how web standards have changed over the years. All the things that frameworks like Aura had to do are now shifted to Web Standard.

The Lightning Web Components provides a layer of specialized services on top of the core stack, which includes:-
1. The Lightning Base Components
2. Lightning Data Service
3. User Interface API



How can I create a Lightning Web Component?

At the current time, LWC is not supported in the Developer Console. To develop Lightning web Components you will need an IDE tool with sfdx plug-ins - which enables interaction with salesforce org, among many other things. The trailhead module here walks you through the setting up of the Salesforce DX i.e. the tools required for developing and also in the module we will create the "Hello World" Component, which will get us started.






Picture this..

You have done your research and decided to implement Salesforce CRM for Managing your Customer Information.

You have networked like crazy to gather all the leads and integrated the data into Salesforce. Everyone is excited and eager for new possibilities in the Business. Lead generation is automated, centralized email marketing is in place and you have saved a lot of time by automating many of the best customer service techniques. Voila !!

But wait, hang on…

Some of your customers and prospects are giving your company negative feedback???

With a little investigation, you have learned that the duplicate records are causing trouble for the team. The Sales Reps are calling and sending emails to the same prospects and customers multiple times. Now this can not only drive your customer aggressive but also burns your productivity.

# What Comprises of Duplicate Data?

Data duplication is an incident when an organization has multiple copies of the same data source.
Exact carbon copy of a record is the most visible form of duplicate data, which is easiest to deal with. But they are not the only type.

The most common type of Duplicate Data is the partial duplicate that contains only certain duplicate information such as, Typos in names and addresses, Spacing in fields, and Use of nicknames instead of names.


# let’s say NO to duplicate data

There are many ways to combat Duplicate Data, the most accessible is the salesforce native Duplicate Management feature. Salesforce finds and handles duplicates using a combination of Matching rules and Duplication rules. Going by definition, 

Matching rules define how duplicate records are identified.

Duplicate rules define what happens when a user views a record with duplicates or starts creating a duplicate record.





When your Sales rep creates a contact, Salesforce looks for possible duplicates (1), based on the criteria in the matching rule; it returns the list of possible duplicates (2). The Duplicate rules at (3) determine what happens with Duplicate records, either block 🚫 the Sales rep from creating Duplicates or create the Duplicate record and throw an alert ❗.

1. Prevent users from creating Duplicate Records

You can create Duplicate rules to alert or block the Sales Rep from creating Duplicate records.




Learn more about how to create the rule from the official document here.

2. Show Duplicate records

If there exists a duplicate record in the database, show alerts when a Sales Rep opens the record.




The source for learning is here.

3. Find duplicates across your organization

Rules can be run across your org to find the bulk duplicate records. Find them, and merge. Navigate to the document to find the setup process.

# Monitor and Maintain Data Quality

There is more to talk about data quality, but let me wind up mentioning how important it is to relentlessly monitor, access, and improve data within the organization. Only through constant attention, you can safeguard your data. The simple way is to leverage on reports and dashboards. One App exchange package by Salesforce Labs, you would really like for this job is the Data Quality Analysis Dashboards App.

Let's have a little hands-on here on the trailhead module for maintaining Data Quality.

This blog was about one simple way to prevent Duplicate data, Hope it was helpful. Please stay tuned to learn about App Exchange tools for Salesforce Data Management.

Newer Posts
Older Posts

Trending

Search This Blog

About Me

About Me

LET’S STAY CONNECTED

Total Pageviews

Labels

  • aura
  • Lightning web components
  • LowCodeLove
  • Salesforce Tips
@INSTAGRAM

Twitter

Tweets by sirireddy2212

Pages

  • About Me

Blog Archive

  • ▼  2020 (5)
    • ►  September (1)
    • ▼  July (2)
      • Introduction To Lightning Web Components
      • Data Quality is the yeast in the bread of business..
    • ►  June (2)
Created By SoraTemplates | Distributed by GooyaabiTemplates