Salesforce Questions
lookup relationship
A lookup relationship essentially links two objects together so that you can "look up" one object from the related items on another object.
Home Page
Create Home pages with features relevant to specific types of users, and assign the customized pages to different apps or app-and-user-profile combinations. Custom Home pages are supported in Lightning Experience only.
What does Company Information Do?
Let's you have an At-a-glance view of your org, find your org ID, see your licensing information, and monitor important limits like data and file usage
What happens after you enable single currency to multi-currency setup?
Once a multicurrency setup is enabled, it can't be disabled.
Junction relationship
Opportunity line items
What are the similarities between permissions and preferences?
Perms and prefs are settings, or metadata switches that configure particular aspects of product functionality. For now, just keep in mind that perms and prefs are bundled into licenses that define functionality for the org as a whole (platform licenses) or for individual users (user licenses).
Lightning Page Canvas (4)
The canvas area is where you build your page. Drag components to reorder them on the page.
Source org
The production org used to create a sandbox org
Toolbar (2)
Use the buttons in the toolbar to cut (), copy (), and paste () page content; and to undo (), redo (), save, or activate your Lightning page. You can also view your page in different formats, refresh the canvas, or adjust the canvas size to fit your view.
Record Page
With a record page, you can create a customized version of an object's record page, tailoring it to your users' needs. Custom record pages are supported in Lightning Experience and in the Salesforce mobile app.
Login History
You can review a list of successful and failed login attempts for the past six months.
Can I deactivate corporate currency?
You can't deactivate the corporate currency.
Object relationships
a special field type that connects two objects together.
hierarchical relationship
hierarchical relationships are only available on the User object. You can use them for things like creating management chains between users.
There are two main types of object relationships (another one you might run into is hierarchical relationship):
lookup and master-detail.
Profile
A group of user-level settings that comprise a subset of the functionality defined in a user license or permission set license. Each user is assigned one profile, which defines the baseline functionality enabled for the user.
Why would companies decide to still with the "classic" version of Salesforce than "lightening"?
All companies put in a lot of work to customize their Salesforce pages. Unfortunately, only "lightening" gets Salesforce updates regularly.
Record Modification Fields
All objects include fields to store the name of the user who created the record and who last modified the record. This provides some basic auditing information.
What can an admin do to modify the functionality defined in an assigned user license?
Assign a profile to the user and assign a permission set to the user
Organization
At the highest level, you can secure access to your organization by maintaining a list of authorized users, setting password policies, and limiting login access to certain hours and certain locations.
Custom Components
Custom components are Lightning components that you or someone else have created. You can configure custom Lightning components to work in Lightning App Builder.
Properties Pane (5)
Depending on what you select on the page, the properties pane shows either the overall page properties or the properties of the component that you've selected. Click Page in the breadcrumb to access the page properties when viewing a component.
Usernames
Each user has both a username and an email address. The username must be formatted like an email address and must be unique across all Salesforce organizations. It can be the user's email address, so long as it is unique.
Username
Each user must have a username that is unique across all Salesforce organizations (not just yours).
Every user must HAVE***
Every user must have a profile assigned.
Where do I install the apps; PRODUCTION OR SANDBOX?
In general, it's a best practice to first install apps in a nonproduction environment like a sandbox or Developer Edition org.
What are the differences between permissions and preferences?
In general, perms control access to features, such as Lightning Experience or Chatter, and certain aspects of security. Prefs define settings that customers can configure, such as time zone or password options.
The out-of-the-box Salesforce search sure sounds great (and it is) and works for most use cases. So why would you need a custom solution at all?
In general, you need a custom search solution when your org uses a custom UI instead of the standard Salesforce UI. Examples of home grown UIs are a customer-facing knowledge base or an internal product data site for your employees. Just a word of caution: Building a custom user interface isn't for everyone and requires extra work. The good news is that a custom search still allows you to take advantage of some of the advanced features of Salesforce search. So, if your company has decided to build a custom UI and needs a custom search, this is the module for you.
Master-Detail Relationships
In this type of relationship, one object is the master and another is the detail. The master object controls certain behaviors of the detail object, like who can view the detail's data.
What does Users Do?
It allows you to reset passwords, create new users and deactivate or freeze existing users, and view information about your users
What does View Setup Audit Trail Do?
It allows you to see 6 months of change history in your org, find out who made changes and when and is a tool for troubleshooting org configuration issues
What does Login History Do?
It allows you to see 6 months of login history for your org, view date, time, user, IP address, and more login data. It is also used for security tracking and adoption monitoring
What does Profiles Do?
It manages who can see what with user profiles and create custom profiles
Salesforce Federated Search
It's the new way for users to search for items stored outside of Salesforce. It allows you to make the global search box an external search engine. When Federated Search is set up, we transfer the user's query to the external engine, which searches the external sources. The results are returned right in the Salesforce search results. We do this through the Salesforce Federated Search connector. The connector is built using the OpenSearch specification, so you can plug in any search engine that conforms to this industry standard.
Where is provisioning applied and not applied?
It's worth noting that provisioning applies only to production orgs, which are active orgs where users access and work with live data including sandboxes. Provisioning does not apply to Demo, Developer, Scratch, or Trial orgs.
If a user leaves the company, what happens to their account and content?
No one in Salesforce can delete a user record - you can only INACTIVATE because they are associated with records on the system.
Objects
Object-level security provides the simplest way to control which users have access to which data. By setting permissions on a particular type of object, you can prevent a group of users from creating, viewing, editing, or deleting any records of that object. For example, you can use object permissions to ensure that interviewers can view positions and job applications but not edit or delete them.
What is the similarities and differences between account teams vs. opportunities team?
Opportunity teams are a bit like account teams. Both let you relate particular people at your company to accounts or opportunities. But, whereas account team members can be expected to form a long-term relationship with a customer, an opportunity team is a temporary group. It's composed of people who can help you close a deal.
Roles
Roles determine what users can see in Salesforce based on where they are located in the role hierarchy. Users at the top of the hierarchy can see all the data owned by users below them. Users at lower levels can't see data owned by users above them, or in other branches, unless sharing rules grant them access. Roles are optional but each user can have only one. If you have an org with many users, you may find it easier to assign roles when adding users. However, you can set up a role hierarchy and assign roles to users at any time. Roles are only available in Professional, Enterprise, Unlimited, Performance, and Developer editions of Salesforce.
What are the main two APIs?
Salesforce Object Query Language (SOQL) and Salesforce Object Search Language (SOSL)
Platform-level perms
Specify features and capabilities for the org as a whole. Platform-level perms are turned on or off by the provisioning system, based on what a customer purchases. As a customer, you can't turn platform-level perms on or off. Examples of platform-level perms include support for creating custom objects or making API requests.
Standard Components
Standard components are Lightning components built by Salesforce.
What lightening components are supported by lightening page?
Standard components, custom components, and third-party components on app exchange.
What is the AppExchange?
The AppExchange is a Salesforce store that has a community of partners that use the flexibility of the Salesforce platform to build amazing apps and other solutions that anyone can use. These offerings are available (some for free, some at a cost) for installation on AppExchange.
Third-Party Components on AppExchange
The AppExchange provides a marketplace for Lightning components. You can find packages containing components already configured and ready to use in the Lightning App Builder.
Setup Audit Trail
The Setup Audit Trail logs when modifications are made to your organization's configuration.
Lightning Components Pane (3)
The components pane contains all standard and custom Lightning components that are supported for your Lightning page. Click and drag a component to add it to the page.
Records
To control data with greater precision, you can allow particular users to view an object, but then restrict the individual object records they're allowed to see. For example, record-level access allows interviewers to see and edit their own reviews, without exposing the reviews of other interviewers. You can manage record-level access in the following ways.
App Page
Use an app page to create a home page for a third-party app that you can add directly into the Salesforce mobile app and Lightning Experience navigation menus. Your users then have an app home page where they can quickly access the most important objects and items.
Passwords
Users must change their password the first time they log in.
Username Format
Users must have a username in the format of an email address (that is, [email protected]), but they don't have to use a real email address. (They can use their email address if they wish as long as their email address is unique across all Salesforce orgs.)
If a customer purchases an upgrade or add-on, how does the admin keep the sandbox org licenses in sync with the production org licenses?
When you make any changes/updates to production org licenses, you must push changes to the sandbox orgs if you want your test environment to mirror your production environment. In many cases, you can refresh the sandbox org to make sure that its licensing information matches the production org's. To ensure that sandbox orgs receive updated license information, customers can use the Match Production Licenses to Sandbox tool. With this tool, you can match all provisioned changes in the production org to the sandbox org, without having to refresh the sandbox. Matching updates the sandbox license counts to match the production license counts. Matching also adds licenses that are in production but not in sandbox, and deletes licenses from the sandbox that aren't in production.
Header (1)
When you're working on a Lightning page, the header shows you its label, and contains a Pages list where you can see the last 10 pages that you modified. You can also return to Setup without saving or to view more help for the Lightning App Builder. If you're editing an app, the header also shows the app name and contains an App Settings tab where you can configure the app's options such as branding, navigation, and the utility bar. In an app context, the Pages list shows all active Lightning pages associated with the current app.
When activating a Home page, you have three different options:
You can make your page the default for everyone in the org, the default for an app, or assign it to one or more app and profile combinations, giving your users access to a page designed just for their role.
What is "Salesforce"?
Your customer success platform designed to help you sell, service, market, analyze, and connect with your customers.
Your custom Lightning components don't automatically work on Lightning pages or in the Lightning App Builder. To make a custom component usable in both, you need to:
1.) Configure the component and its component bundle so that they're compatible with the Lightning App Builder and Lightning pages. Depending on the Lightning component programming model that you're working with, see the Lightning Aura Components Developer Guide or the Lightning Web Components Developer Guide for details. 2.) Deploy MyDomain in your org.
You can set object permissions with profiles or permission sets. A user can have one profile and many permission sets.
A user's profile determines the objects they can access and the things they can do with any object record (such as create, read, edit, or delete). Permission sets grant additional permissions and access settings to a user.
What are the three main categories in the Setup menu?
Administration, Platform Tools, and Settings
How does the whole search thing work?
All records are stored as data fields in the org's database. When you update or create a record, the search engine comes along, makes a copy of the data, and breaks up the content into smaller pieces called tokens. We store these tokens in the search index, along with a link back to the original record. From the user's perspective, the search process is similar to when a record is created. When users enter a term in the search field (1), the search engine breaks up the search term into tokens (2). It matches those tokens to the record information stored in the search index (3), ranks the associated records by relevance (4), and returns the results that users have access to (5).
Alias
An alias is a short name to identify the user on list pages, reports, or other places where their entire name doesn't fit. By default, the alias is the first letter of the user's first name and the first four letters of their last name.
Single object search
SOQL works when you know which field the data resides in. Because we didn't specify the field for march 2016 email, a SOSL search is preferred over SOQL. In general, if the query doesn't specify a target field to search, SOSL works.
Users can have the same email address across organizations.
Login Link
Users can only use the login link in the sign-up email once. If a user follows the link and does not set a password, you (the admin) have to reset their password before they can log in.
List these steps to develop a good AppExchange strategy.
1.) Identify departments that use or plan to use Salesforce. 2.)Research what's available on AppExchange that best meets your stakeholder requirements. Discuss business cases with department heads to determine exact needs. a.)What business problem are you trying to solve?b.)What are your main pain points right now? c.)How many users need this app? d.)What's your budget? e.)What's your time line? When you find an app that you think meets your needs: 4.) Download the app in a test environment (like a free Developer Edition or sandbox). 5.)Ensure that the app you're installing doesn't interfere with any other apps you've installed or customizations you've made. 6.) If you're choosing between multiple apps, take some time to evaluate what you've tested. Determine whether there are feature gaps or unwanted functionality. If necessary, invite your stakeholders to demo the apps and provide feedback. 7.) You're ready to go! You'll install and deploy your app in your production environment. Make sure you keep your users in the loop about what's changing, and provide training and documentation as necessary.
You control record-level access in four ways.
1.) Org-wide defaults specify the default level of access users have to each other's records. 2.) Role hierarchies ensure managers have access to the same records as their subordinates. Each role in the hierarchy represents a level of data access that a user or group of users needs. 3.) Sharing rules are automatic exceptions to org-wide defaults for particular groups of users, to give them access to records they don't own or can't normally see. 4.) Manual sharing lets record owners give read and edit permissions to users who might not have access to the record any other way.
What are the following ways to manage record-level access?
1.) Organization-wide defaults specify the default level of access users have to each others' records. You use organization-wide sharing settings to lock down your data to the most restrictive level, and then use the other sharing tools to selectively give access to other users. For example, you can give all employees access to an object called Candidate to allow anyone to add a candidate to the database. But you can restrict access to Positions so that anyone can see the jobs available but only the employees with the proper permissions can edit them. 2.) Role hierarchies open up access to those higher in the hierarchy so they inherit access to all records owned by users below them in the hierarchy. Role hierarchies don't have to match your organization chart exactly. Instead, each role in the hierarchy represents a level of data access that a user or group of users needs. For example, you can restrict access to Candidates by setting the organization-wide default to Private, but allow recruiters to view and edit the candidate records that they own. Recruiters can't see candidate records they don't own because recruiters are all at the same level in the role hierarchy. However, hiring managers can be given read/write access to all candidate records because they are at a higher level in the role hierarchy than recruiters. 3.) Sharing rules enable you to make automatic exceptions to organization-wide defaults for particular groups of users, to give them access to records they don't own or can't normally see. Sharing rules, like role hierarchies, are only used to give more users access to records—they can't be stricter than your organization-wide default settings. For example, you can allow all employees to view Positions, but use sharing rules to grant full editing access to employees in a role or group called Hiring Managers. 4.) Manual sharing allows owners of particular records to share them with other users. Although manual sharing isn't automated like organization-wide sharing settings, role hierarchies, or sharing rules, it can be useful in some situations, for example, if a recruiter going on vacation needs to temporarily assign ownership of a job application to another employee.
Use SOSL when you don't know in which object or field the data resides and you want to:
1.) Retrieve data for a specific term that you know exists within a field. Because SOSL can tokenize multiple terms within a field and build a search index from this, SOSL searches are faster and can return more relevant results. 2.) Retrieve multiple objects and fields efficiently, and the objects might or might not be related to one another. 3.) Retrieve data for a particular division in an organization using the divisions feature, and you want to find it in the most efficient way possible.
Use SOQL when you know in which objects or fields the data resides and you want to:
1.) Retrieve data from a single object or from multiple objects that are related to one another. 2.) Count the number of records that meet specified criteria. 3.) Sort results as part of the query. 4.) Retrieve data from number, date, or checkbox fields.
You can determine the organization-wide defaults you need for your app by answering the following questions for each object.
1.) Who is the most restricted user of this object? 2.)Is there ever going to be an instance of this object that this user shouldn't be allowed to see? 3.)Is there ever going to be an instance of this object that this user shouldn't be allowed to edit?
The visibility and access for any type of data is determined by the interaction of the above security controls, based on these key principles.
1.)A user's baseline permissions on any object are determined by their profile. 2.) If the user has any permission sets assigned, these also set the baseline permissions in conjunction with the profile. 3.) Access to records a user does not own are set first by the org-wide defaults. 4.) If the org-wide defaults are anything less than Public Read/Write, you can open access back up for certain roles using the role hierarchy. 5.) You can use sharing rules to expand access to additional groups of users. 6.) Each record owner can manually share individual records with other users by using the Share button on the record.
Each user account contains at least the following:
1.)Username 2.)Email Address 3.)User's First and Last Name 4.)License 5.)Profile 6.)Role (optional)
Once multiple currencies is enabled you also:
Activate additional currencies and optionally select a new corporate currency. Ensure users have correct personal currencies. Make sure users use the correct currency when creating records.
What is a salesforce license?
A Salesforce license is similar to a lease agreement between a property manager and a tenant. A Salesforce license, or more precisely, a license definition, is a metadata description of the Salesforce features and services that are available to your org. License definitions describe functionality for your org as a whole and for individual users in your org. A license itself is the specific agreement between Salesforce and a particular customer, which defines functionality for that customer org.
Profile
A subset of the functionality defined in a user license or permission set license. As an admin you assign each user one profile, based on the user's job requirements. The functionality in the profile can't exceed the functionality in the user license or permission set licenses assigned to the user. Profiles ensure that users have the functionality they need, but don't have any functionality that exceeds their job requirements. For example, a user license may provide the capability to read, edit, and delete records, but an assigned profile may only provide the capability to read and edit records. The profile defines baseline functionality for the user, which can't be revoked as long as the profile is assigned. Each Salesforce edition includes several standard profiles. Some editions include the option to create custom profiles. OR Profiles determine what users can do in Salesforce. They come with a set of permissions which grant access to particular objects, fields, tabs, and records. Each user can have only one profile. Select profiles based on a user's job function (the Standard User profile is the best choice for most users). Don't give a user a profile with more access than the user needs to do their job. You can grant access to more items the user needs with a permission set.
Permission set
A subset of the functionality defined in a user license or permission set license. Permission sets are optional supplements that can extend the functionality in the profile assigned to a user. Contain settings that grant users permissions. Permission sets extend users' functional access without changing their profiles. Each user may be assigned one or more permission sets. Note that a permission set is different from a permission set license, defined in the first unit.
User Licenses
A user license determines which features the user can access in Salesforce. For example, you can allow users access to standard Salesforce features and Chatter with the standard Salesforce license. But, if you want to grant a user access to only some features in Salesforce, you have a host of licenses to choose from. For example, if you have to grant a user access to Chatter without allowing them to see any data in Salesforce, you can give them a Chatter Free license.
Custom object search
As with a single object search, you could search through custom objects in SOQL fine. However, we didn't specify in which field the data resides for our search term pink hi-top. In addition, SOQL searches against the database, not the index. So, let's say that the record actually included pink sneaker hi-top. SOQL wouldn't be able to return the right results.
Multiple object search
Because you can only retrieve data from multiple objects that are related to one another, the multiple object search in SOQL is limited. In our scenario, the objects were unrelated, so SOSL it is.
What is CRM?
CRM stands for customer relationship management and is an technology that allows you to manage relationships with your customers and prospects and track data related to all of your interactions.
Data Types
Checkbox—for fields that are a simple "yes" or "no," a checkbox field is what you want. Date or DateTime—these field types represent dates or date/time combinations, like birthdays or sales milestones. Formula—this special field type holds a value that's automatically calculated based on a formula that you write. For example, D'Angelo can write a formula field that automatically calculates a real estate agent's commission on a home sale.
What are the top five Setup pages to know about?
Company Information, Users, Profiles, View Setup Audit Trail, and Login History
Permission set licenses
Extend the functionality of user licenses. With permission set licenses, you can assign more permissions to users than their user license supports.
Permission set
Like a profile, a permission set is a subset of the functionality defined in a user license or permission set license. But, while a user can have just one profile, each user can be assigned multiple permission sets. Each permission set can extend a user's access beyond the functionality defined in the profile. Like profiles, permission sets can't exceed the functionality defined in the assigned user license or permission set licenses. Salesforce provides standard permission sets, and some editions include the option to create custom permission sets. So, why would you use both profiles and permission sets? The profile, as we described, defines the baseline access for a user. Permission sets provide a way to layer additional functionality, to supplement the baseline. With permission sets, as an admin you can grant functional access to a user for specific scenarios, regardless of the user's primary job function. You can use permission sets to reduce the number of unique profiles you need to create, and to reduce the number of permissions you need to include in the profiles.
Platform-level prefs
Like platform-level perms, these prefs also specify features and capabilities for the org as a whole. Unlike platform-level perms, as an org admin you can turn platform-level prefs on or off, usually through Setup. Examples of platform-level prefs include language settings and time zone settings.
What are two basic strategies to combat sluggish searches?
Limit which data you're searching through Limit which data you're returning
What do permission sets do?
Permission sets can only GIVE access they CANNOT TAKE AWAY access
User-level perms
Specify functionality for individual users. As an admin, you use profiles and permission sets to control which user perms in a license are activated for a given user, so that users with the same license can have different levels of functionality. We explain more about how you modify user-level perms later in this unit.
User-level prefs
Specify personalization choices, such as tab display. Each user can configure user prefs for themselves. (User prefs don't control functionality related to feature access or security.)
Do I give app permissions to admins only, all users, or specific profiles?
That depends on who the app is for. If you want to limit access to a particular set of users, plan to modify those user profiles before you install the app.
If a customer purchases an add-on that includes a new user license, how does an existing user get access to the new license?
The admin must assign the new user license to the user.
This is a consequence of two important concepts in the platform:
The permissions on a record are always evaluated according to a combination of object-, field-, and record-level permissions. When object- versus record-level permissions conflict, the most restrictive settings win. What this means is that even if you grant a profile create, read, and edit permissions on the recruiting objects, if the record-level permissions for an individual recruiting record prove to be more restrictive, those are the rules that define what a recruiter can access. For example, if you give the Recruiter profile create, read, and edit permissions on the Candidates object but restrict recruiters' access to only the Candidate records they own, recruiters are only able to access those records.
Where are personal currencies stored?
They are stored in the user's personal setings
Edition upgrade
When a production org transitions to a higher Salesforce edition.
Field History Tracking
You can turn on auditing to automatically track changes in the values of individual fields. Although field-level auditing is available for all custom objects, only some standard objects allow it.
Fields
You can use field-level security to restrict access to certain fields, even for objects a user has access to. For example, you can make the salary field in a position object invisible to interviewers but visible to hiring managers and recruiters.
Of the four types of permissions and preferences, which type can be turned on and off by an admin?
platform-level preferences
What profile has to at least have ONE user and which profile is it?
the only profile that has to have at least one user assigned to it is the SYSTEM ADMINISTRATOR