Category: Salesforce

Learn Salesforce Einstein – Salesforce AI (Artificial Intelligence)

Salesforce Einstein is the World’s smartest CRM (Customer Relationship Management) powered by Artificial Intelligence (AI). It discovers salesforce organisation most important business insights and predicts what will happen next. Based on Salesforce Einstein recommendations, action will be taken and ultimately automates certain tasks to free up Salesforce Customer time.

What is Salesforce Einstein?

Salesforce Einstein is a layer within the Salesforce platform that infuses Artificial Intelligence(AI) features and capabilities across all Salesforce Clouds. Einstein takes care of the data prep, modeling, and infrastructure needed to embed and scale predictive models throughout your Salesforce workflows.

Learn Salesforce Einstein - Salesforce AI (Artificial Intelligence)

Salesforce Einstein Vision.

Salesforce.com has recently released add-ons for image recognition for Heroku. Salesforce Einstein Vision enables you to tap into the power of Artificial Intelligence (AI) and train deep learning models to recognize and classify images at scale. Image recognition can be very helpful for marketers, sales, and Service Cloud Users. Image recognition can reduce a lot of manual tasks for the retail industry, such as counting inventory, providing visual search to the customers, and helping the customers to remotely evaluate product issues. 

Salesforce Einstein data Discovery.

SFDC Einstein Data Discovery platform uses Natural Language Processing (NLP) and machine learning to generate stories that are exported to the CSV or Salesforce Analytics Cloud. To discover insights from huge volume datasets, organizations required data scientists who could then apply mathematical models to discover hidden insights from data. Using Einstein Data Discovery product, one can analyze millions of dataset combinations in minutes.

Salesforce Einstein features.

Salesforce Einstein feature must be enabled in Salesforce and assign to the users. Some of the Salesforce Einstein feature are.

  • Discover: Insights that bring new clarity about your company’s customers.
  • Predict: Outcomes so your users can make decisions with confidence.
  • Recommend: The best actions to make the most out of every engagement.
  • Automate: Streamlined tasks that let your users focus on customer success.

What is Salesforce lightning Experience? Lightning Salesforce

Salesforce Lightning experience is a modern, fast, and intelligent user interface built with proven Salesforce1 Mobile App technology. It is a new generation productive user interface designed for Sales team and Support teams in Salesforce.com. Salesforce1 have been introduced for mobile application and two user interface for desktop version Salesforce classic and lightning Salesforce has been introduced by Salesforce.com.

Lightning Experience (or LEX for short) brings with it an entirely new client side architecture, which departs from the server-side rendering for its predecessor (Salesforce Classic) and Visualforce provided. For backwards compatibility, Visualforce UIs can still be used within Lightning Experience, although, using Visualforce in LEX will not offer the level of extensibility or visual appeal as custom UIs built using the Lightning framework.

What is Salesforce lightning Experience? Lightning SalesforceFor the first time, Salesforce developers can now use the same technology and theme Salesforce have used to build their LEX based applications, known as the Lightning Framework. Salesforce has also chosen to open source their styling framework used by Lightning, which is known as the Lightning Design System (LDS)

Salesforce lightning Experience Features.

Sales team can close more deals and sell quicker and smarter and support team can close a case faster using various tools and Salesforce Lightning Components. In recent times, mobile usage has been increased drastically and influencing Salesforce user to work on their mobiles. Sales representatives are now using mobile to research potential customers, get the details of nearby customer offices, socially connect with their customers, and even more. So Salesforce synced the desktop Salesforce Lightning Experience with mobile Salesforce1.

  • Lightning Salesforce is a modern, fast, and intelligent user interface.
  • It is built with a sales-centric mindset, focusing on helping sales representatives work more naturally on a daily basis.
  • With Lightning Experience, Salesforce users will get an intuitive and intelligent user interface.
  • Lightning Experience is built with proven Salesforce1 Mobile App technology.

Sales representatives can use mobiles to enter customers details like log tasks and notes after client meetings, run reports and dashboards and many more. All these features from the mobile is being brought into the computer web browser by Salesforce Lightning Experience.

