Standard And Custom Objects

Front 1

What can you modify on standard fields?(Customization Fields)

Back 1

-Field-level security -The field label -Help text -Picklist values

Front 2

What types of custom fields allow users to select a value?(Customization Fields)

Back 2

Picklists and lookups

Front 3

True or False: A checkbox can be a controlling field in a field dependency.(Customization Fields)

Back 3

True

Front 4

What happens when you delete a custom field?(Customization Fields)

Back 4

The field's data is also deleted. Deleted fields and their data are stored for a maximum of 15 days, during which they can be undeleted or permanently erased.

Front 5

What does the page layout control?(Customization Fields)

Back 5

The page layout controls:-the fields -sections-related lists-and buttons that appear when users view or edit a record.

Front 6

What is the difference between standard and custom validation?(Customization Fields)

Back 6

-Standard validation allows you to mark certain custom fields as required and/or unique.-Custom validation allows you to create validation rules, using your own business-specific criteria, to prevent users saving invalid data in one or more fields.

Front 7

When you define a data validation rule, what else must you also define?(Customization Fields)

Back 7

An error message

Front 8

Can tasks and events be customized?(Customization Fields)

Back 8

Yes!

Front 9

In Salesforce what is the maximum number of fields that can be added to an object?

Back 9

500

Front 10

The number of Lookup relationship that an object can have are?a. 1b. 2c. 25d. 300

Back 10

C. An object can have maximum of 25 Lookup relationships

Front 11

Which of these is true about the Lookup Relationship. Select one correct answer.a. Parent is not a required field and may be omitted.b. Deleting an object deletes its children.c. Roll-up summary field can be used to perform basic operations over all children of a parent record.d. Security access of the child record is dependent upon the parent record.

Back 11

a. Parent is not a required field and may be omitted.

Front 12

Which of the following is true about Validation Rules? Select two correct answers.a. Validation rules are executed when the user clicks on the Save button.b. Validation rules are not applicable when the data is stored using the API.c. If the error condition evaluates to true, then an error message is generated and the record is not saved. d. Validation rules are applied only when a new record is created, and not when an existing record is edited.

Back 12

A and C. Validation rules are applicable when the record is saved using the API, hence the option B is incorrect. Validation rules are applied every time the record is saved, hence D is incorrect.

Front 13

Describe the capabilities of activity management

Back 13

Activities can be tracked in many different objects including:-Campaigns-Accounts-Contacts-LeadsActivities can be:-Tasks- Events-Requested MeetingsTerminology:-assigned to-subject-due date-comments-related to-name

Front 14

Describe the standard object architecture and relationship model

Back 14

Overview of Relationships:Use relationships to associate an object with other objects in Salesforce. (Custom fields and relationships) You can define different types of relationships by creating custom relationship fields on an object.There are different types of relationships between objects in Salesforce. Their differences include how they handle data deletion, sharing, and required fields in page layouts.~Master-detail Relationship~This type of relationship 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—ExpenseReport—Expense Line Item. You can then perform operations across the master—detail—subdetail relationship. Behaviors of master-detail relationships include:-When a master record is deleted, the related detail and subdetail records are also deleted. -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.-The owner of the master record own the detail and subdetail records. Custom objects on the "detail" side of a master-detail relationship can't have sharing rules, manual sharing, or queues, as these require the Owner field.-The security settings for the master record control the detail and subdetail records.-The master-detail relationship field (which is the field linking the objects) is required on the page layout of the detail and subdetail records.-The master object can be a standard object, such as Account or Opportunity, or a custom object.-As a best practice, don't exceed 10,000 child records for a master-detail relationship.-In a many-to-many relationship, a user can't delete a parent record if more than 200 junction object records are associated with it and if the junction object has a roll-up summary field that rolls up to the other parent-Custom object: Maximum Number of Master - Detail Relationships = 23-A master detail relationship on an object can only be created before the object contains record data~Lookup Relationship~This type of relationship links two objects together but has no effect on deletion, record ownership or security.~Hierarchical Relationship~A self or hierarchical relationship exists when there is a lookup on a field object that points back to the same object that lookup field is on~Many to Many/Junction~A many-to-many relationship allows each record of one object to be linked to multiple records from another object and vice versa. Use a junction object to connect the two objects you want to relate to each other.A Junction object is a custom object with two master detail relationships with a sole purpose of simply relating two objects.

Front 15

Given a scenario, determine the appropriate record types and business processes for custom and standard objects

Back 15

Record types allow you to offer different business processes, picklist values, and page layouts to different users. Record types can be used in various ways, for example:Create record types for opportunities to differentiate your regular sales deals from your professional services engagements and offer different picklist values for each.Create record types for cases to display different page layouts for your customer support cases versus your billing cases.example: I made a separate ACCOUNT record type for dealers and customers.Business Process is the STAGE or STATUS in each given object (Sales Process, Support Process, Solution Process, Lead Process). Customizing the Picklist for each given object

Front 16

Given a scenario, identify when to apply the appropriate sales productivity features

Back 16

Activities: Tasks, Phone Calls, Emails and Events •Assign activities to yourself or others• Synchronize activities using salesforce for outlook • Create reminders and recurring tasks • Automatically log emails in activity history • View calendars of your teammates • Print a list view of your calendar • Use the cloud Scheduler to request meetings with leads and contacts