The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Checking a Salesforce Data Export is complete before migrating (opens in a new tab)

You will learn how to confirm every archive, object and file arrived from a Data Export and how to reconcile CSV row counts against SOQL COUNT() before a target load.

Why read this

You will also learn the documented gaps, such as excluded Formula Fields and Recycle Bin data.

  1. Download every archive within 48 hours
  2. Confirm each expected object CSV is present
  3. Confirm attachments and files were included
  4. Compare each CSV row count to SOQL COUNT()
A sequence of checks to run on a Data Export before migrating from it

A finished Data Export job does not guarantee a complete file set. Archives can be missing, expire after 48 hours, or be overwritten when a new export is queued, so the piece recommends downloading every zip promptly and counting them against what was saved. It also flags that Sandboxes do not support Data Export and that the scheduling user receives the download email.

The article then covers checking objects and files: forgetting to tick the options for attachments or Salesforce Files leaves files out, Formula Fields and Roll-Up Summary Fields are always excluded, and Data Loader does not obtain physical attachments. Chatter and content files in weekly exports come as MIME files named after the record ID, and Data Loader’s ContentDocument export only returns files the user owns or that are shared directly with them unless Query All Files is granted.

For row counts, the author compares each CSV’s data rows to a SOQL COUNT() run by a user with comparable visibility, matching the export mode to the query, and counting outside Excel for files above about 1,048,576 rows. A worked spreadsheet example with Match and Review status formulas shows how a short Contact file is caught. A matching count does not prove that attachments open or that parent relationships are correct.

Read the original at dev.to (opens in a new tab)

Worth reading?