What we call Salesforce lightning Experience?

Salesforce Lightning Experience is simply referred to as “Lightning”. When working with lightning Salesforce we will learn about different Salesforce lightning topics like Lightning Login, Lightning App Builder, Lightning for Outlook, Salesforce Lightning Components, Lightning Sync and many more. Some of them are applicable in Lightning Experience only, but some others will work in both Lightning Experience and older Classic user interfaces. Lightning Sync is used to sync your user contacts and events between your email server with Salesforce

What was before Lightning Salesforce?

Before Salesforce lightning Experience we have Salesforce Classic User interface. Salesforce classic is used by many customer still Salesforce Lightning experience came into existence. To experience modern new features in salesforce.com, it is advised to migrate from Salesforce classic to Lightning Salesforce.

Why should we migrate from Salesforce Classic to Lightning?

Lightning Experience is a modern and intelligent user experience across every device introduced in Summer ’16 release. Still so many users using Salesforce Classic. Salesforce urges users and customers to migrate from classic to Salesforce Lightning experience because the lightning user interface is totally different from classic. It has many features and some of your existing customisations may not work, such as the JavaScript button built by your Salesforce partner or your IT team. 

Change Sets in Salesforce – deployment tools

In our previous Salesforce tutorial, we have learned about What is Salesforce Sandbox, What are the different Salesforce Sandbox Types, How to create Sandbox model in Salesforce and how to login Salesforce Sandbox. In this Salesforce Training tutorial, we will learn about different deployment tools in Salesforce and about Change Sets in Salesforce.

After creating Salesforce Sandbox, we have to establish a plan to deploy changes from Production environment to Salesforce Sandbox. Metadata Migration will be occurred in Salesforce application lifecycle management or Change management. To deploy Salesforce.com Changes, we need to use appropriate deployment tools in salesforce. Some of the deployment tools in salesforce are

  1. Change sets.
  2. Force.com Migration Tool.
  3. Eclipse: Force.com Integrated Development Environment (IDE).
  4. MavensMate: Force.com IDE.
  5. Workbench.

Change Sets in Salesforce

Change sets in Salesforce are groupings of components that can be deployed from one organisation (Production organisation) to another org (Sandbox environment). Both the destination and the target org can be either a sandbox or a production org. The factor that makes change sets truly unique is their declarative nature. The entire process can be done within the Salesforce.com user interface with only point and click tools. Developers can use permission sets or profile settings to specify permissions and other access settings in a change set.

Change sets in Salesforce

What is Metadata?

Metadata describes and gives the information of other data. The Force.com IDE, Force.com Migration tool and browser based user interface are used to add records to our salesforce application. All these tools are powered by Metadata.

Steps to use Change Sets Salesforce?

  1. Create sandbox in Salesforce and establish connection between production and sandbox environment.
  2. Change deployment Settings and allow inbound changes in production environment.
  3. Login to sandbox and create outbound change sets using point and click tools.
  4. Add Change Set components and upload that Change Set to production environment.
  5. Now go to Production environment and click on Inbound Change Set and deploy the change set.

Upload Outbound Change Set in Salesforce.

An outbound change set in Salesforce is a change set created in the Sandbox environment in which you are logged in and to send to production environment. You typically use an outbound change set for customizations created and tested in a sandbox and that are then sent to a production org.

Deploy Inbound Change Set in Salesforce.

An inbound change set in Salesforce is a change set that has been sent from another Salesforce org (Sandbox environment) to the org(production environment) you are logged in to. A change set must be deployed for the changes to take effect. You can deploy the contents of an inbound change set as a whole, but not on a component-by-component basis.

Salesforce sandbox login – test.salesforce.com

In our previous Salesforce tutorial, we have learned about What is Salesforce Sandbox, What are the different Salesforce Sandbox types, How to create new Sandbox in Salesforce. In this Salesforce admin tutorial, we are going to learn about how to login Salesforce sandbox through test.salesforce.com.

Salesforce sandbox login – test.salesforce.com

