Output Structure & Audit Logs

Appended Result Columns

For every Data Group you mapped during the setup phase, the Data Cleaner appends a set of new columns to the end of your file. These columns contain the validation results.

The appended columns follow a strict naming convention based on the mapped group (e.g., location_result, email_updated).

Here is the technical breakdown of the four primary output columns:

• _result (Status): A clear text string representing the validation state. Common values include:
  • valid: The original data was correct.
  • corrected: The data contained errors (e.g., typos, missing diacritics) but was successfully fixed by the API.
  • invalid: The data is completely incorrect or does not exist.
  • invalid (suggestion available): The data is incorrect, but the API found a highly probable alternative.
• _updated (Clean Value): The corrected version of your data. If Foxentry fixed a typo, the clean string is placed here. If the original data was already valid, this column mirrors the original value.
• _suggestion (Alternative): If the API flagged a record as invalid but found a probable match, the suggested string is output here. You can manually review these suggestions later.
• _note (Error/Action Log): Detailed, machine-readable notes or error messages explaining exactly what was wrong or what specific normalization rules were applied (e.g., Fixed: streetWithNumber or Domain does not exist).

Full Datascope Columns

If you enabled the Enrich data (Full Datascope) toggle, additional columns containing the parsed JSON metadata will be appended after the standard result columns (e.g., company_vatStatus, company_employees, location_geometry_lat).

Request Logs & Technical Auditing

Foxentry Data Cleaner features a built-in HTTP request viewer for deep technical auditing and debugging.

By default, request logging is disabled to protect data privacy and save local disk space. You can easily enable it by checking the corresponding box on the final Order (Step 4) page before starting the validation.

Viewing the Logs

If logging is enabled for a specific run, the application stores the complete HTTP request sent to the API and the full JSON response received from the server.

To access the logs:

1. Click the Logs button in the top navigation bar of the application.
2. The interactive viewer allows you to browse all recorded HTTP transactions.
3. You can filter the logs by Status Codes (e.g., isolating 4xx client errors or 5xx server errors).
4. Click on any specific request to inspect the raw JSON payload and the corresponding API response, allowing developers to easily debug mapping issues or review API behavior.

Next step: Running into errors? Check out the final Troubleshooting & QNA section to resolve common mapping and execution issues.