Scribd
Upload
5 views

soql

Uploaded by

rybkazoceanu
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

soql

Uploaded by

rybkazoceanu
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

•Create roll-up summary fields on:

•Any custom object that is on the master side of a master-detail relationship


•Any standard object that is on the master side of a master-detail relationship with a custom object
•Opportunities using the values of opportunity products related to the opportunity
•Accounts using the values of related opportunities
•Campaigns using campaign member status or the values of campaign member custom fields
Note Campaign member custom formula fields that reference fields derived from leads or
contacts aren’t supported.
•Thetypes of fields you can calculate in a roll-up summary field depend on the type of calculation. For
example:

•Number, currency, and percent fields are available when you select SUM as the roll-up type.

•Number, currency, percent, date, and date/time fields are available when you select MIN or MAX as
the roll-up type.
•Sometimes you can’t change the field type of a field that you reference in a roll-up summary field.
•Make sure that the filter for your roll-up summary doesn’t encounter a formula field that results in #Error!. If
one of your filter criteria uses a formula field that results in an error, no matches are returned for that filter
criterion. For example, your roll-up summary filter is “Formula Field equals 10”. Two records contain errors,
and one contains the value “10” in that field. In this case, your summary includes only the record with the
value “10.”

•Salesforce doesn’t recalculate the value of campaign roll-up summary fields when a lead or contact is
deleted. Select the Force a mass recalculation of this field option on the edit page of the roll-up summary
field to manually recalculate the value.

•You can’t use long text area, multi-select picklist, Description fields, system fields like Last Activity,
cross-object formula fields, and lookup fields in the field column of roll-up summary filters.
•Auto number fields aren’t available as the field to aggregate in a roll-up summary field.
•After you create a roll-up summary field on an object, you can’t convert the object’s master-detail
relationship into a lookup relationship.
•Roll-up summary fields aren’t available for mapping lead fields of converted leads.

How Salesforce Processes Validation Rules


Salesforce processes rules in the following order:
1.Validation rules
2.Assignment rules
3.Auto-response rules
4.Workflow rules (with immediate actions)
5.Escalation rules
In addition,
•When one validation rule fails, Salesforce continues to check other validation rules on that field or
other fields on the page and displays all error messages at once.
•If
validation rules exist for activities and you create an activity during lead conversion, the lead
converts but a task isn’t created.
•Validation
rules are only enforced during lead conversion if validation and triggers for lead
conversion are enabled in your organization.
•Campaign hierarchies ignore validation rules.
•Salesforceruns validation rules before it creates records submitted via Web-to-Lead and Web-to-
Case and then creates records that have valid values.
•Togive a default value to a division field before the validation rule evaluation, the division field
must be on the page layout.
•Validation rules continue to run on individual records if the owner is changed. If the Mass Transfer
tool is used to change the ownership of multiple records, however, validation rules don’t run on
those records.

Introduction to Data Import


You can easily import external data into Salesforce. Supported data sources include any program that can
save data in the comma delimited text format (.csv).
Salesforce offers two main methods for importing data.
•Data Import Wizard—this tool, accessible through the Setup menu, lets you import data in
common standard objects, such as contacts, leads, accounts, as well as data in custom objects. It can
import up to 50,000 records at a time. It provides a simple interface to specify the configuration
parameters, data sources, and the field mappings that map the field names in your import file with
the field names in Salesforce.
•Data Loader—this is a client application that can import up to 150 million records at a time, of any
data type, either from files or a database connection. It can be operated either through the user
interface or the command line. In the latter case, you need to specify data sources, field mappings,
and other parameters via configuration files. This makes it possible to automate the import process,
using API calls.
With both methods, the number of records you can import depends on your permissions, the type of
data you’re importing, and the overall data storage limits for your organization. The type of objects
you can import depends on your edition.

Use the Data Import Wizard When:


•Youneed to load less than 50,000 records.
•The objects you need to import are supported by the wizard.
•You don’t need the import process to be automated.
Use Data Loader When:
•You need to load 50,000 to 150 million records. If you need to load more than 150 million records,
we recommend you work with a Salesforce partner or visit the AppExchange for a suitable partner
product.
•You need to load into an object that is not supported by the Data Import Wizard.
•You want to schedule regular data loads, such as nightly imports.
Data Loader uses the SOAP API to process records. For faster processing, you can configure it to use
the Bulk API instead. The Bulk API is optimized to load a large number of records simultaneously. It is
faster than the SOAP API due to parallel processing and fewer network round-trips.
This information can help you integrate your imported data into Salesforce.
•New Values for Picklists and Multi-Select Picklists—If you import a picklist value that doesn’t match
an existing picklist value:
•For an unrestricted picklist, the Data Import Wizard uses the value that’s in the import file.
•For a restricted picklist, the Data Import Wizard uses the picklist’s default value.

•Multi-Select Picklists—To import multiple values into a multi-select picklist, separate the values by
a semicolon in your import file.
•Checkboxes—To import data into a checkbox field, use 1 for checked values and 0 for unchecked
values.
•Default Values—For picklist, multi-select picklist, and checkbox fields, if you do not map the field in
the import wizard, the default value for the field, if any, is automatically inserted into the new or
updated record.
•Date/Time Fields—Ensure that the format of any date/time fields you are importing matches how
they display in Salesforce per your locale setting.
•Formula Fields—Formula fields cannot accept imported data because they are read-only.
•Field Validation Rules—Salesforce runs validation rules on records before they are imported.
Records that fail validation aren’t imported. Consider deactivating the appropriate validation rules
before running an import if they affect the records you are importing.
Salesforce offers two main methods for exporting data.

•Data Export Service—an in-browser service, accessible through the Setup menu. It allows you to
export data manually once every 7 days (for weekly export) or 29 days (for monthly export). You can
also export data automatically at weekly or monthly intervals. Weekly exports are available in
Enterprise, Performance, and Unlimited Editions. In Professional Edition and Developer Edition, you
can generate backup files only every 29 days, or automatically at monthly intervals only.
•Data Loader—a client application that you must install separately. It can be operated either through
the user interface or the command line. The latter option is useful if you want to automate the export
process, or use APIs to integrate with another system.

You might also like