Salesforce

Maintaining accurate, clean data is one of the most critical things you can do to get the most out of Salesforce. It builds the trust of your team and helps you work toward complying with various data security and privacy laws.

Manage Duplicates

Salesforce finds and handles duplicates using a combination of matching rules and duplicate rules. Duplicate rules and duplicate jobs specify matching rules that determine how duplicates are identified.
To manage duplicates, follow this process:

1. Find duplicates across your org
2. Create reports on duplicate records
3. Manage duplicates using duplicate record sets
4. View error logs for duplicate rules and Matching rules

1. Find Duplicates Across Your Org

Use duplicate jobs with standard or custom matching rules to scan your Salesforce business or person accounts, contacts, or leads for duplicates.
i. Go to Setup → Duplicate Jobs → Click New Job
ii. Select an object → Select an existing matching rule or create one → Click Run
iii. View summary by going to Setup → Duplicate Jobs

2. Create Reports on Duplicate Records

Use duplicate record reports to fine-tune your duplicate and matching rules and share the results of duplicate jobs.
A duplicate records report can include these records.

• Duplicates created when a rule alerts a user to a possible duplicate, but the user creates the duplicate anyway.
• Records manually added to a duplicate record set
• Records in duplicate record sets generated by duplicate jobs

Go to Setup → Report Types → Create a report type → Select Duplicate Record Set as the primary object → Relate Duplicate Record Items to the primary object that you selected → Save the report type.
Save the Report Type. I named the report type as Duplicate Records.

Then create a new Report. Select the newly created Report Type, Duplicate Records, as the report type for this report. The below report shows the Duplicate Record Sets and the related Duplicate Record Items.
If you open the Duplicate Record Set, it shows the actual duplicate records too as highlighted below.

3. Manage Duplicates Using Duplicate Record Sets

A duplicate record set is a list of items identified as duplicates. It’s created when a duplicate rule or job runs. To manage duplicates that aren’t surfaced by a duplicate rule, create a duplicate record set.

• On a duplicate record set list view, click New.
• Specify a duplicate rule or a duplicate job.
• In Lightning Experience, in the Related tab, click New.
• In Lightning Experience only, merge duplicates in a set by selecting the Compare and Merge action.

4. View Error Logs for Duplicate Rules and Matching Rules
Troubleshoot system errors that prevent duplicate rules or matching rules from running. Error logs are deleted after 90 days.
Setup → Duplicate Error Logs → View the error logs

You already know that Lightning Web Components is a new programming model introduced by Salesforce for building Lightning components. In this article, we’ll discuss what tools you need to build Lightning web components and how to build one.

To create and develop Lightning Web Components and use their powerful features and performance benefits, you need to set up Salesforce DX. You also use Visual Studio Code, which is the recommended Salesforce development environment. You write a simple Lightning web component and add it to a page in Lightning Experience. Below are the steps to create a Lightning Web Component with conditional rendering.

Steps to build Lightning web components

1. Setup Visual Studio Code
2. Create a Project & connect to Salesforce org
3. Create a Lightning web component
4. Deploy & add to a Lightning page

1. Set Up Visual Studio Code

Visual Studio code editor has easy-to-install extensions for syntax highlighting, code completion, and more. First, install Salesforce extensions for Visual Studio Code. Search for Salesforce Extension Pack and click Install.

Search for Lightning Web Components and click Install. Re-launch Visual Studio Code to complete the installation.

Make sure the editor is ready by typing sfdx, you should see the commands already.

2. Create a Project & connect to Salesforce org

1. In Visual Studio code, press Command + Shift + P on a Mac or Ctrl + Shift + P on Windows.
2. Type SFDX.
3. Select SFDX: Create Project
4. Enter a Project Name & click create.
5. Select SFDX: Authorize an Org. Login & Allow

Success message shows like this.

3. Create a Lightning web component

1. In Visual Studio code, press Command + Shift + P on a Mac or Ctrl + Shift + P on Windows.
2. Type SFDX.
3. Select SFDX: Create Lightning Web Component.
4. Press Enter to accept the default force-app/main/default/lwc.

Give a name to the component, say Cloud Fountain. This simple component displays the text ‘Hello Cloud Fountain’