Salesforce Sandboxes are separate Salesforce CRM environments that are isolated from your Salesforce production organization, so any actions that happen in our sandboxes do not affect our Salesforce production environment, and vice versa.

Sandboxes that we created in Salesforce.com can be viewed and managed. To view list of Sandboxes in Salesforce.com, navigate to Setup | Sandboxes.

Sandbox created successfully

As shown above, we have one Sandbox called DevSandbox and the Sandbox type is partial Copy Sandbox.

  • Status of the Salesforce Sandbox is completed.
  • Location is CS57.
  • Current org Id is 00D0k0000000f2D and also it displays the date when it completed.

How to login Salesforce Sandbox.

User can login Salesforce sandbox through test.salesforce.com and by clicking login button. Login button is only displayed to system administrator. When Log in button is clicked, Salesforce.com will automatically redirects to Sandbox page.

Salesforce sandbox login - test.salesforce.com

  • When we login Salesforce Sandbox we will find Sandbox name as shown above.

Salesforce sandbox login through test.salesforce.com

When your sandbox is ready for use, you receive a notification email that your sandbox has completed copying.

Salesforce sandbox login - test.salesforce.com

  • As shown above email alert will be sent. Now we can login Salesforce Sandbox through the URl : https://test.salesforce.com

To access your sandbox, click the link in the notification email. Users can log in to the sandbox at https://test.salesforce.com by appending .sandbox_name to their Salesforce usernames.

Salesforce sandbox login - test.salesforce.com

 Users can log in to an active sandbox by using the following URL: https://test.salesforce.com  and entering a modified username, which is <username> from production, with a suffix for the name of the sandbox. Here our Sandbox name is DevSandbox. 

For example, if a username for a production org is prasanth.tutorialkart-wndf@force.com, and the sandbox is named “devsandbox,” the modified username to log in to the sandbox is prasanth.tutorialkart-wndf@force.com.devsandbox.

Sandboxes that no one has logged in to for 180 days are deleted. Users who have created or most recently refreshed any sandbox within your organization will be notified that the sandbox is scheduled for deletion. These users will receive at least three e-mail notifications over 30 days prior to the deletion.

How to create Salesforce Sandbox

In Salesforce.com, a Sandbox can be created, refreshed and deleted.When we create new Salesforce Sandbox, Salesforce will automatically copy our data from the production organization into the new created Salesforce Sandbox for development, testing and training without affecting the data and configurations in our Salesforce production org.

How to create Salesforce Sandbox?

Salesforce user must be familiarized with different Salesforce Sandboxes types in SFDC. We need to set up model for our Sandbox environment so before creating Salesforce sandboxes we have to consider some important possible activities that may be essential. 

In Salesforce.com to create Full Sandbox and partial Copy Sandbox, Salesforce Sandbox template must be created and applied at sandbox creation. In this Salesforce tutorial, we are going to learn how to create Salesforce sandbox. To create new Salesforce Sandbox Navigate to Setup | Deploy | Sandboxes.

How to create Salesforce Sandbox

  • Click on Sandboxes. Here we are going to create Partial copy Salesforce Sandbox.

How to create Salesforce Sandbox

  • Clicking on the New Sandbox button allows you to create a new Salesforce Sandbox.
  • The Sandbox Templates tab is used with Partial Copy sandboxes and determines the types of record and data that is to be copied over from the production environment.
  • The Sandbox History tab allows you to see the sandbox refresh history, showing when sandboxes were created and who created them.The Refresh link allows you to replace an existing sandbox with a new copy. The existing copy of the sandbox remains available while the refresh completes and until you activate the new copy.

How to create Salesforce Sandbox

  • Enter name(10 character or fewer) and Description for Sandbox.
  • Select the type of the Sandbox that you want to create. Here we have selected Partial copy sandbox.
  • Click on next.

Selecting  Salesforce Sandbox Template.

Salesforce Sandbox template allows user to pick specific objects and data to Full Sandbox or partial copy sandbox to control the size and content of each Salesforce sandbox. 

  • Select the template from the list and click Create.

