Record IDs Data import/export Mass Transfer External IDs Flashcards
Record IDs Data import/export Mass Transfer
Two forms of Record ID
15-character case sensitive shows in browser reports, lists & formula fields 18-character case insensitive to account for excel used for API (including dataloader) first 3 characters define the object
Avoid hard coding Record ID into anything
e.g. A formula field to test for a record type ID. The record type id in a sandbox will be different to the sandbox formulas will break (unless it’s a full sandbox)
Preferred method is to compare the ‘name’ of the record type. (RecordType.DeveloperName)
Know the differences between the Import Wizard & the Data Loader
Need to understand differences to apply to scenarios.
Wizard: <= 100Mb
Workflows can be bypassed
Data Loader
Can update any object
No limit to the records
no de-dupe
no transformation
could be run from command line (ie can be shceduled)
can insert, update, upsert, delete, export
can use .csv or JDBC connection
bulk API – moves data files to server so it’s a “local” load (goes faster).
Dataloader is API
know the authentication requirements of an API login vs. a web-based login
Mass Transfer
Used to update ownership of Account, Leads and Custom Objects.
Must identify who it’s going to, but not from.
Can only transfer 250 at a time.
Cannot be easily undone.
What happens when accounts are transferred?
Any notes that belong to the existing owner. All contacts that belong to the existing owner. All opportunities (including closed opportunities if you select the Transfer closed opportunities checkbox below) that belong to the existing owner. All open activities assigned to the existing owner. Note that completed activities will not be transferred. The new owner might need to edit sharing.
External IDs
Designed for Integration
This is a field attribute on a custom field (text, email, number)
Also should mark field as Unique & Case sensitive.
It gets indexed and can be searched
Best use is Upsert capability of the SOQL language
Weekly Data Export
Only reason he’s seen it used is for regulatory compliance. Re-building an SF db using it would mean that all the IDs would change and stuff.
Mass Delete
Can only be used for Accounts, Contacts, Activities, Leads, Cases, Solutions, Products
Cannot delete from custom objects
Accounts will delete cascade to contacts etc.
Can delete 200 at a time, goes to recycle bin
Data Migration best practices
Cannot assign records to in-active users (need to activate, load, deactivate - can get temp user limit upped to make it possible)
Insertable System fields, allow you to preserve creation date, user, etc. from legacy systems.
Utilize external IDs
Avoid too much activity history
Turn off work flow rules
List Views
Available on most tabs
Only one object type
Customizable (filters, columns)
Can be updated by end users