Skip to main content

Run Cleaner

After you have a saved Cleaner Configuration, you can run Cleaner on an input File.

A Cleaner Run applies the selected Configuration and enabled Rules to the File you choose. The original source File is not overwritten. The Run creates output you can review and download.

Before you begin​

Confirm that:

  • the Cleaner Configuration is the one you intend to use
  • the Configuration has a current saved revision
  • the input File matches the Import Config used by the Cleaner Configuration
  • the File includes the Fields referenced by enabled Rules
  • you know which Fields are expected to change
  • someone will review the output before it is used downstream

Typical run steps​

A standard Cleaner Run usually looks like this:

  1. Open Cleaner Configurations.
  2. Select Run for the Configuration you want to use.
  3. On Run Cleaner, optionally edit the Run name.
  4. Under Choose input, use Select file to choose the input File.
  5. Select Run.
  6. Watch Progress while Cleaner imports, processes, and exports the dataset.
  7. When the Run completes, review the completion metrics and available Downloads.
  8. Open Cleaner Job History later if you need to review the Run again.

Run setup​

The Run screen includes these user-facing areas:

AreaWhat it means
Run nameOptional friendly name that makes the Run easier to find in Job history.
Choose inputThe input area where you select the File for this Run.
Select fileThe file picker for the input File.
AuditOptional setting for detailed Run review information when available.
RunStarts the Run.
CancelStops the Run while it is in progress.

Progress and completion​

During a Run, Cleaner shows progress information such as:

  • Status
  • Rows read
  • Rows inserted
  • Problems
  • Rows output
  • Rows removed
  • elapsed time and estimated remaining time while the Run is active

When the Run finishes, Cleaner shows a completion area with the Run result and counts for Records read, inserted, problems, and output.

Output and downloads​

The main output is the cleaned File. On the completion screen, it appears in Downloads when the output is ready.

If Cleaner records problems during processing, a problems download may also be available on the completion screen. Problems are most likely when a data type standardization Rule cannot parse a value.

The Run also stores summary information that appears in Cleaner Job History and Cleaner Job Summary.

Cleaner Job History​

The Cleaner Job History screen lists recent local Cleaner Runs. It shows:

  • Job
  • Started
  • Duration
  • Status
  • Imported
  • Exported
  • Problems
  • Cells changed
  • Summary

Use Summary to open the detailed page for a Run.

Cleaner Job Summary​

The Cleaner Job Summary page shows the selected Run and includes:

  • Job details
  • last Run time
  • status
  • input File
  • Rows imported
  • Rows processed
  • Rows exported
  • Problems
  • Cells changed
  • Cleaned file

Use Download in the Cleaned file section to download the cleaned output when it is ready.

What to review after the Run​

Do not check only whether the Run completed. Review whether the result is correct.

Inspect representative Records and ask:

  • Were the intended Fields cleaned?
  • Were the right values changed?
  • Did any values change that should have remained unchanged?
  • Do the cleaned values match the business standard you intended?
  • Are the Problems and Cells changed counts reasonable?
  • Is the output ready for reporting, export, import, or handoff?

If the result is not what you expected​

If the output is not correct, do not move the dataset forward.

Instead:

  1. Return to the Cleaner Configuration.
  2. Check the Rule order, target Fields, and Rule options.
  3. Adjust the Configuration.
  4. Save a new draft or publish the revised Configuration when ready.
  5. Run again on a small representative File before using the output downstream.

Common mistakes to avoid​

  • running Cleaner against a File that does not match the selected Import Config
  • assuming a completed Run means the business result is correct
  • ignoring the Problems count
  • skipping review of Records that were expected to stay unchanged
  • reusing a Configuration after the source File format changes without checking Field names