How to create Salesforce Sandbox

Now the process of creating Partial copy Sandbox will take several minutes to several days depending upon the size and type of your organization.

How to create Salesforce Sandbox

As shown above, we have successfully created Salesforce Sandbox called DevSandbox.

Sandbox created successfully

In our upcoming Salesforce tutorial, we will learn about how to login Salesforce Sandbox and how to enter username and password to access Salesforce Sandbox.

How to Create Salesforce Sandbox Template

In Salesforce.com to create Full Sandbox and partial Copy Sandbox, Salesforce Sandbox template must be created and applied at sandbox creation. For Developer and Developer Pro Sandbox there is no need to create Salesforce Sandbox template.

What is Salesforce Sandbox Template ?

Salesforce Sandbox template allows user to pick specific objects and data to Full Sandbox or partial copy sandbox to control the size and content of each Salesforce sandbox.

  • When creating Sandbox template, we can select standard and custom object data.
  • Some objects are included before selecting data because they are required in any organization.
  • Sandbox template can understand the relationship of the selected object.
  • Selected object list can be displayed with total selected number.

To create a Partial Copy sandbox and Full Sandbox, we must create and apply a sandbox template at creation time, although there is a maximum of 5 GB of data storage and 5GB of file storage that can be stored. For each selected object in the sandbox template, up to 10,000 records are brought over from the production environment.

How to Create Salesforce Sandbox Template?

In this Salesforce tutorial, we are going to learn about how to create salesforce sandbox template and how this sandbox template is used when creating Partial copy sandbox and full copy Sandbox.

  • Navigate to Setup | Deploy | Sandboxes.

Click on Sandboxes, now a new page will be displayed with three tabs Sandbox, Sand template and Sandbox history.

  • Select Sandbox template | New Sandbox template.

How to Create Salesforce Sandbox Template

  • Enter name (10 character ) and description for the Sandbox template.

How to Create Salesforce Sandbox Template

Adding objects to Salesforce Sandbox template.

To add objects to Salesforce Sandbox template, select the checkbox for each object from the available objects list. Selected objects list will be displayed as shown above. When we deselect the checkbox object will be removed from the selected object list.

  • After confirming all your choices, finally click on Save button.

How to Create Salesforce Sandbox Template

For example, if you have a Salesforce Sandbox template that includes only accounts to create a Partial Copy sandbox then up to 10,000 Account records will be copied into the new sandbox . Unlike the Developer and Developer Pro sandboxes, the Partial Copy sandbox can only be refreshed once every 5 days. 

Different Salesforce Sandbox types

In Salesforce.com we have four Different Salesforce Sandbox types. It is very useful to understand the advantages and disadvantages of each Salesforce Sandbox type. Different Salesforce Sandbox types are

  1. Full Sandbox.
  2. Partial Data Sandbox.
  3. Developer Sandbox and
  4. Developer Pro Sandbox.

Salesforce Sandbox is a snapshot of your production environment on the date you create or refresh it. A Sandbox instance is created in a separate environment for a variety of purposes such as development, testing, and training, without affecting the data and configurations in your Salesforce production instance.Different Salesforce Sandbox types

Different Salesforce Sandbox types.

Full Sandbox Salesforce.

A Full Salesforce Sandbox includes all of the metadata and data from your production org. All object records, custom setting records, and the like will be available in your Full sandbox. This would, for example, include all of the Case records created in your production environment as part of your customer support department. Likewise, all Opportunities created by your Sales team would be copied to the sandbox. A few additional options are also made available:

  • Field history: You have the option of copying a configurable amount of field history data from production.
  • Chatter data: You can include the Chatter posts and activity from production if desired.

There are two primary considerations you’ll want to make when setting up these options:

  • First, do you have concerns about file storage limits in your sandbox? If so, consider avoiding inclusion of Chatter data. Field History data does not count against your data storage limits.
  • Second, are you looking to provision the sandbox as quickly as possible? If so, avoid copying any field history or Chatter data. Overlooking these items will expedite the provisioning time of a Full sandbox.

