[Nikita]

Hi Prachi,

Can you please explain what is your exact requirement?

[Nikita]

Hi Piyush,

Each dashboard can have up to 20 components.

[Nikita]

Hi Piyush

The tabular reports cannot be used to run a dashboard report in salesforce. Tabular reports are the simplest and fastest way to look at data. Similar to a spreadsheet, they consist simply of an ordered set of fields in columns, with each matching record listed in a row. Tabular reports are best for creating lists of records or a list with a single grand total. They can't be used to create groups of data or charts, and can't be used in dashboards unless rows are limited. It displays just the row of records in a table-like format with the grand total. That is why Tabular reports cannot be used for generating dashboards.

[Nikita]

Hi Piyush,

Lead can be captured with salesforce by

• Web to Lead
• Lead Import

[Nikita]

Hi Prachi,

The Unfiled Public Report Folder in classic is also known as the Public Report Folder in Lightning Experience, is another special report folder. Reports stored in this report folder are accessible by all the users. If you also have permission to create and customize the report, then you will be able to store the reports in this folder.

[Nikita]

Hi Prachi,

1. Open Process Builder:
   • Salesforce Classic: Setup | Create | Workflows & Approvals | Process Builder
   • Lightning Experience: Gear icon | Setup | Platform Tools | Process Automation | Process Builder
2. Click on New | Enter Process Name. Then click Save.
3.  Click Add Object. Select Lead.
4. Select when you need to start the process: only when a record is created or when a record is created or edited.
5. Click Save.
6. Set criteria:
   • Enter a Criteria Name (something like Attach Lead to Campaign).
   • Criteria for Executing Actions: Enter the Conditions that must be met for the lead to be added to the campaign if any, otherwise select No criteria—just execute the actions!
   • Click Save.
7.  Add Immediate Actions:
   • Select the Create a Record Action Type.
   • Enter an Action Name.
   • Select Record Type: Campaign Member.
   • Set Field Values:
     • Campaign Id: 15 digit Id of the Campaign (You will find the Id in the URL of the campaign record).
     • Lead Id (Type: Reference): [Lead].Id
   •  Note: No need to set criteria for any other fields unless they are required in the Campaign Member records.
8. Save the Process.

[Nikita]

Hi Prachi,

Following is a sample Code to add hyperlink in Lightning DataTable, please make changes as per your need.

Apex Controller

public class TestClass111 {
    @AuraEnabled
    public static List<Account> getAccounts(){
        List<Account> acList = new List<Account>();
        acList = [Select Id, Name, Website From Account Where Website != NULL LIMIT 10];
        return acList;
    }
}

Lightning Component

<aura:component controller="TestClass111" implements="flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId,forceCommunity:availableForAllPageTypes,force:lightningQuickAction" access="global" >
    <aura:attribute name="accountList" type="Account[]"/>
    <aura:attribute name="columns" type="List"/>
    <aura:handler name="init" value="{!this}" action="{!c.onInit}"/>
    <h4>Lightning Data Table</h4>
    <lightning:datatable
    	data="{!v.accountList}"
        columns="{!v.columns}"
        keyField="Id"
        hideCheckboxColumn="true"
    />
</aura:component>

Lightning Controller

({
	onInit : function(component, event, helper) {
        var action = component.get("c.getAccounts");
        action.setCallback(this, function(response){
            if(response.getState() === 'SUCCESS'){
                component.set("v.accountList", response.getReturnValue());
                var columns = [
                    {label:'Id', fieldName:'Id', type:'String'},
                    {label:'Name', fieldName:'Name', type:'String'},
                    {label:'Website', fieldName:'Website', type: 'url', typeAttributes: { label: 'My Website Name', target:'_blank'}}
                ];
                component.set("v.columns", columns);
            }
            else{
                alert(response.getState());
            }
        });
        $A.enqueueAction(action);
	}
})

 

[Nikita]

Hi Laveena,

When importing custom objects, solutions, or person accounts, you can use external IDs to prevent duplicate records from being created as a result of the import operation. An external ID is a custom field that has the “External ID” attribute, meaning that it contains unique record identifiers from a system outside of Salesforce.

[Nikita]

Hi Laveena,

use the isTest(SeeAllData=true) annotation to grant test classes and individual test methods access to all data in the organization,
1) If a test class is defined with the isTest(SeeAllData=true) annotation, this annotation applies to all its test methods whether the test methods are defined with the @isTest annotation or the test method keyword
2) The isTest(SeeAllData=true) annotation is used to open up data access when applied at the class or method level

[Nikita]

Hi Laveena,

You can define different types of relationships by creating custom relationship fields on an object. Before you begin creating relationships, determine the type of relationship that suits your needs.Different types of relationships between objects in Salesforce determine how they handle data deletion, sharing, and required fields in page layouts. Let’s review the types of relationships.

Master-detail:Closely links objects together such that the master record controls certain behaviors of the detail and subdetail record. For example, you can define a two-object master-detail relationship, such as Account—Expense Report, that extends the relationship to subdetail records, such as Account—Expense Report—Expense Line Item. You can then perform operations across the master—detail—subdetail relationship.

Many-to-many: You can use master-detail relationships to model many-to-many relationships between any two objects. A many-to-many relationship allows each record of one object to be linked to multiple records from another object and vice versa.

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.

Lookup: Links two objects together. Lookup relationships are similar to master-detail relationships, except they do not support sharing or roll-up summary fields. With a lookup relationship, you can:

• Link two different objects.
• Link an object with itself. For example, you might want to link a custom object called “Bug” with itself to show how two different bugs are related to the same problem.

External lookup: An external lookup relationship links a child standard, custom, or external object to a parent external object. When you create an external lookup relationship field, the standard External ID field on the parent external object is matched against the values of the child’s external lookup relationship field. External object field values come from an external data source.

