Dev401-016:Data Management: Data management Overview
Course Objectives
1.List typical data management operations.
2.Define upsert and external ID.
3.List typical use cases where upsert is useful.
4.List some tools available to perform data management operations.
5.Execute the Data Loader via its command line interface.
Module Objectives
1.List typical data management operations.
2.List 3 ways to obtain record IDs.
3.State typical use case for modifiable system field feature.
4.Locate resource explaining algorithm for converting 15-digit IDs to 18-digit form.
5.Explain tupical situation where the use of the 15-digit ID can cause problems.
Module Agenda
1.Essential Data Management Oprrations
2.Record IDs
3.Object Relationships
4.Modifiable System Fields
Universal Containers Scenario
1.Universal Containers(UC) has decided to standardize all of its recruiting activities onto the Recruiting app.
2.UC has recruiting data from a variety of sources - (i.e. paper forms, Excel spreadsheets,legacy HR system) that it would like to load into the Recruiting app.
3.UC needs to assemble and prepare the recruiting data it has for efficient migration into the Recruiting app.
4.UC needs to learn data management capabilities of the platform and how to use them.
Essential Data management Operations
1.Exporting Data
- Get reference IDs for insert/updates
- Download records for backup
2.Inserting Data
- Load users
- Load existing Positions
3.Updating Data
- De-duplicate existing data
- Introduce Records Types
4.Deleting Data
- Free up space used by too much legacy data
- Fix mistakes!
Record IDs
1.Unique identifier of a record.
1,Analogous to a primary or foreign key field in a database table.
3.Salesforce generates an ID value when a new record is created i.e. a00D0000005iTiz
Where to Get Salesforce IDs
1.IDs may be obtained 3 ways:
- URL
- Report
- Web Services API, e.g., the Data Loader
Format for Record IDs
1.Salesforce.com Object IDs come in 2 forms:
- 15-digit case-sensitive form
- 18-digit case-insensitive form
2.Reports and Object IDs
- Reports (and office Edition) return 15-digit IDs
- Report framework does not expose IDs for all objects
3.API and Object IDs
- API always returns 18-digit IDs
- API will accept either the 15-digit or 18-digit format
Object Relationships
1.Relationships exist between objects, for example:
- All Positions have an owner
- Candidates are related to Position through a job Application
- Reviews are associated to a Job Application
2.Relationships are expressed through:
- Related lists and lookups in the application
- IDs(foreign keys) in the database
Determine the Order to Load Data
1.Object relationships introduce data dependencies.
2.Dependencies dedicate the order of data load.
3.To load Review data, you must:
- Load Users
- Load Positions
- Load Candidates
- Load Job Applications
- Load Reviews
Optional Feature: Modifiable System Fields
1.What Does IT Do?
- Allows you to set Created Date, Created By, last Update Date, Last Update By
- Useful for migrating data from external systems and preserving history
- Generally, these fields are Read-Only
2.How Do You Get It?
- Contact salesforce.com
- Customer Support will enable
Modifiable System Fields
1.Only accessible through API.
2.Backwards compatible with all SOAP-based API's
3.Restricted to Account, Opportunity, Contact, lead, Case, Task, and Event Standard Objects.
4.Works for all Custom Objects
5.Read-only for existing records
Best Practice:enable only for initial data migration
Review
1.Name 3 ways you can obtain a record's ID?
URL,Report,Web Service
2.Why can it be dangerous to work with the 15-digit case sensitive form of the record ID?
??
3.True of False:The Created Date can be updated for a record via the API as long as the Modifiable System Fields feature is turned on.
False