As a standard, production orgs are provided with one Full sandbox available for use. As a result, the application of a Full Salesforce sandbox must be thoughtful and strategic. In Sandbox mainly three activities will occur they are development, testing, and training.

  • Full sandbox would be much more useful for testing or training than for development.
  •  Data volume is more often a dependency for test execution and training than it is for development.

Partial Data Sandbox Salesforce.

Partial Data Salesforce sandboxes are very similar to Full sandboxes except that they only allow a subset of data to be copied to the sandbox from production. Salesforce.com offers a “sandbox copy engine” that assists with the selection of data to be copied. Up to 10,000 records of each selected object will be included in the copy. Additionally, file and data storage limit is 5 GB.

 Note  Each Salesforce sandbox type has a different limit for file and data storage. Object records count against data storage; content, files, and Chatter feeds count against file storage.

Developer and Developer Pro Sandboxes

Developer and Developer Pro sandboxes include no data from production and they only consist of metadata. This is often sufficient for testing needs. If additional data is needed, you can manually create it via the UI (as a production user would) or load in a set of data via Data Loader. If you needed a smaller set of data, there’s really no need to provision a Full or Partial Data sandbox.

Example :- let’s say you need a sample of Accounts, Contacts, Opportunities, Cases, and Leads; you can create files of 10–100 records for each quickly with relative ease.

The only differences between Developer and Developer Pro sandboxes are the limits for file and data storage. A Developer sandbox can hold up to 200 megabytes of each, while a Developer Pro sandbox can hold up to 1 gigabyte of each.

Sandbox TypeRefresh IntervalStorage LimitWhat’s CopiesSandbox Template
Developer Sandbox1 dayData Storage : 200 MB

File Storage : 200 Mb

Metadata onlyNot Available
Developer Pro Sandbox1 dayData Storage : 1 GB

File Storage : 1 GB

Metadata onlyNot Available
Partial Copy Sandbox5 daysData Storage : 5 GB

File Storage : 5 GB

Metadata and Sample dataRequired
Full Sandbox29 daysSame as Production Org.Metadata and all data Available

Conclusion : In this Salesforce Tutorial, we have learned about Different Salesforce Sandbox types and it’s features. In our upcoming Salesforce tutorial, we will learn about refreshing Salesforce Sandbox.

What is Salesforce Sandbox

The term Salesforce sandbox refers to a development or testing environment within Salesforce.com. A sandbox is created as a copy of the current production organization and is provisioned with all of the configuration, code, and setup data (i.e., metadata) from that organization. Record data may be included, depending on the type of Salesforce Sandbox. Sandbox is initially a replica of production, it is not automatically synced with production in any way. The changes in production will not automatically be reflected in Salesforce sandbox.

What is Salesforce Sandbox?

Salesforce Sandbox is a snapshot of your production environment on the date you create or refresh it. A Sandbox instance is created in a separate environment for a variety of purposes such as development, testing, and training, without affecting the data and configurations in your Salesforce production instance.

What is Salesforce Sandbox

Salesforce Sandbox is not considered as a backup of production data and configuration at a point of time, but this is wrong because you usually will use Sandbox for other purposes such as coding, testing, quality assurance, and staging. Sandboxes should not be considered as data backups for the following reasons:

  • Full Sandbox refresh is limited to once every 29 days.
  • The full Sandbox is only included in the Unlimited and Performance editions. For all others, it has to be purchased as an add-on to your subscription.

The Sandbox should be nearly identical to your production data and configuration. You need to refresh the Sandbox to apply the latest production configuration, data changes, and all existing configurations. Data in the Sandbox that hasn’t been deployed in the production environment will be overwritten.

We can manage multiple Sandboxes depending on our licenses or additional Sandbox purchases. Each Salesforce Sandbox instance is isolated from other instances. So operations performed in one Sandbox will not affect other Sandboxes or your production environment. We can deploy Change Sets from one Sandbox to another Sandbox within the same Production org, also Change Sets are deployed from and to Production with the Sandbox.