Skip to main content

Cleaner FAQ

What kind of problem is Cleaner best for?​

Cleaner is best for problems where the main goal is to make values more consistent.

Typical examples include trimming extra spaces, replacing placeholder values with blanks, replacing recurring text values, and standardizing dates or numbers into a consistent format.

Which Rule actions are available?​

The Cleaner Rule editor shows these actions:

  • Trim spaces
  • Blank value cleanup
  • Find and replace text
  • Standardize data type

Each Rule also has a required Plain-language name, a required Apply to columns target, and a Use this rule switch.

Can I apply a Rule to every Field?​

Yes. In Apply to columns, use * to apply a Rule to every available Field.

Use this carefully. Applying a Rule to every Field can change more data than intended and may affect performance.

Does Cleaner show a before-and-after preview before I run it?​

The Cleaner authoring screen shows a Selected columns preview and Rule summaries. Those help you verify the Fields and Rules before saving.

It does not show a full before-and-after preview of cleaned values before the Run. For new or changed Configurations, run Cleaner on a small representative File first and review the output.

Should I test on a small File first?​

Yes. A small, representative File is usually a practical way to confirm that a Configuration behaves the way you expect.

This is especially important when:

  • the Configuration is new
  • the Rules were recently edited
  • the source data comes from a new process or team
  • the output will feed an important downstream workflow

Can I reuse the same Configuration later?​

Yes. A saved Configuration allows you to apply the same standardization logic whenever a similar File arrives again.

Before reusing it, confirm that the incoming File still matches the Import Config and includes the Fields referenced by enabled Rules.

What should I review after a Run?​

Review representative Records and confirm that the business outcome is correct, not just that the Run completed successfully.

At minimum, check that:

  • the intended values changed
  • unintended values did not change
  • the cleaned output matches your expected standard
  • the Problems count is reasonable
  • the Cells changed count is reasonable
  • the result is ready for the next step in the workflow

What is the biggest mistake to avoid?​

Trying to solve too many unrelated problems in one Configuration.

Cleaner works best when each Configuration has a clear purpose. Focused Configurations are easier to test, safer to reuse, and easier for other users to understand.

How do I know whether a value should be standardized?​

Ask whether the variation is causing a real business problem.

If inconsistent formatting or wording is making the data harder to report on, validate, match, export, or interpret consistently, it is often a good candidate for Cleaner.

If the variation carries meaningful nuance, pause before standardizing it.

What if I am not sure which Fields to include?​

Start with the Fields that clearly affect the business outcome you are trying to improve.

Avoid cleaning a Field "just in case." If the expected cleaned result is unclear, it is better to leave that Field out until the standard is better defined.

What if the result is not what I expected?​

Go back to the Configuration, identify which Rule or assumption needs adjustment, and test again on a smaller File.

That iteration is normal. Cleaner Configurations often improve over a few review cycles before they become stable reusable assets.

Is Cleaner only useful for large datasets?​

No. Cleaner can be valuable for both small and large datasets.

The main question is not File size. It is whether you are applying repeatable standardization logic that is worth saving and reusing.

What if I am not sure this is the right WebHammers Tool?​

Use Cleaner when the question is, "How do I make these values more consistent?"

If the real task is filtering Records, comparing sources, joining Files, splitting outputs, identifying duplicates, or reducing exposure of sensitive data, another WebHammers Tool is usually a better fit.