How to Run Data Validation Tool

The Data Validation Tool in Pricefx lets you validate data before uploading it to a partition or using it in other processes such as Data Upload or accelerator deployment. This guide describes how to select validation scenarios, provide data sources, map file fields to Pricefx structures, and review and download validation results.

Navigation: Account > Data Tools > Data Validation Tool

Prerequisites

Before you start, confirm the following:

• Account access: You have access to a Pricefx account with the Data Validation Tool enabled under Data Tools.

• Data files: You have the files you want to validate, or the files were uploaded previously under your account. The tool supports CSV and Excel (.xls, .xlsx) files.

• Partition access: If a selected validation scenario requires a partition, you have access to the relevant partition.

Start New Validation

1. Go to Account > Data Tools > Data Validation Tool.

2. On the Data Validation Tool landing page, click Start new validation.

The landing page displays the text Start a new data validation and the description Quickly validate data to detect missing values, duplicates, and rule conflicts with clear reports and fix suggestions. The tool opens a four-step wizard with these steps: Validations setup, Data source setup, Data mapping, and Report Overview.

Step 1: Select Validation Scenarios

Use this step to choose the validation scenarios and checks to run against your files.

1. On the Validations setup step, review the heading Configure validation scenarios.

2. When you enter the step with nothing selected, the Add validation scenarios dialog opens by itself. If you return to the step with scenarios already selected, or navigate back to it, the dialog stays closed and you open it with Add more scenarios.

3. Click Add more scenarios.

4. In the Add validation scenarios dialog, use the Type to find... search field to locate a scenario, or scroll the list.

5. Select the checkbox for each scenario you want to run. For the full list of scenarios and what each one checks, see Validation Scenarios on the Data Validation Tool overview.

6. Click Confirm to add the selected scenarios.

7. Optionally, clear individual checks on a scenario card to narrow what that scenario runs. Clearing the last check does not remove the scenario from the step: the card stays and turns inactive, and an inactive scenario does not block Continue. To take a scenario off the step, clear it in the Add validation scenarios dialog.

8. Click Continue to proceed to the next step.

Step 2: Provide Data Sources

Use this step to provide the files for the selected validation scenarios.

1. On the Data source setup step, review the Data Upload heading and the instruction: Please provide files for the selected validation scenarios. You may upload a new file or select one that has been uploaded recently.

2. If a selected scenario requires a partition, select the partition. In the Basic file check (any file) scenario, selecting a partition is optional; when you select one, you can choose the Entity Type and Entity Name for each added file so that the metadata (data types, mandatory flags) is fetched from the partition.

3. For each required entity or data source listed under Add required files for [scenario name] (for example, Customer, Product, or Data Source: TxStandardData), click the plus icon to open the file options.

4. Choose one of the following options:

   • Upload new file: Upload a new file (or multiple files at once) directly in the process.

   • Select from uploads: Select a file that you previously uploaded under your account.

5. To find a previously uploaded file, use the search field, then select the required file.

6. To confirm you selected the correct file, open the file preview.

7. Click Continue to proceed to the next step.

Tip: If you want to use one file across multiple validation scenarios, you only need to upload it once. After that, you can attach it to other scenarios using Select from uploads.

Step 3: Map File Fields to Pricefx Structures

Use this step to map the columns in each file to the corresponding Pricefx structures. The header shows the Data Source File name, the Entity Type, the Used for Validation Scenario value, and the file position (for example, File 1 of 3).

On the Data mapping step, set the Parsing Options for the file:

Then complete the mapping:

1. Review the Preview of Uploaded Sample File (Header + 3 rows) to confirm the columns parse correctly. The preview shows the total row count, for example 11 rows.

2. In the Required Mappings section, confirm each entry under Import File Columns maps to the correct entry under Pricefx Columns. For example, map ProductID [sku] to Product ID and Label [label] to Product Name.

3. In the Optional Mappings section, map any remaining fields. To use AI-assisted mapping, click Map fields with AI.

