Only the following fields are automatically indexed in Salesforce:
* Primary keys (Id, Name and Owner fields).
* Foreign keys (lookup or master-detail relationship fields).
* Audit dates (such as SystemModStamp).
* Custom fields marked as an External ID or a unique field.
“Data skew” is a condition which you will encounter when working for a big client where there are over 10,000 records. When one single user owns that many records we call that condition ‘ownership data skew’.
When such users perform updates, performance issues will be encountered because of “data skew”. This happens when a single user/ members of a single role own most of the records for a particular object.
Record level access is determined by the parent, Mandatory on the child for reference of the parent, cascade delete (if you delete the parent, it can cascade delete the child).
Force.com is the entire framework and codebase on which the whole Salesforce application exists. We can also say that Salesforce is built on Force.com, which is a Platform as a Service (PaaS) that allows us to simplify the design, development, and deployment of cloud-based applications and websites. Developers can work with Cloud Integrated Development Environment (Cloud IDE) and deploy the applications on the servers of Force.com.
The computer system executes one or more tasks according to the set of rules and scheduled tasks.
Apex cannot be customized in a production Org, it must be changed and deployed through a sandbox and meet test coverage requirements.
A protocol that defines a uniform way of passing XML-encoded data. SOAP Stands for Simple Object Access Protocol.
Taking customisations one level further, Salesforce enables you to build custom applications on the platform. Think about how Sales & Service Clouds are set up with their various features designed for a certain purpose, this can be recreated for any team function.
If you are familiar with Trailhead, you may have already created a few custom applications that will give you a good answer to this question. If not, here are a few ideas…
<> An HR application to help internal teams manage jobs and job applicants.
<> A finance system that can track invoices
<> A goal setting App that can help managers set targets and goals for their team.
Reports will give a clear picture to the management. Management will make use of reports to track progress towards its various goals, increase revenue, and control expenditure. Reports will also help to predict trends and thus gives the advantage of the increase in profits.
There are four types of reports in Salesforce. They are as follows:
A report is formed by grouping the records by rows as well as columns. It is used when you want to see data by two separate dimensions that aren’t related, such as date and product.
Example: Summarize opportunities by account horizontally and by month vertically.
A report that provides a listing of data with groupings and subtotals. It is used when subtotals are needed, based on the value of a particular field, or when you want to create a hierarchically grouped report.
Example: All opportunities for your team subtotaled by owner and sales stage.
A report that provides details of a company in tabular format. It is used when you want a simple list or an item list with a grand total.
Example: These reports are used to list all accounts, list of opportunities, list of contacts, etc.
A report that is created by the mixture of any combination of reports. Like matrix report plus summary report can give you a joined report. Also, matrix reports and tabular reports can give a joined report.
Example: You can develop a report to display opportunity, case, and activity data for your accounts.
A Permission Set is a collection of settings or permissions that is used to give access to numerous tools and functions for the user. You can use permission sets for different types of users to extend functional access without changing their profiles. Instead of creating a separate profile each time, you could easily create a Permission Set.
A connected app is a framework used to integrate an application with Salesforce with the help of APIs and standard protocols. It uses standard SAML, OAuth, and OpenID Connect protocols to authenticate, authorize, and provide single sign-on (SSO), for external apps. With the help of the Connected app, Salesforce admins can set up security policies and control who can use the corresponding apps.
Salesforce is very meticulous when it comes to recording intricate details such as sales numbers, customer details, customers served, repeat customers, etc. Salesforce makes it easy to create detailed reports, charts, and dashboards for keeping track of sales.
It is a personal look up to the same object. The self-relationship creates a tree diagram of the objects. Let's take an example as an object “merchandise”. In this, we can create relationship merchandise between two accounts. This is called a self-relationship.
The external lookup relationship is used to connect the child object to the parent object. The child object may be either a custom, standard, or external object. It uses to identify the correct map of the child object with the parent external object. The external lookup relationship values fields are matched against the External Id values.
The relationship between the two objects is called a lookup relationship. Lookup relationships connect two object links together so that you can look up from related items to other items. It can be one-to-one or one to many.
Junction objects are useful in building many-to-many relationships between objects in Salesforce.
Consider an example of recruiting application, where a position for a job is linked to many candidates or a candidate can apply for many other jobs. Here, a third-party object “job application” is referred to as a junction object in order to connect the data model. In the above-given example, “job application” is the junction object.
This Master-Detail relationship is the same as the relationship between a parent & child. In this aspect, the master is treated as Parent, and the Detail is a child. The master Object takes control of the behavior of the Detail object. The survival of the child is dependent on the parent because if the Master gets deleted the Detail will also automatically get deleted. You can create Roll-up summary fields in master records which helps in calculating the Min, Avg, Sum of the child records.
We have three types of relationships in Salesforce, which are:
* Apex is a strongly typed and object-oriented programming language that permits developers to execute flow and transaction control statements on Salesforce platform servers in conjunction with calls to the API. It uses syntax that looks similar to Java and pretends like database stored procedures.
* Apex allows developers to add business logic to many system events, including Visualforce pages, button clicks, and related record updates. This code can be initiated by requests from web services and from triggers on objects.
* All Apex code runs completely on-demand on the Lightning platform. Apex code is written and saved to the platform by developers. Through the user interface, end-users trigger the execution of Apex code
Before we understand dynamic dashboards, let us first understand static dashboards. Static dashboards are the basic dashboard types that will be visible to any user who has made a report out of his data. An example of this is what a Sales manager/ Marketing manager would be able to see on his Salesforce org. In other words, a normal dashboard shows data only from a single user’s perspective. Now comes the concept of dynamic dashboards.
Dynamic dashboards are used to display information which is tailored to a specific user. Let us consider the same example as above. In case the Sales manager wants to view the report generated specific to only one of his team members, then he can use dynamic dashboards.
A bucket field lets you group related records together by ranges and segments, without the use of complex formulas and custom fields. Bucketing can thus be used to group, filter, or arrange report data. When you create a bucket field, you need to define multiple categories (buckets) that are used to group report values.
Role: In Salesforce Role is meant to increase the data visibility to a particular user. It can be done through sharing rules or by building a role hierarchy. Using roles, you can control the ac
Profile: Unlike the roles profile is mandatory for all, and it stays at the object level. It is treated as a building pillar of an organization.
Sharing rules are written to give edit access (public read and write) or public read only access to certain individuals in Salesforce 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.
WhoID refers to people. Typically: contacts or leads. Example: LeadID, ContactID
WhatID refers to objects. Example: AccountID, OpportunityID
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:-
<> Workflow in Salesforce allows you to automate standard internal procedures and processes for saving time across your organization. It helps to evaluate records as they are created or updated and determines if an automated action needs to occur.
<> Automation functions in Salesforce include the functions such as sending follow-up emails, tracking the customer map journey, performing other marketing activities to boost the sales of the company, etc.
<> A workflow rule is a major container for a set of workflow instructions. These instructions are usually summed up in an if/then statement. Workflow rules are divided into two main components. They are:
Criteria: The “if” part of the “if/then” statement i.e., what must be true of the record for the workflow rule to execute the related actions.
<> Actions: The “then” part of the “if/then” statement i.e., what to do when the record meets the criteria.
<> Consider an example for a workflow, “if it is raining, then bring an umbrella”. In this example, the criteria are “it is raining” and the action is “bring an umbrella”. If the criteria aren’t met, then the action isn’t executed. The workflow rule’s actions are executed only when a record meets all the criteria of a workflow rule.
A dashboard in Salesforce is a pictorial representation of the report. It displays data from source reports as visual components. These components provide a snapshot of key metrics and performance indicators of the organization at a single glance. A single dashboard is capable of displaying 20 reports at a time.
<> Master-Detail relationship is a relationship between a parent and child where the master represents the parent and the detail represents a child. This relationship can be used when we want to control the display of detail records based on the value present in the master record.
<> The master object completely takes control of the behavior of the Detail object. The survival of the child is dependent on the parent, because if the parent gets deleted then the child automatically gets deleted. You can create Roll-up summary fields in master records which will calculate the SUM, AVG, and MIN of the child records.
<> Consider an example of a courier company model, where a delivery schedule is always linked to a delivery location. If we delete a delivery location from our list, then all the related delivery schedules should also be removed. Such a dependency can be achieved only through a Master-Detail relationship.
The profile is defined as a collection of rules and procedures a person needs to follow to access particular records. There are multiple profiles available in Salesforce. For example, a sales profile can have access to leads, opportunities, contacts, campaigns, etc.
As far as the second question is considered, the answer would be yes. The people who work in one department have the same profile. So the people who work under a particular department would be assigned with the same profiles.
As we have seen in the sales profile, many people work under it and every person who works under is assigned the same profile. Hence any number of people can have the same profile.
An Audit trail in Salesforce is a unique feature that helps in tracking the changes made in the organization by you and other administrators. In that way, you will always get to know who has modified the project at the last minute. It is helpful for the organization with more administrators.
By using an audit trail, you can get to know the details about changes made, the date and time of the change, and the username of the team member who made the changes.
An App in Salesforce is a logical container that holds various details related to the company such as a logo, name, business operations, etc. You can customize apps to match your needs, or you can develop new applications by combining custom and standard tabs.
The process to create an app in Salesforce is given below:
Setup —> build—> Create—> App—> Click on new.
By following the above procedure, you can develop an application as you want.
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.
Object relations in Salesforce can be of the following types:
* One to many
* Many to many
In Salesforce, we can link the standard and custom object records in a related list. It is done by the object relationship overview. Various types of relationships can be created to connect specific business cases with specific customers. It is possible to create a custom relationship on an object and define various relationship types.
One of Salesforce’s biggest selling points is its platform (Previously called Force.com). This enables you to create powerful customisations on top of Salesforce’s products, that allow you to completely tailor the applications to your organisation’s exact needs. This is made even more attractive by the fact that you can create customisations with clicks, not code.
At a basic level, this allows you to create custom fields and objects, to store unique information related to your organisation. One of the most popular customisation possibilities is automation. You can create automation to pretty much do anything in Salesforce, update a field, create a record, send an email, etc…These types of customisations can end up saving users a lot of time.
Programmatic refers to development where a developer is writing code to achieve a task. This could include, but is not limited to, Apex, Visualforce & Lightning Web Components.
The Audit trail in Salesforce is a unique feature that helps in tracking the changes that have been made in the organization by you and other administrators. It would be helpful for the organization with more administrators. This audit trail shows you the information of the twenty most recently made changes in your organization.
Below are the things that you could come to know:
* The date and time.
* Username of who made the changes.
* What the change was.
In Salesforce, objects are database tables that are used to store the data of an organization. There are two types of objects in Salesforce. They are:
* Standard object: These are the objects provided by the Salesforce platform, which includes contacts, accounts, cases, campaigns, opportunities, leads, products, contracts, reports, dashboards, etc.
* Custom object: They are objects created by developers based on the business process. It stores the important and unique information of an organization. It gives a structure for data sharing. The custom object includes page layouts, custom fields, relationship to other objects, custom user interface tab, etc.
There are four types of reports that are available in Salesforce, which are as follows.
* The tabular report is those that give us the total in a tabular format.
* Matrix report the format where grouping is done based on columns and rows.
* The summary report gives us detailed reports based on columns.
* Joined reports which are capable of allowing two or more reports in one report.
Profiles determine the level of access a user can have in a Salesforce org.
As far as the first part of the question is concerned, Yes. One profile can be assigned to any number of users. 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. In case the team lead or manager need access to additional records/ objects then it can be done by assigning permission sets only for those users.
Over the years, Salesforce has built up a huge portfolio of other products to help serve its customers. One of the most attractive selling points is the fact that they can seamlessly integrate with each other, creating a full 360-degree view of their customers.
By selecting the “All Time” in the “Range” on the page.
They are “Date filters.”
‘Time’ is the latest field in Salesforce.
Below mentioned are the Salesforce Standard Fields
Last modified by,
We can create two types of Apps in Salesforce
Custom app: This type of apps can be used in every business scenario. It is widely used in the market.
Console app: This type of app can be used only in the client service business, where we focus on solving the client’s issues. It is not comparatively, widely used in the market.
An App in Salesforce.com is a container that holds various things such as a logo, name, and a set of required tabs. It is also called a group of tabs that work together to prove the functionality that you are looking for.
In Salesforce, you can customize apps to match your requirements, or you can build new applications by combining custom and standard tabs.
The process to create an app in Salesforce:
Setup ---> build---> Create---> App---> Click on new.
Objects in Salesforce are used as database tables that are used to store information of an organization. We have two types of objects in salesforce, they are.
Standard Object: These are the objects provided by the salesforce, which include contacts, accounts, opportunities, leads, cases, campaigns, products, contracts, dashboards, etc.
Custom Object: This includes the modifications made to the Salesforce by users. It stores the essential and unique information of an organization. Custom Object includes page layouts, relationship to other objects, custom user interface tab, custom fields, etc.
The following are the major subsidiaries of Salesforce:
* Demandware Inc
Salesforce provides CRM software and cloud-based solutions that help enterprises to connect better with their customers. It supports businesses to manage their customer's data and track their activities efficiently.