Decision table import fails due to CSV header mismatch in supplier onboarding

BPM ServiceNow
, , , , , , , ,
1

I’m trying to import decision tables from CSV files for our supplier approval workflow, but the import keeps failing with header validation errors. Our procurement team exports supplier criteria from Excel, and we need to bulk-import these as decision tables.

The error message shows:


CSV Import Failed: Header mismatch
Expected: Condition_1, Condition_2, Action
Found: Supplier_Risk_Score, Annual_Revenue, Approval_Level

We have about 150 supplier approval rules across different categories (manufacturing, services, consulting), and manually recreating these decision tables would take weeks. The CSV schema works fine in our legacy system, but ServiceNow Decision Management seems to expect specific column names. Is there a way to map our existing CSV headers to the decision table structure without reformatting all our files?

2

Let me walk you through a complete solution for importing your supplier approval decision tables with mismatched CSV headers.

CSV Header Schema Handling: ServiceNow Decision Management requires CSV headers to match the decision table column definitions exactly. For your supplier onboarding use case, you have three options:

  1. Header Mapping Approach (Recommended for one-time imports): Create a simple transform script that preprocesses your CSV:

// Map legacy headers to decision table columns
headerMap = {
  'Supplier_Risk_Score': 'Risk_Level',
  'Annual_Revenue': 'Revenue_Threshold',
  'Approval_Level': 'Approver_Role'
};
  1. Decision Table Import Configuration: Before importing, ensure your decision table structure matches your business logic:
  • Navigate to Decision Tables > Your Supplier Approval Table
  • Verify column definitions match the number of conditions and actions you need
  • If you have 8 criteria in your CSV but only 5 columns in the decision table, either add the missing columns or decide which criteria to exclude
  1. Transform Map Solution (Best for recurring imports): For your 150+ supplier rules across categories, set up a reusable transform map:
  • Go to System Import Sets > Create Transform Map
  • Name it “Supplier Decision Table Import”
  • Map each CSV column to the corresponding decision table field
  • Set unmapped columns to “Ignore”
  • Add field mapping scripts for any data transformations needed

Supplier Approval Workflow Integration: Once your decision tables are imported, they need to integrate properly with your workflow:

Step-by-step Import Process:

  1. Export one sample CSV from your legacy system
  2. In ServiceNow, create or verify the decision table structure matches your requirements (conditions for risk score, revenue, category, etc.)
  3. Use the Decision Table import wizard: Decision > Decision Tables > Import
  4. Upload your CSV and proceed to the mapping screen
  5. Map each source column to target decision table columns:
    • Supplier_Risk_Score → Condition: Risk Level
    • Annual_Revenue → Condition: Revenue Amount
    • Approval_Level → Action: Approver Assignment
  6. For extra unmapped columns, select “Do Not Import” in the dropdown
  7. Run a test import with 10-20 rows first to validate the mapping

Handling Multiple Categories: For your manufacturing, services, and consulting categories, you have two approaches:

  • Single decision table with a Category condition column (simpler maintenance)
  • Separate decision tables per category (better performance, clearer organization)

I recommend separate tables for 150+ rules - it’s easier to manage and update category-specific rules without affecting others.

Automation for Bulk Import: Since you have multiple CSV files, create a scripted import process:

  1. Set up a staging table to receive CSV data
  2. Create a Business Rule that triggers after CSV load
  3. The rule validates headers, applies transformations, and loads into decision tables
  4. Add error logging for any rows that fail validation

This approach handles your immediate header mismatch issue while providing a sustainable solution for future imports. The transform map ensures your legacy CSV format works seamlessly with ServiceNow’s decision table structure without requiring manual reformatting of 150 files.

3

I agree with Raj about the mapping feature, but there’s a catch - the mapping interface only appears if your CSV has at least one column name that partially matches a decision table column. If there’s no match at all, the import fails immediately with that header mismatch error. Try renaming at least one column in your CSV to match the decision table structure, then the mapper should activate. For your supplier approval workflow, you might need to create a preprocessing script that standardizes the headers before import.

4

The decision table import in ServiceNow is pretty strict about CSV structure. By default, it expects headers that match your decision table’s condition and action column names exactly. However, there’s a mapping feature in the import wizard that lets you map source CSV columns to target decision table columns. When you start the import, there should be a mapping step before the actual import where you can align your CSV headers with the decision table structure.