4. For any field that requires a type change, use the Convert action and set the target type (String, Date, Number, or Boolean).

5. Resolve any entry marked Not found in options by selecting a valid import file column or removing the row.

6. Repeat the mapping for each file (for example, files 2 and 3 of 3).

7. Click Continue to proceed to the next step.

In the Basic file check (any file) scenario, you can select which validation to apply to each field: mandatory, uniqueness, or notNull.

Step 4: Review and Download Validation Results

When you start the validation, it runs in the background and may take some time. You can leave the page and come back; once the validation finishes, the Report Overview opens with the results for all scenarios.

Overall Result

The Report Overview opens with the overall score shown as a ring, with a badge giving the number of issues found, and a label stating the outcome:

Data Quality Categories

Beside the overall result, one card per quality category shows that category’s score out of 100. Only the categories that the selected scenarios actually evaluated are shown, so a run may display four cards rather than all six. Hover over a card to see the category’s definition and the pass or fail band applied to it.

The overall score combines the category scores, and each category carries its own weight. A low score in a heavily weighted category therefore costs more than the same score in a light one.

A Pricefx admin configures both the weights and the per-category bands. Neither needs a product release.

Finding Severity

Every check has a severity. The severity shows how much a finding matters, not how many records it affects.

• Critical – you must fix these findings before you continue.

• Major – fix these findings if possible. They do not block you.

• Minor – these findings are for information only. The category score does not include them.

A Critical check group shows an error after a single violation. Its score can still be above the category pass threshold.

For example, one duplicate ID makes Data Uniqueness red. The overall result reads Critical Issues Found, even if the score is high.

This behavior is intended. You must correct a Critical condition, even if it occurs once.

Five scenarios include Critical checks. Each covers a condition that makes the data unusable for analysis:

• Required fields filled in – the required identifiers must have values.

• No duplicate IDs – each primary identifier must be unique.

• Valid customer & product links – each transaction must refer to an existing customer and product.

• Enough data to analyze – each entity must have a minimum number of rows.

• Comprehensive data quality – includes the checks above.

Reviewing the Findings

1. Review the overall result and the category scores at the top of the Report Overview.

2. Under Validation scenarios results, expand a scenario to see its check groups. Each scenario is shown with its version, and each group with its own status icon, its title, and a one-line description of what it requires.

3. The scenarios and groups keep the structure you chose in the Validations setup step. Any finding therefore traces straight back to the scenario you added.

4. Open Preview Issue List on a group to see the individual findings. The table lists Record, Entity, Entity Type, File, Field, and Invalid value. Each finding therefore names where to fix it. Entity names are spelled out in full, for example Customer rather than C.

5. For a group that could not be evaluated, open Error Details. It names the table and column, and gives the reason: the column was not mapped, the check failed, or an execution error occurred.

6. Click Download full report to download the complete results, including every finding rather than the preview subset. Start new validation begins a fresh run.

Extended Field Detection Results

If you selected the Extended Field Detection scenario, its result is presented as its own table rather than as a pass or fail count. The table names the Quantity column it compared against, the File and Entity, and one row per numeric field:

The tooltip shows a first-pass and a second-pass score. The second pass runs only for fields the first pass did not classify as extended, so its score is empty for the rest.

All rows are informational. A Per-unit classification does not stop you from continuing, and Extended Field Detection results are included in the downloadable full report.

What to Do Next

Under What can be done to improve the result? the Report Overview offers three routes:

• Correct Data File Issues – fix the issue in your master data file and upload it again with Reupload Dataset.

• Fix Mapping Errors – return to the mapping step with Change Data Mapping.

• Proceed Anyway – continue and accept the reported quality issues in the final result.

A Pricefx admin can configure the validation thresholds without a new product version release. Confirm the configured thresholds with your admin if the overall results do not match your expectations.

Expected Result

You have run data validation against your files. You can review the validation results, identify issues by file and entity, and download a full report.