Beyond the Import Wizard: Section 4 - Validation and Verification After Import

Published Date: November 2, 2026
Audience: Everyone
Products and Versions Covered: 

• Jama Connect® All Versions
  • Cloud/CVC
  • Self-hosted
    • Replicated - KOTS
    • Kubernetes - Native
      • Database
      • OS

IMPORTANT: Access to the REST API and the Jama Connect Cloud MCP Server is restricted to users with a Named Creator Jama Connect license, which includes access to v1, Labs, and SCIM endpoints. Users without a Named Creator license—including those with a Creator Float license—do not have access.

Summary

For users validating or troubleshooting import results.

This section breaks down the most common failure modes with links to existing articles, but it also identifies step-by-step recovery strategies to support your Validation and Verification of the imported data.

When an import can't start, Jama Connect usually tells you why. Missing required fields, unsupported file types, and similar issues produce clear error messages.

The harder problems occur when the import succeeds, but the results aren't what you expected. That's where validation and verification become essential.

Resolution

4.1 Quick Diagnosis

Before diving into the rest of this section, check whether your issue matches one of these common import problems. If it does, the linked article may answer your question immediately.

• Why doesn’t the import wizard find my file? Unsupported file type (only .doc, .docx, .xls, .xlsx, and .csv are supported)
• Why do I see a blank screen in the import wizard? Wrong worksheet selected or incompatible unique field name
• Why isn’t the import wizard showing my excel headers? Incorrect header row
• Why did I get an import error “importFieldMapping” is null? Check the unique field name
• Why don’t I see Category or Tag field options in the mapping screen? Category and Tag fields cannot be imported with Excel

If your issue isn't listed above, return to Section 2: Foundations for spreadsheet preparation tips or continue reading for validation and troubleshooting guidance.

4.2 Unintended Results

The most difficult import problems aren't failures to import, but failures to import as intended. Most questions with Excel imports really come down to: "The import succeeded... but not the way I expected." This is why Validation and Verification of your data is the critical next step. Let’s define the two terms in the context of Excel imports.

Validation: Did I import the right data?

Confirm that the correct items, hierarchy, fields, and relationships were imported into the correct locations. Questions like:

• Did everything import?
• Did I import the correct worksheet?
• Did the right item types get created?
• Did I accidentally duplicate data?
• Did I import into the correct project/location?

These are all asking: Did I build the right thing?

Verification: Did the data import correctly?

Confirm that field values, formatting, hierarchy, workflows, and other behaviors match what you intended. Questions like:

• Did hierarchy come out correctly?
• Did rich text preserve formatting?
• Did picklists map correctly?
• Did only the intended fields update?
• Did my Round Trip overwrite what I expected?

These are all asking: Did I build the thing right?

4.3 Verify with a Small Test Import

One of the most common mistakes is importing everything on the first attempt. Large imports make validation, verification, and recovery significantly more difficult if something doesn't behave as expected.

Instead, import five to ten representative items into a sandbox or test project before importing the full dataset.

Confirm the following before proceeding:

• Hierarchy imported as expected.
• Field mappings produced the correct values.
• Rich text formatting was preserved.
• Picklist values imported correctly.
• Default values were applied where expected.
• Items were created in the correct location and with the correct Item Type.

Only after you're satisfied with the results should you proceed with the full import.

Consultant Tip: Dry Run Imports

A five-row test import catches almost every structural problem you'll encounter while being much faster to troubleshoot than hundreds of imported items.

4.4 The Most Common Validation & Verification Questions

If your import completed successfully but the results weren't what you expected, start with this list. Most post-import questions are answered elsewhere in this guide or in the linked knowledge base articles.

4.5 Things That Trip Up Even Experienced Users

This last section addresses the corner and edge cases that represent about 10% of the questions customers ask about Excel imports, but they're responsible for 90% of the headaches.

In what cases will a round trip import overwrite locked items?

It depends on why the item is locked. System locks prevent Excel from updating the item, while user locks only prevent editing through the Jama Connect user interface. Verify the type of lock before assuming a Round Trip update will succeed.

• If the item is user-locked by the user performing the import, the log reports the items as updated. 
• If the item is user-locked by another user, the items are still updated, but the log reports the number of locked items.  

See: System vs. User Locks

What happens when Jama Connect configuration changes after you built your spreadsheet?

Excel templates don't exist in isolation; they reflect your Jama Connect project configuration at the time they were created. If fields, picklists, workflows, or Item Types change later, a spreadsheet that imported successfully yesterday may produce different results today.

See:

• Best Practice for Changing a Field Type
• Delete or Update an Item Type's Field Without Losing Data
• Batch Edit of Item Titles

Can I import test execution results?

It depends on the field type. Default test execution result fields in Test Runs and Test Cases don't behave like standard Item Type fields and can only be updated through the REST API (not Excel import). If you need to import test results with Excel, create a custom field on the item type instead.

This behavior is closely related to read-only fields.

Can an Excel import overwrite read-only fields?

No. Excel imports respect Jama Connect's read-only restrictions. While some read-only fields can be updated through the REST API under specific conditions, Excel imports cannot.

This behavior is closely related to locked items and system-managed fields.

Can an Excel import overwrite or create system fields (Global ID, Project ID, etc.)?

No. These are Jama Connect-managed system identifiers used to maintain relationships and internal references. Editing them in Excel will not change the values in Jama Connect.

Can I reorganize hierarchy during a Round Trip?

No. Round Trip imports aren't intended to reorganize your existing Explorer tree. You can add new rows beneath existing containers and create new folders using highlighting or indentation, but they won't restructure the existing project hierarchy.

See Section 3.5: Building Hierarchy During New Imports.

Can I use a Round Trip to delete items?

No. Round Trip imports synchronize additions and updates; they don't delete existing items. If a row is removed from your spreadsheet, Jama Connect doesn't interpret that as a request to delete the corresponding item.

Delete items directly in Jama Connect (or through another supported mechanism) if removal is required.

Additional Resources

• Beyond the Import Wizard: A Field Guide to Excel Imports in Jama Connect
• Section 1 - Summary and Guide Overview
• Section 2 - Foundations or Before You Click "Import"
• Previous: Section 3 - Choosing (and preparing for) the Right Import Options
• Next: Section 5 - Advanced Strategies and Nuances
• Section 6 - Lessons from the Field

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.