Course 1.6 · Curriculum 2026.1
Data management: imports, duplicates, and cleaning up after someone else
Load data without corrupting the org, and find the corruption already in it. Taught around phantom invoice data found in a real migration.
- Estimated effort
- 5 hr
- Lessons
- 42
- Modules
- 7
- Material
- 5 hr
Estimated effort is the sum of the lesson and lab times in this version of the course. It is not video runtime, which is lower.
Canadian dollars. One learner, lifetime access to this course version. Tax extra.
1 lesson free to preview
This course does not issue a certificate on its own. It counts toward the paths listed below, and those do.
01What you will learn
7 capabilities, stated as things you can do
Each one is what you should be able to do at the end, not what the course covers. If an outcome is not testable, it is not an outcome.
- Load a related dataset in the right order using external ids rather than record ids.
- Choose between Data Import Wizard, Data Loader and a query tool for a given job.
- Design a duplicate rule and matching rule that catch real duplicates without blocking real work.
- Reconcile a loaded dataset against its source and itemise what did not key.
- Find inherited bad data by reconciling a reported total against its own line items.
- Delete safely: soft delete, recycle bin, hard delete, and what each does to a rollup.
- Write a data dictionary an auditor can read.
02Curriculum
7 modules, 42 lessons
Every lesson shows its length and its type. A SCORM lesson looks like any other lesson, which is the point of ingesting packages rather than linking out to them.
7 modules · 42 lessons · 5 hr of material
Order of operations, external ids, and upsert. Most import disasters are a relationship loaded before its parent.
- VideoImport Wizard, Data Loader, or a query tool: choosing by the job6 min
- VideoExternal ids and upsert, and why record ids are the wrong keyA record id is created by the target org. An external id comes from the source system, so a re-run updates instead of duplicating.Preview7 min
- ReadingTurning automation off during a load, and the risk of doing so6 min
- VideoBulk API versus REST, and the batch size that actually matters6 min
- VideoField mapping, and the column that silently did not load7 min
- LabLab: load 2,000 accounts and 8,000 contacts, twice, idempotently6 min
A parent-child dataset has exactly one order that works. Everything else fails partway through, usually quietly.
- VideoLoading a parent-child dataset in the right order7 min
- VideoSelf-relationships and the load that has to run twice6 min
- ReadingComposite requests, and loading two objects in one call7 min
- VideoRollback behaviour, and what a partial failure actually leaves behind6 min
- VideoLoad logs: what to keep, and for how long7 min
- LabLab: load a five-object dataset with two circular-looking relationships6 min
Matching rules, duplicate rules and merge. Tuned so they catch the duplicate and do not block the salesperson at 4pm on a Friday.
- VideoMatching rules: fuzzy, exact, and the fields that actually discriminate6 min
- VideoDuplicate rules: alert, block, and the report nobody reads7 min
- ReadingTuning a matching rule so it stops blocking real work6 min
- VideoMerging records, and what merge does to related lists7 min
- VideoBulk deduplication, and the merge you cannot undo6 min
- LabLab: tune a duplicate rule against a seeded dataset7 min
Soft delete, recycle bin, hard delete, and what each one does to a rollup someone downstream is trusting.
- VideoDeleting safely: soft delete, recycle bin, hard delete, and rollups6 min
- VideoCascade delete, and the master-detail child you did not mean to lose6 min
- ReadingMass delete, and the permission that should not be given lightly7 min
- VideoArchiving instead of deleting, and when that is the honest choice6 min
- LabLab: delete a batch of records and verify every rollup afterward7 min
- VideoData retention, and the policy you write down before you need it6 min
A reported lifetime invoicing figure was inflated by phantom data inherited from a migration. This module is where that forensic pass starts.
- VideoThe reported total that did not reconcileThe headline number came from a rollup. The line items behind it did not sum to it. That gap is where every forensic pass starts.7 min
- Video31 percent of quote lines carrying no tax code, found by querying rather than asking6 min
- ReadingWhere a headline number actually comes from, and why that matters6 min
- VideoA reported lifetime invoicing total, and the gap that did not add up7 min
- VideoIsolating inherited records: created date, owner, and the load signature6 min
- LabLab: find the gap between a headline and its own line items7 min
Three-way reconciliation across the old system, the new one and the accounting ledger. 97 percent keyed, and the unkeyed residue itemised rather than hidden.
- VideoReconciling a total against its own line itemsThree-way reconciliation across the old system, the new one and the accounting ledger. 97% keyed, and the unkeyed residue itemised rather than hidden.6 min
- VideoTwo mistake invoices, and how they were found7 min
- ReadingThe corrected figure, across 2,860 invoices, and why the count matters too6 min
- VideoThree-way reconciliation across two retired systems and a live one7 min
- VideoThe residue you itemise instead of hiding: the residue, named6 min
- LabLab: reconcile a total across three systems and itemise what did not key7 min
A clean-up is not finished when the number is fixed. It is finished when someone else can read why it changed.
- VideoWrite a data dictionary an auditor can read7 min
- VideoThe proof step: sweeping the table after a fix and reporting zero hits6 min
- ReadingWhat a clean-up report says to the person who has to sign off on it7 min
- LabLab: find and quantify the phantom data in a seeded orgThe capstone lab. Reconcile a seeded lifetime invoicing figure against its line items and isolate every inherited record.28 min
- VideoHanding a corrected number to someone who has to defend it6 min
- QuizCheck: data management14 min
03Before you start
What you need first
Assumed knowledge and setup
- Course 1.3. External ids and relationships are the whole mechanism here.
- Data Loader or a similar client installed, plus a spreadsheet tool.
- A Developer Edition org you are willing to load several thousand test records into.
Courses that come first
Part of these paths
- Salesforce AdministratorShareCo Certified Administrator
- The Full StackShareCo Certified Platform Engineer
04Who teaches it
Ege Taskent
Salesforce Developer, Certified Platform Administrator
The credential, and the rollout. The half of an implementation where people actually start using the thing.
Salesforce Certified Platform Administrator
05Reviews
No learner reviews yet
This course has not been taken by enough people to publish an honest rating, and we will not print invented quotes on a page that sells verification discipline. Here is what we can evidence instead.
- Assessment
- Lesson checks onlyThis course carries lesson checks. The certificate is issued by the path assessment, not by this course.
- Curriculum version
- 2026.1You enrol into a version. Content changes do not move you mid-course, and your required-lesson count is snapshotted at enrollment.
- Refunds
- 14 daysFull refund within 14 days if you have completed under a quarter of the required lessons. Stated here rather than in a footer.
Start 1.6
Enrol as an individual, or buy seats and assign this course to your team. Progress is reported per lesson, per module and per path.
- 5 hr estimated effort, labs included
- Lifetime access to the version you enrol in
- A ShareCo certificate is not a Salesforce certification