Indirect lookup: An indirect lookup relationship links a child external object to a parent standard or custom object. When you create an indirect lookup relationship field on an external object, you specify the parent object field and the child object field to match and associate records in the relationship. Specifically, you select a custom unique, external ID field on the parent object to match against the child’s indirect lookup relationship field, whose values come from an external data source.

Hierarchical: A special lookup relationship available for only the user object. It lets users use a lookup field to associate one user with another that does not directly or indirectly refer to itself. For example, you can create a custom hierarchical relationship field to store each user's direct manager.

[Nikita]

Hi Somendra,

Yes, two users can have the same profile. Take the example of a Sales or Service team in a company. The entire team will be assigned the same profile. The admin can create one profile: Sales Profile, which will have access to the Leads, Opportunities, Campaigns, Contacts and other objects deemed necessary by the company. In this way, many users can be assigned the same profile

No, two profiles can not be assigned to the same user.

[Nikita]

Hi Somendra,

No, it is not possible to edit apex classes and triggers directly in production environment.

It needs to be done first in Developer edition or testing org or in Sandbox org. Then, to deploy it in production, a user with Author Apex permission must deploy the triggers and classes using deployment tools.

However, Visualforce pages can be created and edited in both sandbox and in production.

Only if the page has to do something unique (different values), it would have to be developed via Sandbox.

[Nikita]

Hi Somendra,

A standard field record name can have data type of either auto number or text field with a limit of 80 chars.

For generating auto numbers, the format needs to be specified while defining the field and after that for every record that is added, the number will get auto-generated. For example:-
Sr No-{1}
Sr No-{2}
Sr No-{3}

[Nikita]

Hi Somendra,

Sharing rules are written to give edit access (public read and write) or public read only access to certain individuals in Sales force org. A classic example is when: – only your managers or superiors need to be given extra credentials to your records in objects as compared to your peers.

By default, all users in your organization will have organization-wide-default sharing settings of either Public Read Only or Private.
To give access to more records, which users do not own, we write sharing rules.
Example: Sharing rules are used to extend sharing access to users in public groups or roles. Hence, sharing rules are not as strict as organization-wide default settings. They allow greater access for those users.

As far as the second part of the question is concerned, the answer is no. We cannot use sharing rules to restrict data access. It is only used for allowing greater access to records

[Nikita]

Hi Laveena,

Dynamic dashboard always show data integrated with real-time so we can not scheduled dynamic dashboard.

[Nikita]

Hi Laveena,

If the Organization-Wide Settings (OWD) in your Salesforce Org is set to anything other than “Public Read/Write” for any of the standard or custom objects then it is more than likely that you will need to setup some sharing rules to share these records with other users. So what are the different ways to share records? Here is a checklist of all the different ways (20 that I could think of) in which you can share records in Salesforce. You can use this as a quick reference guide to help you determine which of these options will be most appropriate to meet your business requirements.

 

[Nikita]

Hi Prachi,

The profile determines whether a user can create a new record using a specific record type.

[Nikita]

Hi Prachi,

When the multiple currencies feature is enabled, Corporate currency is used as the basis for all currency conversion rates in salesforce.

[Nikita]

Hi Prachi,

Time-Dependent Workflow Action s needed to complete this requirement

[Nikita]

Hi Laveena,

The merge statement merges up to three records of the same sObject type into one of the records, deleting the others, and re-parenting any related records.

The following example merges two accounts named 'Acme Inc.' and 'Acme' into a single record:

List<Account> ls = new List<Account>{new Account(name='Acme Inc.'),new Account(name='Acme')};
insert ls;
Account masterAcct = [SELECT Id, Name FROM Account WHERE Name = 'Acme Inc.' LIMIT 1];
Account mergeAcct = [SELECT Id, Name FROM Account WHERE Name = 'Acme' LIMIT 1];
try {
    merge masterAcct mergeAcct;
} catch (DmlException e) {
    // Process exception here
}

 

[Nikita]

Hi Prachi,

When you convert qualified leads, Salesforce moves any campaign members to the new contacts. The leads become read-only records unless your administrator gives you permission to edit them. If existing accounts and contacts share the names specified on the leads, you can choose to update the existing accounts and contacts. Salesforce adds information from the lead into empty fields; Salesforce does not overwrite existing account and contact data.

For more detail please refer https://help.salesforce.com/articleView?id=leads_notes.htm&type=5

[Nikita]

Hi Prachi,

ID-15 are Case Sensitive
ID-18 are Case Safe

you can't have 2 separate records with the same ID-18

[Nikita]

Hi Piyush,

Settings can a system administrator control in the salesforce user interface are following

• Enable Collapsible Sections
• Show Quick Create
• Enable Hover Details
• Enable Related List Hover Links
• Enable Separate Loading of Related Lists
• Enable Separate Loading of Related Lists of External Objects
• Enable Inline Editing
• Enable Enhanced Lists
• Disable Navigation Bar Personalization in Lightning Experience
• Enable Tab Bar Organizer
• Enable Printable List Views
• Enable Spell Checker on Tasks and Events
• Enable Customization of Chatter User Profile Pages
• Change Default Display Density Setting in Lightning Experience
• Enable Lightning Right-to-Left (RTL) Support (Beta)
• Disable Lightning Experience Transition Admin Reminders

[Nikita]

Hi Piyush,

when we convert a lead account, contact and opportunity(Optional) are cretaed but the opportunity is optional so if you checked the checkbox box ‘Don’t create a new opportunity then the opportunity will be not created.

[Nikita]

Hi Piyush,

contacts, events, and tasks can be synched using the new Salesforce for Outlook