Salesforce learning Notes
The maximum number of records that can be evaluated in a single trigger by Salesforce.
Up to 200 records can enter your trigger at once!.
150 DML statements limit:
A user can be assigned to one or more of feature licenses.
maximum number of records you can import with the Import Wizard 50,000
50,000 Import Wizard
Opportunity is an object that can't be imported with the import wizard.
The Recycle Bin in the sidebar allows you to view and restore records deleted within the last 15 days. After which they are permanently deleted.
15 days deleted records
By associating campaigns using a lookup relationship, you can group campaigns within a specific marketing program or initiative.
Hierarchies contain up to five levels. Each campaign can have one parent campaign.
In a master detail object relationship, you cannot create a sharing rule for a detail object, it is inherited.
detail object No Sharing rule
An Administrator can grant Read/Write and Read Only access through sharing rules. Sharing rules can be based on record ownership or other criteria.
You can't use Apex to create criteria-based sharing rules.
Also, criteria-based sharing cannot be tested via Apex.
Read/Write and Read Only sharing rules
How many custom summary formulas can you have per report? 5.
5 custom summary formulas.
The default batch size is 200 records.
Future methods are typically used for:
Callouts to external Web services. If you are making callouts from a trigger or after performing a DML operation, you must use a future or queueable method. A callout in a trigger would hold the database connection open for the lifetime of the callout and that is a "no-no" in a multitenant environment.
Queueable Apex is essentially a superset of future methods with some extra #awesomesauce. We took the simplicity of future methods and the power of Batch Apex and mixed them together to form Queueable Apex
Because queueable methods are functionally equivalent to future methods, most of the time you’ll probably want to use queueable instead of future methods.
When object vs. record level permissions conflict, the most restrictive setting wins. (If a record level is more restrictive, although object level allows it, still the record level wins because it is more restrictive)
Changing your sharing model deletes any manual shares your users have created.
You can't change the organization-wide sharing default setting for some objects:
1. Standard User
Create, Read, Edit, Delete on records they can access
2. Read Only
Only view records that they can access
3. System Administrator
Super powers! View all data & modify all data
4. Solution Manager
Standard User + manage published solutions
5. Marketing Manager
Standard users + import leads
6. Contract Manager
Standard user + manage contracts
You can create up to 500 roles for your organization.
Individual users can import up to 500 records during each import session using the 'Import Your Contacts' wizard.
Administrators can import up to 50,000 records at a time using the "Import Accounts & Contacts for Your Company" wizard.
An opportunity alert: sends a notification the first time an opportunity reaches the threshold. So, an
opportunity that reaches the threshold with 90% probability will not trigger additional alerts if the
probability subsequently goes higher. However, an opportunity that already triggered an alert and then
fell below the threshold can trigger a second alert if it crosses that threshold again. Your threshold consists of an opportunity amount and
probability
Forecasts: is a revenue projection that aggregates individual opportunities into a total or summary,
expressed in a dollar amount and/or units of product (Roll up).
Your administrator determines which types of schedules your organization can use: quantity schedules,
revenue schedules, or both. Your administrator also specifies which types of schedules can be established
for each separate product.
Without a lead assignment rule, the system assigns all new web-generated leads to the Default
Lead Owner defined on the Lead Settings page
Users who need access to same records can be grouped together with Sharing rules. o Users can always view and edit all data owned by or shared with users below them in the role hierarchy. o An option (Grant Access Using Hierarchies) on your organization-wide default allows you to ignore the hierarchies when determining access to data. Grant using hierarchies cannot be disabled for standard objects. o Contacts that are not linked to an account are always private. Only the owner of the contact and administrators can view it. Contact sharing rules do not apply to private contacts. o Notes and attachments marked as private via the Private checkbox are accessible only to the person who attached them and administrators. o Events marked as private via the Private checkbox are accessible only by the event owner. Other users cannot see the event details when viewing the event owner’s calendar. However, users with the “View All Data” or “Modify All Data” permission can see private event details in reports and searches, or when viewing other users’ calendars. o Users above a record owner in the role hierarchy can only view or edit the record owner’s records if they have the “Read” or “Edit” object permission for the type of record Exceptions to Role Hierarchy-based Sharing
Your formulas can reference custom links
Note that formula fields
are not available in search result layouts.
Cross-object formulas that reference currency fields
Salesforce allows a maximum of ten (10) unique relationships per object in cross-object formulas
sharing model
Record Access (Record level security) a. Private: b. Public Read only c. Public Read/Write d. Public Read/Write/Transfer
You cannot reference cross-object formulas in roll-up summary fields.
Custom reference field can reference other Custom reference fields and cross Custom reference field and rollup summary field
In cross-object formulas, you cannot reference merge fields for objects related to activities. For
example, merge fields for contacts and accounts are not available in task and event formulas
The lead is marked as “Read” and will not display in the My Unread Leads list view. However, if you save
the lead using the Save & New button, the lead is marked as “Unread.”
When referencing a record type in a formula, use RecordType.Id instead of RecordType.Name. If you use
RecordType.Name and the record type name changes, your formula will break. The record type ID never
changes.
By Default you will get recordTypeID only on your trigger.
the value of a lookup field is not actually a string (as displayed in the UI) but an ID,
Do not use the $RecordType global variable in cross-object formulas. The $RecordType variable only
resolves to the record containing the formula, not the record to which the formula spans.
Import wizard for leads (under lead tab) or data management | Import leads (<= 50,000)
With Web-to-Lead,you car add up to 500 new leads a day.
In cross-object formulas, you cannot reference record owner merge fields for any object
Long text area, encrypted, and Description fields are not available for use in formulas
Deleted custom fields counts against the maximum number of custom fields allowed in your
Salesforce uses the round half up tie-breaking rule for numbers in formula fields.
In account formulas, all business account fields are available as merge fields. However, account fields
exclusive to person accounts such as Birthdate and Email are not available.
IF(IsTask, "This is a task", "This is an event")
The output of your formula must be less than 19 digits.
Salesforce allows a maximum of ten (10) unique relationships per object in cross-object formulas.
For example, if two different
formulas on opportunities reference two different fields of an associated account, only one unique
relationship exists (from opportunities to accounts).
In cross-object formulas, you cannot reference merge fields for objects related to activities. For
example, merge fields for contacts and accounts are not available in task and event formulas.
In cross-object formulas, you cannot reference record owner merge fields for any object. For example,
the opportunity owner's Role merge field is not available in opportunity formulas
Products are the individual items that you sell on your opportunities and quotes.
You can create a
product and associate it with a price in a price book. Each product can exist in many different price books
with many different prices
Up to 200 records can enter your trigger at once!.
150 DML statements limit:
A user can be assigned to one or more of feature licenses.
maximum number of records you can import with the Import Wizard 50,000
50,000 Import Wizard
Opportunity is an object that can't be imported with the import wizard.
The Recycle Bin in the sidebar allows you to view and restore records deleted within the last 15 days. After which they are permanently deleted.
15 days deleted records
By associating campaigns using a lookup relationship, you can group campaigns within a specific marketing program or initiative.
Hierarchies contain up to five levels. Each campaign can have one parent campaign.
In a master detail object relationship, you cannot create a sharing rule for a detail object, it is inherited.
detail object No Sharing rule
An Administrator can grant Read/Write and Read Only access through sharing rules. Sharing rules can be based on record ownership or other criteria.
You can't use Apex to create criteria-based sharing rules.
Also, criteria-based sharing cannot be tested via Apex.
Read/Write and Read Only sharing rules
How many custom summary formulas can you have per report? 5.
5 custom summary formulas.
The default batch size is 200 records.
Future methods are typically used for:
Callouts to external Web services. If you are making callouts from a trigger or after performing a DML operation, you must use a future or queueable method. A callout in a trigger would hold the database connection open for the lifetime of the callout and that is a "no-no" in a multitenant environment.
Queueable Apex is essentially a superset of future methods with some extra #awesomesauce. We took the simplicity of future methods and the power of Batch Apex and mixed them together to form Queueable Apex
Because queueable methods are functionally equivalent to future methods, most of the time you’ll probably want to use queueable instead of future methods.
When object vs. record level permissions conflict, the most restrictive setting wins. (If a record level is more restrictive, although object level allows it, still the record level wins because it is more restrictive)
Changing your sharing model deletes any manual shares your users have created.
You can't change the organization-wide sharing default setting for some objects:
1. Standard User
Create, Read, Edit, Delete on records they can access
2. Read Only
Only view records that they can access
3. System Administrator
Super powers! View all data & modify all data
4. Solution Manager
Standard User + manage published solutions
5. Marketing Manager
Standard users + import leads
6. Contract Manager
Standard user + manage contracts
You can create up to 500 roles for your organization.
Individual users can import up to 500 records during each import session using the 'Import Your Contacts' wizard.
Administrators can import up to 50,000 records at a time using the "Import Accounts & Contacts for Your Company" wizard.
An opportunity alert: sends a notification the first time an opportunity reaches the threshold. So, an
opportunity that reaches the threshold with 90% probability will not trigger additional alerts if the
probability subsequently goes higher. However, an opportunity that already triggered an alert and then
fell below the threshold can trigger a second alert if it crosses that threshold again. Your threshold consists of an opportunity amount and
probability
Forecasts: is a revenue projection that aggregates individual opportunities into a total or summary,
expressed in a dollar amount and/or units of product (Roll up).
Your administrator determines which types of schedules your organization can use: quantity schedules,
revenue schedules, or both. Your administrator also specifies which types of schedules can be established
for each separate product.
Without a lead assignment rule, the system assigns all new web-generated leads to the Default
Lead Owner defined on the Lead Settings page
Users who need access to same records can be grouped together with Sharing rules. o Users can always view and edit all data owned by or shared with users below them in the role hierarchy. o An option (Grant Access Using Hierarchies) on your organization-wide default allows you to ignore the hierarchies when determining access to data. Grant using hierarchies cannot be disabled for standard objects. o Contacts that are not linked to an account are always private. Only the owner of the contact and administrators can view it. Contact sharing rules do not apply to private contacts. o Notes and attachments marked as private via the Private checkbox are accessible only to the person who attached them and administrators. o Events marked as private via the Private checkbox are accessible only by the event owner. Other users cannot see the event details when viewing the event owner’s calendar. However, users with the “View All Data” or “Modify All Data” permission can see private event details in reports and searches, or when viewing other users’ calendars. o Users above a record owner in the role hierarchy can only view or edit the record owner’s records if they have the “Read” or “Edit” object permission for the type of record Exceptions to Role Hierarchy-based Sharing
Your formulas can reference custom links
Note that formula fields
are not available in search result layouts.
Cross-object formulas that reference currency fields
Salesforce allows a maximum of ten (10) unique relationships per object in cross-object formulas
sharing model
Record Access (Record level security) a. Private: b. Public Read only c. Public Read/Write d. Public Read/Write/Transfer
You cannot reference cross-object formulas in roll-up summary fields.
Custom reference field can reference other Custom reference fields and cross Custom reference field and rollup summary field
In cross-object formulas, you cannot reference merge fields for objects related to activities. For
example, merge fields for contacts and accounts are not available in task and event formulas
The lead is marked as “Read” and will not display in the My Unread Leads list view. However, if you save
the lead using the Save & New button, the lead is marked as “Unread.”
When referencing a record type in a formula, use RecordType.Id instead of RecordType.Name. If you use
RecordType.Name and the record type name changes, your formula will break. The record type ID never
changes.
By Default you will get recordTypeID only on your trigger.
the value of a lookup field is not actually a string (as displayed in the UI) but an ID,
Do not use the $RecordType global variable in cross-object formulas. The $RecordType variable only
resolves to the record containing the formula, not the record to which the formula spans.
Import wizard for leads (under lead tab) or data management | Import leads (<= 50,000)
With Web-to-Lead,you car add up to 500 new leads a day.
In cross-object formulas, you cannot reference record owner merge fields for any object
Long text area, encrypted, and Description fields are not available for use in formulas
| Salesforce Edition | Personal Edition | Contact Manager | Group Edition | Professional Edition | Enterprise Edition | Unlimited Edition | Developer Edition |
| Custom Fields per Object | 5 | 25 | 100 | 100 | 500 | 800 | 500 |
| Total Custom Objects | NA | 5 | 50 | 50 | 200 | 2,000 | 400 |
| Maximum number of Apex classes scheduled concurrently | 100. In Developer Edition orgs the limit is 5. |
| Maximum number of batch Apex jobs queued or active concurrently | 5 |
Deleted custom fields counts against the maximum number of custom fields allowed in your
organization.
Salesforce uses the round half up tie-breaking rule for numbers in formula fields.
In account formulas, all business account fields are available as merge fields. However, account fields
exclusive to person accounts such as Birthdate and Email are not available.
IF(IsTask, "This is a task", "This is an event")
The output of your formula must be less than 19 digits.
Salesforce allows a maximum of ten (10) unique relationships per object in cross-object formulas.
For example, if two different
formulas on opportunities reference two different fields of an associated account, only one unique
relationship exists (from opportunities to accounts).
In cross-object formulas, you cannot reference merge fields for objects related to activities. For
example, merge fields for contacts and accounts are not available in task and event formulas.
In cross-object formulas, you cannot reference record owner merge fields for any object. For example,
the opportunity owner's Role merge field is not available in opportunity formulas
Products are the individual items that you sell on your opportunities and quotes.
You can create a
product and associate it with a price in a price book. Each product can exist in many different price books
with many different prices
Comments
Post a Comment