While running an integration platform import you get a “TF237165: The Team Foundation Server could not update the work item because of a validation error on the server. This may happen because the work item has been modified or destroyed, or that you do not have permission to update that work item.”
Figure: TF237165: The Team Foundation Server could not update the work item
Unfortunately it does not tell you what it was trying to save.
Applies To
- TFS Integration Tools 2.2, March 2012
Finding
This was a Configuration error that was not really presented effectively. I found it by reducing the dataset to a few known failing items and commenting out all of the field before re-running the migration. I then added each field in one at a time until the error occurred.
I had a missing field migration to map a data value into reason:
And I had an incorrect mapping in the ValueMap:
Figure: Value mapping for Reason field
You can see on lines 2 and 3 of the code above I had incorrectly specified the mapping as having a left value for the field that I was mapping as a @@MISSINGFIELD@@.
Workaround
The mentioned field either needs removed from the mapping or added to the work item. In this case I will be removing it from the mapping as I don’t need that field on the Task WIT.
Did this solve your problem?
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
TFS Integration Tools – Issue: Error occurred during the code review of change group
Explains causes and solutions for the "Error occurred during the code review of change group" in TFS Integration Tools, including common …
TFS Integration Tools - Issue: TF205022: The following path contains more than the allowed 259 characters
Explains how to resolve the TFS error caused by file paths exceeding 259 characters during migration, with steps to shorten paths and adjust …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …