[Parul]

1. From Setup, enter Clean Rules in the Quick Find box, then select Clean Rules.
2. Edit a geocode clean rule. There are four geocode clean rules available.
3. Review your clean rule settings.
4. Save the rule.
5. Activate the rule.
6. f Clean all records when this rule is activated or saved is selected, geocodes are automatically added to all existing records. New records automatically get geocodes when they’re saved. Existing geocode values are overwritten.
7. Repeat this process for the other geocode clean rules.
8. In Salesforce Classic, if you want to be able to check the clean status of the geocode clean rules, add the Clean This Record with Data.com related list to the page layout for accounts, contacts, and leads. (In Lightning Experience, this step isn’t necessary!)

[Parul]

From left to right

[Parul]

You can only inactivate the user, but not delete the user from the org.

[Parul]

You will get a JSON response back by default. If necessary, you can force the issue via the Accept: application/json HTTP header or by appending .json to the URL.

[Parul]

You will need to configure a public site and make the webservice available through it.

 

[Parul]

Hi,

Follow below steps:

Create a custom field with a lookup filter.

From Setup, click the Object Manager tab.
Click Case, then click Fields & Relationships.
Click Contact Name, then click Edit.
In the Lookup Filter section, click Show Filter Settings.
Click the lookup icon  and choose Contact Name, then Account ID, then click Insert.
Choose equals as the operator.
In the Value/Field menu, select Field.
Click the lookup icon  and choose Case, then Account ID, then click Insert.
Ensure the Required radio button and the Active checkbox are selected.

Click Save.

[Parul]

You can certainly create an activity history entry through trigger or just set field history for "Send Email Confirmation"  so this information will automatically get saved under "<object> History" related list.

I hope this help.

[Parul]

It is actually possible to complete this module using two standard developer edition orgs.  You can create and upload the package in one org and install it (via the url) in a second org. It takes 5-10 minutes after you upload the package from the 1st org before it will be available for install but should work fine after that.  The package installs just like any other app from the App Exchange and only take a few minutes to complete. Once the package is installed, just connect to the second org from the Trailhead module and allow it to confirm that the package is present.

[Parul]

Yes, it's possible

[Parul]

Governor Limits in Salesforce.com are the run time limits enforced by the apex runtime, Since Salesforce runs on multi-tenancy environment and in order to have same performance to the database,it has imposed some run time limits called governor limits. There are many types of Salesforce Governor limits like Pre transaction limits, Force.com platfform apex limits, static apex limits and many other limits.
Because Apex runs in a multitenant environment, the Apex runtime engine strictly enforces limits to ensure that runaway Apex code or processes don’t monopolize shared resources. If some Apex code exceeds a limit, the associated governor issues a runtime exception that cannot be handled.

[Parul]

FlexiPage. Represents a Lightning page. A Lightning page is a customizable page composed of regions containing Lightning components. Includes access to the associated FlexiPage object in the Metadata API.

[Parul]

A role hierarchy works together with sharing settings to determine the levels of access users have to your Salesforce data. Users can access the data of all the users directly below them in the hierarchy. ... Each role in the hierarchy just represents a level of data access that a user or group of users needs.
The role hierarchy enables these behaviors:A manager will always have access to the same data as his or her employees, regardless of the org-wide default settings. For custom objects, you can override this behavior by deselecting the Grant Access Using Hierarchies checkbox. However, we want our role hierarchy to apply to all of our custom objects, so leave the check boxes selected.
Users who tend to need access to the same types of records can be grouped together—we’ll use these groups later when we talk about sharing rules.

[Parul]

Extending a Lightning Component
When a component extends another component it inherits all of the helper methods and attributes. It also has the ability to call super component controller actions, but don’t do it (more on that later). All event handlers in the super component are inherited by the sub component. Additionally, they can both handle the same event, but the ordering of handler execution is not defined (kind of like multiple Apex triggers on a single object).

When you want to create a component that can be extended you must set a value of true for the extensible attribute of the aura:component. By default, components are not extensible, just like Apex classes are not. As an example, consider a component, objectPanel, that displays some basic information about a Salesforce object in a uniform way, has a section that allows sub components to display a group of records however they wish, and also provides common methods to interact with the database in its helper. Since one of the main features is to show the records and operate on them and the objectPanel does not provide its own list of records, it is defined as abstract by specifying abstract=”true”.

<aura:component extensible=”true” abstract=”true” controller=”ObjectPanelController”>
	<aura:attribute name=”sObjectType” type=”String” required=”true” />
	<aura:attribute name=”maxRows” type=”Integer” default=”20″ />
	<aura:attribute name=”fields” type=”String” />
	<aura:attribute name=”records” type=”Object[]” />
	<aura:attribute name=”sObjectInfo” type=”Object” />
	<aura:handler name=”init” value=”{!this}” action=”{!c.doInit}” />
	<aura:handler event=”aura:waiting” action=”{!c.waiting}” description=”toggles spinner when data begins loading” />
	<aura:handler event=”aura:doneWaiting” action=”{!c.doneWaiting}” description=”toggles spinner when data finishes loading” />

	<h2>{!v.sObjectInfo.Label}</h2>
	<div>{!v.body}</div>
	<div>
		<a onclick=”{!c.navigateToObjectList}”>Visit {!v.sObjectInfo.LabelPlural}</a>
	</div>
</aura:component>

Here is an example of the objectPanel component being extended by the accountPanelcomponent.

<aura:component extends=”c:objectPanel”>
	<aura:attribute name=”showAccountWarning” type=”Boolean” default=”true” />

	<aura:set attribute=”sObjectType” value=”Account” />
	<aura:set attribute=”fields” value=”AccountNumber,Website” />

	<aura:iteration items=”{!v.records}” var=”rec”>
		<div>
			<a onclick=”{!c.deleteRecord}”>Del</a> |
			<a onclick=”{!c.navigateToRecord}”><ui:outputText value=”{!rec.Name}”/></a>
			<ui:outputText value=”{!rec.AccountNumber}” />
			<ui:outputURL value=”{!rec.Website}” />
			<aura:renderIf isTrue=”{!and(v.showAccountWarning, rec.Is_Red__c)}”>
				<span class=”warn”>WARNING: Red Account</span>
			</aura:renderIf>
		</div>
	</aura:iteration>
</aura:component>

The extends attribute is set to the c:objectPanel component to indicate that the accountPanel is a sub component of the c:objectPanel component. Note the “c:” that precedes the objectPanel in the extends attribute. It is the namespace of the component being extended, which in this case is the default namespace. If you were extending a component in a managed package you’d use its namespace.

[Parul]

Junction Object is a custom object with two master-detail relationships. Using a custom junction object, you can model a “many-to-many” relationship between two objects. For example, you create a custom object called “Bug” that relates to the standard case object such that a bug could be related to multiple cases and a case could also be related to multiple bugs.
By using Junction Object we can achieve this relationship, here junction object is having Master- Detail Relationship with different objects (Ex.Students & Courses). Using this Master to Detail Relationship, we can create the Many-to-Many Relationship in between the objects.

[Parul]

Master-Detail (1:n)

A parent-child relationship in which the master object controls certain behaviors of the detail object.

When a record of the master object is deleted, its related detail records are also deleted.
The Owner field on the detail object is not available and is automatically set to the owner of its associated master record. Custom objects on the detail side of a master-detail relationship cannot have sharing rules, manual sharing, or queues, as these require the Owner field.
The detail record inherits the sharing and security settings of its master record.
The master-detail relationship field is required on the page layout of the detail record.
By default, records can’t be reparented in master-detail relationships. Administrators can, however, allow child records in master-detail relationships on custom objects to be reparented to different parent records by selecting the Allow reparenting option in the master-detail relationship definition.
You can define master-detail relationships between custom objects or between a custom object and a standard object. However, the standard object cannot be on the detail side of a relationship with a custom object. In addition, you cannot create a master-detail relationship in which the User or Lead objects are the master.

[Parul]

Lookup Relationship (1:n)

This type of relationship links two objects together, but has no effect on deletion or security. Unlike master-detail fields, lookup fields are not automatically required. When you define a lookup relationship, data from one object can appear as a custom related list on page layouts for the other object. See the Salesforce online help for details.

Child row not automatically deleted when a parent row is deleted
No inherited sharing.
25 lookup relation relationships allowed per object.
Lookup field on child not necessarily required.

To create a many-to-many relationship, simply create a custom junction object with two master-detail relationship fields, each linking to the objects you want to relate. See the Salesforce online help for details. … Unlike master-detail fields, lookup fields are not automatically required.

[Parul]

when a master record is deleted in Look-up Relationship child record is not deleted.

[Parul]

Hello,

Based on the presentation following styles can be used to generate a report in Salesforce.

Tabular Report: The basic form of presentation of user data is tabular report. It has simple listing of data without any subtotals. One can use this report if the presentation is simple.

Summary Report: Summary report is a little bit advanced report as compared to tabular report having a grouping of information with subtotals.

Matrix Report: Matrix report has groups of data based on columns and rows. This report can be used to represent a comparison between related total with the total by row and total by column.

Join Report: Join report has the more advanced way to represent data. This report will allow you to relate different blocks and show them in a single report. Each block has unique attributes like name, filters, columns, data, and summary fields.

Features of the Salesforce Reports:
Salesforce Reports is one of the most powerful features to represent business and easy understanding of the relationship among objects. Every report in salesforce support following features.
Custom Summary Formula field: User can define formula based on summary report is generated.
Exception Reports (Cross Filters): These reports are used to show highlight the position where data doesn’t exist. These reports are created using cross filters.
Custom Summary Formulas: These formulas are used on reports to calculate complex data from summary level.

Thanks.

[Parul]

No

[Parul]

Settings -> Platform Encryption -> Encrypt Fields allows only to encrypt available standard fields. for existing custom fields have you tried navigating to custom field page and see if there is encryption option?

[Parul]

Dynamic dashboards enable each user to see the data they have access to. With adynamic dashboard, you can control data visibility without having to create a separate dashboard, with its own running user and folder, for each level of data access.

[Parul]

Addin some more points:

Application Events vs Component Events : Which/How to use for handling custom events in Lightning. Lightning framework is based on event-driven architecture which allows to communicate between different events. Lightning events can be fired or handled by javascript controller.

[Parul]

An inline visualforce page is a vf page which can be embedded within a detail page of a record. Salesforce allows doing so, in the edit page layout option. A vf page would be available for embedding in the detail page layout provided page is using standard controller of that particular object. For example, in the below example a inline vf page of standard controller 'contact' would be available for embedding in contact records only.

[Parul]

The following task

Tasks.
Email alerts.
field updates.
Outbound messages

[Parul]

It is a development requirement you can refer to trailed by salesforce