This would be your HTML file. In this, we are displaying the text “hello {greeting}”. Note that greeting is a variable here

	<template>
	<lightning-card title=”HelloWorld” icon-name=”custom:custom14″>
	<div>
	<p>Hello, {upperCaseName}!</p>
	<lightning-input name=”last_name” label=”Last Name” onchange={changeHandler}></lightning-input>
	<template if:false={showLastNameOnly}>
	<div>
	<lightning-input name=”first_name” label=”First Name” onchange={changeHandler}></lightning-input>
	</div>
	</template>
	<lightning-input type=”checkbox” label=”Show Last Name only” onchange={handleCheckBox}></lightning-input>
	</div>
	</lightning-card>
	</template>

view rawhelloWorld.html hosted with  by GitHub

This is the .js file. In this javascript file, we are assigning a value ‘Cloud Fountain’ to the variable called ‘greeting’. @track indicates, it is a variable.

	import { LightningElement, track } from ‘lwc’;
	export default class HelloWorld extends LightningElement {
	// @track greeting = ‘World’;
	@track firstName = ”;
	@track lastName = ”;
	@track showLastNameOnly = false;
	changeHandler(event) {
	// this.greeting = event.target.value;
	const fldValue = event.target.name;
	if(fldValue === ‘first_name’)
	this.firstName = event.target.value;
	else if(fldValue === ‘last_name’)
	this.lastName = event.target.value;
	}
	handleCheckBox(event){
	this.showLastNameOnly = event.target.checked;
	}
	get showLastNameOnly(){
	return this.showLastNameOnly;
	}
	get upperCaseName(){
	if(this.showLastNameOnly){
	return `${this.lastName}`.toUpperCase();
	}
	else{
	return `${this.firstName} ${this.lastName}`.toUpperCase();
	}
	}
	}

view rawhelloWorld.js hosted with  by GitHub

This is the .xml file. In this file, we are setting isExposed to True implies, this component is available to be used in the Lightning pages. Which type of Lightning pages is defined in the targets.

	<?xml version=”1.0″ encoding=”UTF-8″?>
	<LightningComponentBundle xmlns=”http://soap.sforce.com/2006/04/metadata” fqn=”helloWorld”>
	<apiVersion>45.0</apiVersion>
	<isExposed>true</isExposed>
	<targets>
	<target>lightning__AppPage</target>
	<target>lightning__RecordPage</target>
	<target>lightning__HomePage</target>
	</targets>
	</LightningComponentBundle>

view rawlcb.xml hosted with  by GitHub

That’s it. Now you can deploy this project to Salesforce

4. Deploy & Add the component to Lightning Page

Just right click the file and select SFDX: Deploy Source to Org

After deployment, the lightning web component will be available in the App Builder as a custom component on the left side menu to use in the page.

Thank you for reading this post. Please feel free to leave feedback.

As you know Salesforce introduced Lightning web components in Spring 19 release and with that the existing Lightning components are renamed as Aura components. So, the question lies how does Aura components and Lightning web components coexist in the same space and here we are to discuss the same. One thing is for sure – Aura components and Lightning web components can co-exist and work together in many different ways.

Coexistence

If you’re looking to use Aura components and Lightning web components together in your applications then there are two strategies to consider: Nested and Side-by-side compositions.

Nested Composition

A nested composition is a component within a component, either an Aura component or Lightning web component. This is like a parent-child relationship. The rule is you can have both Aura components and Lighting web components inside a parent Aura component, but Lightning web components can only contain other Lightning web components.

In the above ‘nested composition’ example, the Aura component has two child components: another Aura component and a Lightning web component.

The other parent, Lightning web component, also has two children. Both children are Lightning web components.

Remember – Aura component is the ultimate parent.

Side-by-side Composition

The other type of composition is side-by-side in which Aura component and Lightning web component are not within the same hierarchy but are placed separately in a Lightning App Page as shown below.

Here the parent Aura component and the parent Lightning web component are in Side-by-Side strategy. And within the parent Aura component and the parent Lightning web component, the strategy used is nested composition.

How do they work together?

Now that we have seen the different ways the components can co-exist within a single Lightning App Page, let’s look at how they talk between themselves in both nested and side-by-side arrangement using the above example.

1. 1. Aura component: The parent aura component can interact directly with child component attributes whether those are standard Aura events or custom Aura event bundles.
   2. Lightning web component: The parent Lightning web component can send and receive information through JavaScript CutomObject objects, as well as interacting with child component methods and properties exposed through public APIs.

Both Aura and Lightning web components can send and receive data through the Lightning Data Service (LDS) and the User Interface API.

Limitation: A mechanism for communication between Aura components and Lightning web components that aren’t in the same component hierarchy isn’t provided by the platform yet! But this will be soon available in Lightning Event Service as highlighted in the images above.