AUSTRALIAN MANAGEMENT. GLOBAL CAPABILITY.12-month work warranty →
CDXCAD & DOCUMENTATION EXPERTISE
Let’s talk ↗

HOME / ACADEMY

CDX Academy

← All 40 lessons

Digital information · Lesson 39 · Approx. 7 minutes including practice

Sandbox imports and reconciliation

Test imports in an isolated environment with approved data. Compare record counts, totals and relationships, then inspect representative records. Retain logs and rollback instructions before any production cutover is authorised.

Follow the information flow

Step 1: Approved sample

A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.

Reconcile more than record counts

A sandbox import is a controlled test in an isolated environment using authorised data. Successful execution does not prove that relationships, values and business meaning are correct. Compare record counts, relevant totals, parent-child relationships and representative records. Identify what failed, what was skipped and what was transformed. Keep the input dataset and mapping version together so the result can be reproduced.

Prepare and check the work

Define acceptance criteria before the test and record the expected outcomes. Review exception logs and investigate unexplained differences rather than adjusting totals to match. Confirm the rollback approach and responsibilities with the system owner. A production cutover needs explicit authorisation and appropriate access controls; completing a sandbox test does not grant permission to change live business data.

Worked example · demonstration only

An import reports all rows accepted, but several items are linked to the wrong supplier because a mapping used a non-unique name. Record counts alone would miss the error. Reconcile relationships and correct the mapping before another test.

Guided practice and review evidence

Use only a demonstration dataset for this exercise: Write an acceptance checklist for a 100-record trial import. Before starting, write down the question the finished record should answer and identify the source information you would need on a real job. Keep a separate list of missing inputs. Prepare a first draft, then compare it with the topic-specific checks above. Ask another person to follow your references without explaining them verbally. Record where they hesitate, what information they cannot locate and any different interpretation. Keep a brief review log with four columns: observation, proposed action, responsible reviewer and closure evidence. Revise the example and repeat the information-finding check. Your evidence of completion is the revised demonstration record plus that log, not simply time spent reading. Do not upload client information to the academy or practise on operating equipment.

What good completion looks like

A useful result can be understood by someone who did not prepare it. They can identify its purpose, applicable item, source and review status, and they can distinguish confirmed information from unresolved questions. Pay particular attention to this failure mode: A successful import status does not prove the data is complete or correct. Check the output in the format the recipient will use. A native file, spreadsheet and exported PDF can expose different problems. Keep the source revision and the issued output linked, and record any limitations of the handover. On a real project, follow the customer's authorised checking and approval arrangements before the information is used. The knowledge check below tests understanding of this lesson; it does not assess practical competence or authorise regulated work.

Practical workflow

  1. Establish the source: identify the approved input, document revision and person responsible for its technical content. Record missing information as an open question.
  2. Prepare a small representative example before applying the approach to a whole project. Check identifiers, units, references and the intended reader’s needs.
  3. Ask the nominated reviewer to check technical meaning. Capture the response, resolve comments and issue only under the agreed document-control process.

Review checklist

  • Can another reader identify the source and applicable revision?
  • Are assumptions and unresolved decisions clearly recorded?
  • Is there evidence of the required review before issue?

Knowledge check

Answer all three correctly to record completion. You can review the lesson and retry.

1. What is required before production cutover?
2. What should you do with missing or conflicting technical information?
3. What does this academy completion demonstrate?
Sign in to record completion

Educational material and demonstration examples. Not accredited training, practical competency assessment or authority to perform regulated work. Use current approved sources and your responsible technical authority on real projects.

LET’S MAKE YOUR NEXT PROJECT CLEARER

From your technical knowledge.
To a professional deliverable.

Request a quote