Import and Export Problems
On this page
7.9 Import and Export Problems
Locate reading, mapping, matching, checking, writing, or output failures separately. Preview is not committed import; text success is not complete photo export.
7.9.1 Source Reading and Structure
Keep originals and inspect copies. Check Excel worksheet/header/start/merges; CSV encoding/separator/qualifier/multiline; JSON/XML record paths; Word/Markdown table/key-value/paragraph mode. Convert protected/damaged/unsupported files properly, not by extension renaming. Inspect first/middle/last records. Both previews currently show at most 200 rows, not source size or proof that later records passed; use wizard totals/results.
7.9.2 Types, Identifiers, and Photo Matching
Preserve numbers like 00123 as text from the source. Destination text cannot restore stripped zeros/truncated digits. Use unambiguous four-digit-year dates, inspect conversions, numeric ranges/separators, and NULL/empty/default meaning rather than filling everything with zero/false. Check photo names/paths/extensions/subfolders and missing/multiple/overwrite policy. Files over 20 MB fail current synchronization checks. First-by-filename is not a legitimate remedy for ambiguous people.
Figure 7.9-1. Show dummy source and converted values for zeros, dates, and photo paths in English. Never suggest truncated source digits can be automatically restored.
7.9.3 Keys, Modes, and Permissions
Verify target, mapping, main-table key, destination uniqueness, and no blank/duplicate batch keys. Names/display labels are not generally update keys/foreign IDs.
| Mode | Misunderstanding | Action |
|---|---|---|
| Add Only | Existing people will update | Inspect constraints/results; do not repeat the entire source. |
| Update by Match Key | Unmatched skipped means lost | Verify key/zeros; create only through approved workflow. |
| Add or Update | Only one type of change will happen | Check both creation/replacement scope and permissions in isolation. |
Wizard access/check success does not establish all write rights or immunity to concurrency/constraints. Recheck after source/mapping changes.
7.9.4 Partial Success, Cancellation, and Retry
Stop normally and preserve successful/failed/skipped lists. After forced exit/disconnect, query keys to establish completed writes rather than assuming rollback. For a fictitious batch of 100 with 92 successes, 5 failures, and 3 skips, verify the 92, repair the 5, and explain the 3; never repeat all 100 in Add Only. If results are lost, compare unique keys before choosing retry scope.
Separate constraints, lengths, photos, and external effects. Trial a few known failures after repair and reread. Only approved full consistent recovery should replace an unrecoverable batch; deleting successful people to start over is not the default.
7.9.5 Missing Exports or Unreadable Files
Export uses loaded, filtered rows and optionally checked rows within them, not automatically the whole database. Inspect SQL/user/search/group/scope/count/fields and data/photos mode. For missing images check source, blank/duplicate names, writes, and item errors; a visible interface image is not necessarily binary export support. Check space, completeness, actual format/extension, encoding, and target reader. Preserve unique results instead of overwriting open files. Sample IDs/dates/photos; exports are not complete backups.
Figure 7.9-2. Show fictitious 92/5/3 results, failed-only reconciliation, and exported record/photo counts. Hide paths and people; do not run production imports for illustrations.