Asme File Upload Failed Error Updating Manuscript Error Entity Validation Error
This browser is no longer supported.
Upgrade to Microsoft Border to take advantage of the latest features, security updates, and technical support.
Resolve validation errors for process import
Azure DevOps Services
During process import, the process is validated to ensure the organisation works as expected for the custom process. Y'all'll receive a list of error messages if the process fails validation.
If you've received a validation mistake when y'all tried import procedure, you lot'll need to resolve the error before retrying the import. Each error has a link to learn more about the specific validation failure and guidance on how to right it. Apply the resolution fix(es) provided for the message(southward) that you received, zip up the updated files, and retry the import operation.
If you lot're merely starting your customization, review the validation rules provided.
Information messages - no action required
TF402555: Field [refName] is deleted.
The process that you're importing doesn't include the named field in the procedure being updated, therefore information technology is removed as function of the update operation.
Scenario case
- Add custom field to Problems.xml work item
<FIELD name="Foo" refname="MyCompany.CustomFields.Foo" blazon="String" reportable="dimension" /> - Import procedure
- Remove field from Bug.xml
- Import updated process
The arrangement displays an information message well-nigh the field to be deleted.
TF402555: Field MyCompany.CustomFields.Foo will be deleted
TF402591: Field with reference name [refName] cannot be renamed to '[name1]' from '[name2]' in existing processes [processName].
The procedure that y'all're importing contains a renamed field that uses the same refname in the current procedure(es).
Field names cannot be renamed.
TF402598: Work particular type [refName] is deleted.
The procedure that you're updating doesn't include the named WIT that exists in the current process. Every bit part of updating the existing process, the system deletes the named WIT from the current process.
Scenario instance
- Create new work item blazon chosen "LSI"
<WORKITEMTYPE name="LSI" refname="My.LSI"> - Import procedure
- Remove the LSI work item type from the process
- Import updated process
The arrangement displays an information message nigh the deletion.
TF402598: Work detail type My.LSI will be deleted
TF402601: Work item type [witName] is renamed to [name1] from [name2].
The process contains a renamed WIT. The WIT is renamed in the existing procedure.
The procedure that you're updating contains a WIT that's been renamed from the name in the current procedure.
As part of updating the existing process, the system renames the WIT in the current procedure. All piece of work items in existing projects that reference the procedure are as well renamed.
Scenario example
- Create new work item type called "LSI"
<WORKITEMTYPE proper name="LSI" refname="My.LSI"> - Import process
- Rename the LSI work item type to Live Site Incident
<WORKITEMTYPE proper noun="Live Site Incident" refname="My.LSI"> - Import updated procedure
The system displays an data message about the WIT to be renamed.
TF402601: Work item type My.LSI will be renamed to 'Live Site Incident' from 'LSI'
Miscellaneous file errors
TF402586: Error parsing file: [Mistake message]
Malformed XML syntax tin can crusade parsing file errors. Missing closing tags, missing quotes, missing open up or shut brackets (< or >) can cause a parsing file fault.
From the fault bulletin, determine and correct the source of the malformed XML.
TF402594: File violates the schema with the following error: [Error bulletin]
Each XML file in the procedure zilch file must conform to the given schema. Schema violation errors are caused by custom XML tags or attributes within the XML file. Read the fault message to determine the source of schema violation and fix appropriately.
The schema definition for work item tracking defines all child elements inside the Course element as camel instance and all other elements as all capitalized. If you encounter errors when validating your type definition files, cheque the case structure of your elements. Besides, the instance structure of opening and closing tags must lucifer according to the rules for XML syntax.
Error examples
Custom XML tag:
<WORKITEMTYPE proper noun="Problems" refname="My.Problems"> <FOO>Hello World</FOO> ... Actress attribute added to XML chemical element:
<WORKITEMTYPE proper name="Bug" refname="My.Issues" foo="hello world"> VS412450: Xml schema validation error in [fileName]. [Mistake message]
Correct the schema fault in the named file.
Process template plug-in errors
The ProcessTemplate.xml is the root file that defines the unabridged process and all XML definition files that will be imported to add or update a process. This file contains all of the plug-ins and task groups that are referenced when creating a project. Each job grouping references a subordinate XML file (often in a subfolder) where the specific tasks are defined. In general, you specify one task group for each plug-in.
The ProcessTemplate.xml definition file must conform to the syntax and rules described in ProcessTemplate XML element reference.
VS412457: Specified file '[fileName]' could not be found in the process package.
Right the procedure zip parcel to include the named file.
VS402452: The process template did not specify a version, or specified an invalid version.
Edit the ProcessTemplate.xml file to specify a version.
Mistake example
ProcessTemplate.xml file specifies the aforementioned version GUID every bit for the Agile process, which is a locked process.
<ProcessTemplate> <metadata> <name>Fabrikam Agile</name> <description>Use this template to support Fabrikam Agile planning methods.</clarification> <version type="ADCC42AB-9882-485E-A3ED-7678F01F66BC" major="7" pocket-size="36" /> Resolution example
A unlike GUID is specified.
<ProcessTemplate> <metadata> <name>Fabrikam Agile</proper noun> <description>Use this template to support Fabrikam Active planning methods.</description> <version type="7710F7A4-1F19-4054-9FBC-D94A5935221E" major="vii" modest="1" /> VS412453: Procedure template zip file doesn't comprise required plugin [pluginName].
All files listed inside the ProcessTemplate.xml file and its supported plug-in files must exist present within the process zip file.
Use a search tool to find all instances of filename=value inside the ready of procedure files and folders. And then, either update the plug-in to remove the missing named file, or add together the named file to the process folder where it belongs.
<taskList filename="WorkItem Tracking\WorkItems.xml" /> Error instance
The WorkItemTracking plug-in specifies fileName="WorkItem Tracking\TypeDefinitions\Epic.xml, however it hasn't been added to the WorkItem Tracking\TypeDefinitions folder.
<WORKITEMTYPE fileName="WorkItem Tracking\TypeDefinitions\Ballsy.xml" /> Resolution example
Add the Epic.xml file to the WorkItem Tracking\TypeDefinitions binder.
VS412454: Plug-in [pluginName] contains several taskList {1}, {ii}. Only one taskList per plugin is allowed.
Right the ProcessTemplate.xml file for the named plug-in to reduce the number of tasklist elements divers.
Error case
The WorkItemTracking plug-in contains two tasklist statements.
<grouping id="WorkItemTracking" description="Workitem definitions uploading." completionMessage="Work item tracking tasks completed."> <dependencies> <dependency groupId="Classification" /> <dependency groupId="Groups" /> </dependencies> <taskList filename="WorkItem Tracking\WorkItems.xml" /> <taskList filename="WorkItem Tracking\FabrikamWorkItems.xml" /> </group> Resolution instance
<group id="WorkItemTracking" clarification="Workitem definitions uploading." completionMessage="Work item tracking tasks completed."> <dependencies> <dependency groupId="Classification" /> <dependency groupId="Groups" /> </dependencies> <taskList filename="WorkItem Tracking\FabrikamWorkItems.xml" /> </group> TF402575: You can merely include 1 Category definition file in your process.
Error example
The WorkItems.xml file contains two CATEGORIES statements.
<task id="Categories" name="Categories definitions" plugin="Microsoft.ProjectCreationWizard.WorkItemTracking" completionMessage="Work item type categories created"> <dependencies> <dependency taskId="WITs" /> </dependencies> <taskXml> <CATEGORIES fileName="WorkItem Tracking\Categories.xml" /> <CATEGORIES fileName="WorkItem Tracking\Custom_Categories.xml" /> </taskXml> </task> Resolution case
The WorkItems.xml file has been updated to contain merely one CATEGORIES statement.
<task id="Categories" proper noun="Categories definitions" plugin="Microsoft.ProjectCreationWizard.WorkItemTracking" completionMessage="Work detail type categories created"> <dependencies> <dependency taskId="WITs" /> </dependencies> <taskXml> <CATEGORIES fileName="WorkItem Tracking\Custom_Categories.xml" /> </taskXml> </chore> TF402576: You can only include one ProcessConfiguration definition file in your process.
Error example
The WorkItems.xml file contains indistinguishable ProjectConfiguration statements.
<taskXml> <PROCESSCONFIGURATION> <ProjectConfiguration fileName="WorkItem Tracking\Procedure\ProcessConfiguration.xml"/> </PROCESSCONFIGURATION> </taskXml> <taskXml> <PROCESSCONFIGURATION> <ProjectConfiguration fileName="WorkItem Tracking\Procedure\ProcessConfiguration.xml"/> </PROCESSCONFIGURATION> </taskXml> Resolution example
The WorkItems.xml file has been updated to contain only i ProjectConfiguration statement.
<taskXml> <PROCESSCONFIGURATION> <ProjectConfiguration fileName="WorkItem Tracking\Process\ProcessConfiguration.xml"/> </PROCESSCONFIGURATION> </taskXml> TF402587: Required ProcessConfiguration file missing.
The WorkItems.xml file specifies the ProcessConfiguration file to upload. Either the file isn't specified, contains an out-of-date specification, the specified file is missing from the template, or the folder/file name isn't correct.
Error case
The configuration specified is out-of-engagement and specifies ii files that aren't contained in the Procedure binder.
<taskXml> <PROCESSCONFIGURATION> <CommonConfiguration fileName="WorkItem Tracking\Process\CommonConfiguration.xml"/> <AgileConfiguration fileName="WorkItem Tracking\Process\AgileConfiguration.xml"/> </PROCESSCONFIGURATION> </taskXml> Resolution example
The WorkItems.xml file has been updated to incorporate the right configuration ProjectConfiguration statement.
<taskXml> <PROCESSCONFIGURATION> <ProjectConfiguration fileName="WorkItem Tracking\Process\ProcessConfiguration.xml"/> </PROCESSCONFIGURATION> </taskXml> TF402577: Field [refName] specifies friendly proper name [friendlyName] which is already in use by fields [refName] in processes [processNames].
Friendly names must be unique beyond all field definitions for all WIT definitions specified for all processes imported to Azure DevOps Services.
The named processes contain WITs that define a field that uses the friendly name.
Alter the WIT definition in your process zip file that contains [refName] and specify a different friendly name or brand it match an existing field in utilise.
Error example
The UserStory WIT definition contains FIELD element for Fabrikam.Product.Family with friendly proper noun Product.
<FIELD name="Production" refname="Fabrikam.Production.Family" type="String" reportable="dimension"> <HELPTEXT>Enter the name of the product family for this story or characteristic.</HELPTEXT> </FIELD> Yet, in an existing process, Fabrikam.Production.Versions uses the friendly name Production.
<FIELD proper name="Product" refname="Fabrikam.Product.Versions" type="String" reportable="dimension"> <HELPTEXT>Enter the proper name of the production version for this story or feature.</HELPTEXT> </FIELD> Resolution example
Update the UserStory WIT definition to match the existing field.
<FIELD name="Product" refname="Fabrikam.Product.Versions" type="String" reportable="dimension"> <HELPTEXT>Enter the name of the product version for this story or feature.</HELPTEXT> </FIELD> TF402585: Required WorkItemTracking plug-in reference missing from the process template.
You must specify the Microsoft.ProjectCreationWizard.WorkItemTracking plug-in in the metadata section of the ProcessTemplate.xml file:
Mistake example
The Microsoft.ProjectCreationWizard.WorkItemTracking plug-in is missing from the plugins section of the ProcessTemplate.xml file.
<plugins> <plugin name="Microsoft.ProjectCreationWizard.Classification" wizardPage="false" /> <plugin name="Microsoft.ProjectCreationWizard.Reporting" wizardPage="false" /> <plugin proper noun="Microsoft.ProjectCreationWizard.Portal" wizardPage="truthful" /> <plugin proper noun="Microsoft.ProjectCreationWizard.Groups" wizardPage="simulated" /> <plugin name="Microsoft.ProjectCreationWizard.VersionControl" wizardPage="true" /> <plugin name="Microsoft.ProjectCreationWizard.TestManagement" wizardPage="false" /> <plugin name="Microsoft.ProjectCreationWizard.Build" wizardPage="false" /> <plugin name="Microsoft.ProjectCreationWizard.Lab" wizardPage="false" /> </plugins> Resolution example
<plugins> <plugin proper noun="Microsoft.ProjectCreationWizard.Nomenclature" wizardPage="false" /> <plugin name="Microsoft.ProjectCreationWizard.Reporting" wizardPage="faux" /> <plugin proper name="Microsoft.ProjectCreationWizard.Portal" wizardPage="true" /> <plugin proper name="Microsoft.ProjectCreationWizard.Groups" wizardPage="false" /> <plugin proper name="Microsoft.ProjectCreationWizard.WorkItemTracking" wizardPage="false" /> <plugin name="Microsoft.ProjectCreationWizard.VersionControl" wizardPage="truthful" /> <plugin name="Microsoft.ProjectCreationWizard.TestManagement" wizardPage="false" /> <plugin name="Microsoft.ProjectCreationWizard.Build" wizardPage="simulated" /> <plugin proper noun="Microsoft.ProjectCreationWizard.Lab" wizardPage="false" /> </plugins> Categories
The Categories.xml definition file must conform to the syntax and rules described in Categories XML element reference.
TF402546: Category [categoryName] is missing from the categories file.
All categories that are referenced in the ProcessConfiguration.xml file must be defined in the Categories.xml file. In addition, the system requires that the Categories.xml file comprise definitions for the post-obit categories:
- Bug Category
- Code Review Request Category
- Code Review Response Category
- Feedback Asking Category
- Feedback Response Category
- Hidden Types Category
- Requirement Category
- Shared Step Category
- Shared Parameter Category
- Task Category
- Test Case Category
- Test Plan Category
- Test Suite Category
Update your Categories.xml file to define the missing [proper name] category.
Fault example
ProcessConfiguration references the Epic Category, even so it is missing from the Categories.xml definition file.
Resolution instance
Epic Category is added to the Categories file.
<CATEGORY proper noun="Ballsy Category" refname="Microsoft.EpicCategory"> <DEFAULTWORKITEMTYPE name="Epic" /> </CATEGORY> TF402553: Element [name] references category [categoryName] which isn't divers in the categories file.
Update your Categories.xml file to define the missing [categoryName] category.
TF402560: You've defined [n] categories. Only [nn] are immune.
Review your Categories.xml file for all CATEGORY element statements and determine which ones you tin delete and so as non exceed the allowed limit. So, review your ProcessConfiguration.xml file to supervene upon values that reference deleted categories.
TF402596: Category [categoryName] doesn't define work Particular type [witName].
Categories must reference WITs that are defined in the /WorkItem Tracking/TypeDefinitions folder and listed as a task for upload in the WorkItems.xml plug-in file.
Review your Categories.xml file for references to a WIT that isn't included in the /WorkItem Tracking/TypeDefinitions binder.
Fault case
The name of the WIT referenced for Microsoft.EpicCategory is misspelled.
<CATEGORY name="Epic Category" refname="Microsoft.EpicCategory"> <DEFAULTWORKITEMTYPE name="EpicABC" /> </CATEGORY> Resolution example
<CATEGORY proper noun="Epic Category" refname="Microsoft.EpicCategory"> <DEFAULTWORKITEMTYPE proper noun="Epic" /> </CATEGORY> TF402597: Custom category [categoryName] isn't supported because ProcessConfiguration doesn't reference it.
You can but specify custom categories that you use to configure an Active tool feature in the ProcessConfiguration.
Review your ProcessConfiguration.xml file and determine if you've missed adding support for a category. Otherwise, remove [categoryName] from the Categories.xml file.
Fault example
ProcessConfiguration doesn't reference Microsoft.EpicCategory, although it'southward defined in the Categories.xml definition file.
Resolution example
Add PortfolioBacklog to ProcessConfiguration to reference Microsoft.EpicCategory.
<PortfolioBacklog category="Microsoft.EpicCategory" pluralName="Epics" singularName="Epic" workItemCountLimit="1000"> <States> <Land value="New" blazon="Proposed" /> <State value="Agile" type="InProgress" /> <State value="Resolved" type="InProgress" /> <Country value="Closed" type="Complete" /> </States> <Columns> <Column refname="Organization.WorkItemType" width="100" /> <Cavalcade refname="System.Title" width="400" /> <Column refname="System.State" width="100" /> <Column refname="Microsoft.VSTS.Scheduling.Effort" width="50" /> <Cavalcade refname="Microsoft.VSTS.Common.BusinessValue" width="fifty" /> <Column refname="Microsoft.VSTS.CMMI.RequirementType" width="100" /> <Cavalcade refname="Arrangement.Tags" width="200" /> </Columns> <AddPanel> <Fields> <Field refname="Organisation.Title" /> </Fields> </AddPanel> </PortfolioBacklog> Reference articles:
- ProcessConfiguration XML element reference
- Categories XML element reference
Classification plug-in errors
The Nomenclature.xml definition file must adapt to the syntax and rules described in Nomenclature plug-in.
TF402511: The Nomenclature plug-in contains duplicate property proper name: [propertyName].
Fault example
Classification.xml file contains a 2d holding name="MSPROJ" statement under the properties container element.
<backdrop> <holding name="MSPROJ" value="Classification\FileMapping.xml" isFile="true" /> <holding proper noun="MSPROJ" value="Classification\Fabrikam_FileMapping.xml" isFile="true" /> <holding name="Process Template" value="Fabrikam Agile"/> </backdrop> Resolution example
Remove the duplicate statement.
<properties> <belongings proper name="MSPROJ" value="Nomenclature\Fabrikam_FileMapping.xml" isFile="true" /> <holding name="Procedure Template" value="Fabrikam Agile"/> </properties> TF402512: File [fileName] does non exist.
The file specified in the Classification.xml file isn't present in the specified path or the path is misspelled.
Error case
The Classification folder path is misspelled.
<backdrop> <property proper name="MSPROJ" value="Classification\Fabrikam_FileMapping.xml" isFile="true" /> <property name="Process Template" value="Agile"/> </properties> Resolution case
<properties> <property proper noun="MSPROJ" value="Classification\Fabrikam_FileMapping.xml" isFile="truthful" /> <property name="Process Template" value="Fabrikam Agile"/> </properties> TF402513: Name [pathName] in the Nomenclature plug-in doesn't conform to TreePath naming restrictions.
Review the Node elements y'all've specified and change the names to suit to supporting naming conventions. Reference: Add and modify expanse and iteration paths.
Mistake example
The Path names include the # character which is not immune.
<Node StructureType="ProjectLifecycle" Name="Iteration" xmlns=""> <Children> <Node StructureType="ProjectLifecycle" Name="Sprint #1" /> <Node StructureType="ProjectLifecycle" Name="Sprint #2" /> <Node StructureType="ProjectLifecycle" Name="Sprint #3" /> </Children> </Node> Resolution case
The Path names have been corrected.
<Node StructureType="ProjectLifecycle" Name="Iteration" xmlns=""> <Children> <Node StructureType="ProjectLifecycle" Proper name="Sprint 1" /> <Node StructureType="ProjectLifecycle" Proper noun="Sprint ii" /> <Node StructureType="ProjectLifecycle" Name="Sprint 3" /> </Children> </Node> TF402514: Node StructureType [structureTypeName] in the Nomenclature plug-in is not supported.
The StructureType attribute only allows the post-obit values: ProjectModelHierarchy and ProjectLifecycle.
Review the Node elements that you've specified and remove any unsupported attributes.
Mistake case
ProjectLifecycle has been misspelled.
<Node StructureType="ProjectLifecylce" Name="Iteration" xmlns=""> <Children> <Node StructureType="ProjectLifecycle" Proper name="Sprint one" /> <Node StructureType="ProjectLifecycle" Name="Dart two" /> <Node StructureType="ProjectLifecycle" Name="Sprint iii" /> </Children> </Node> Resolution example
Misspelled name has been corrected.
<Node StructureType="ProjectLifecycle" Name="Iteration" xmlns=""> <Children> <Node StructureType="ProjectLifecycle" Name="Dart i" /> <Node StructureType="ProjectLifecycle" Name="Sprint 2" /> <Node StructureType="ProjectLifecycle" Name="Dart 3" /> </Children> </Node> TF402515: A holding attribute in the Nomenclature plug-in is either missing or non supported.
The property element only allows the following attributes: proper noun , value , and isFile.
Review the belongings elements you lot've specified and remove whatsoever unsupported attributes.
Error example
The value attribute is misspelled.
<backdrop> <property name="MSPROJ" vaule="Classification\Fabrikam_FileMapping.xml" isFile="true" /> <property name="Process Template" value="Agile" /> </properties> Resolution example
Misspelled attribute has been corrected.
<properties> <property name="MSPROJ" value="Nomenclature\Fabrikam_FileMapping.xml" isFile="true" /> <property name="Process Template" value="Fabrikam Agile"/> </properties> TF402516: The Classification plug-in contains more than 2 root level Nodes, which is not supported.
Review the Node elements y'all've specified and remove extra root level nodes.
Error instance
Classification.xml file contains a 2nd Node StructureType="ProjectLifecycle" statement under the Nodes container element.
<Nodes> <Node StructureType="ProjectLifecycle" Name="Iteration" xmlns=""> <Children> <Node StructureType="ProjectLifecycle" Name="Sprint 1" /> <Node StructureType="ProjectLifecycle" Proper noun="Sprint ii" /> <Node StructureType="ProjectLifecycle" Name="Sprint 3" /> </Children> </Node> <Node StructureType="ProjectLifecycle" Name="Iteration" xmlns=""> <Node StructureType="ProjectModelHierarchy" Name="Area" xmlns="" /> </Nodes> Resolution example
Remove the second statement.
<Nodes> <Node StructureType="ProjectLifecycle" Name="Iteration" xmlns=""> <Children> <Node StructureType="ProjectLifecycle" Name="Sprint 1" /> <Node StructureType="ProjectLifecycle" Proper name="Sprint 2" /> <Node StructureType="ProjectLifecycle" Name="Dart 3" /> </Children> </Node> <Node StructureType="ProjectModelHierarchy" Name="Surface area" xmlns="" /> </Nodes> TF402523: Area or Iteration path '[pathName]' in the GroupsandPermissions plug-is missing from the Classification plug-in.
Add the missing [pathName] to the Classification.xml file or remove it from the GroupsandPermissions.xml file.
Fault example
Classification.xml file specifies sprints, non iterations.
GroupsandPermissions.xml teamSettings specifies Iterations.
<teamSettings areaPath="Area"> <iterationPaths backlogPath="Iteration"> <iterationPath path="Iteration 1" /> <iterationPath path="Iteration ii" /> <iterationPath path="Iteration 3" /> </iterationPaths> </teamSettings> However, the Nomenclature.xml specifies sprints.
<Node StructureType="ProjectLifecycle" Name="Iteration" xmlns=""> <Children> <Node StructureType="ProjectLifecycle" Name="Sprint 1" /> <Node StructureType="ProjectLifecycle" Name="Sprint 2" /> <Node StructureType="ProjectLifecycle" Proper name="Dart iii" /> </Children> </Node> Resolution instance
Update GroupsandPermissions.xml to use sprints.
<teamSettings areaPath="Area"> <iterationPaths backlogPath="Iteration"> <iterationPath path="Sprint 1" /> <iterationPath path="Sprint two" /> <iterationPath path="Dart iii" /> </iterationPaths> </teamSettings> Link types
Notation
Custom link types aren't supported in the electric current import process.
TF402561: You lot've defined [northward] custom link types. But [nn] are allowed.
Review your WorkItems.xml plug-in file for all LINKTYPE chemical element statements. Remove statements associated with custom link types so as not exceed the allowed limit. And so, remove the respective link type definition file from the LinkTypes folder.
Also, remove whatever references to the custom link types that you've added to a WIT definition within a LinksControlOptions section under the FORM section.
TF402583: Custom link type [proper noun] is invalid because custom link types aren't supported.
Review your WorkItems.xml plug-in file for all LINKTYPE element statements. Remove any statements that specify a custom link type. And and so, remove the corresponding link type definition file from the LinkTypes folder.
The following LINKTYPE element statements within the WorkItems.xml plug-in file are valid:
<LINKTYPES> <LINKTYPE fileName="WorkItem Tracking\LinkTypes\Affects.xml" /> <LINKTYPE fileName="WorkItem Tracking\LinkTypes\SharedStep.xml" /> <LINKTYPE fileName="WorkItem Tracking\LinkTypes\TestedBy.xml" /> <LINKTYPE fileName="WorkItem Tracking\LinkTypes\SharedParameterLink.xml" /> </LINKTYPES> Global lists
Note
Global lists aren't supported in the current import process feature.
TF402564: You lot've defined [n] global lists. Only [nn] are allowed.
One or more WITs divers in the custom process template contain a GLOBALLIST element. Search through your WIT definition files and supersede any GLOBALLIST elements with ALLOWEDVALUES or SUGGESTEDVALUES elements. For reference syntax, encounter Ascertain pick lists.
TF402565: You lot've defined [due north] items in global list [globalListName]. A maximum of [nn] is allowed.
The named GLOBALLIST element contains more items than allowed. Either reduce the number of list items contained in the GLOBALLIST element, or segment the global list into ii or more elements and so that neither list exceeds the maximum number of allowed items.
For reference syntax, come across Ascertain pick lists.
Process configuration
The ProcessConfiguration.xml definition file must conform to the syntax and rules described in ProcessConfiguration XML chemical element reference.
TF402543: Element [elementName] requires that y'all map exactly ane workflow state to metastate [metastateName].
Update the States department inside the named element in the ProcessConfiguration.xml file to provide the missing metastate mapping or remove extra mappings.
Fault example
ProcessConfiguration.xml RequirementBacklog element is missing a metastate mapping for type="Proposed".
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Backlog items" singularName="Backlog item"> <States> <Land value="Committed" type="InProgress" /> <State value="Done" blazon="Consummate" /> </States> . . . </RequirementBacklog > Resolution instance
Missing metastate mappings have been added.
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Backlog items" singularName="Backlog detail"> <States> <State value="New" blazon="Proposed" /> <Country value="Committed" type="InProgress" /> <State value="Done" type="Complete" /> </States> . . . </RequirementBacklog > TF402547: Chemical element [elementName] requires that for piece of work detail type [witName] you map at to the lowest degree one state to metastate [metastateName].
Review the WORKFLOW states divers for the named WIT and then update the States section within the named element in the ProcessConfiguration.xml file to provide the missing metastate mapping for the named WIT.
TF402548: Element [elementName] requires that you map at least one country to metastate [metastateName].
Update the States section within the named element in the ProcessConfiguration.xml file to provide the missing metastate mapping.
Error example
ProcessConfiguration.xml RequirementBacklog element is missing a metastate mapping for blazon="InProgress".
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Excess items" singularName="Backlog item"> <States> <State value="New" type="Proposed" /> <Country value="Washed" type="Complete" /> </States> . . . </RequirementBacklog > Resolution case
Missing metastate mappings have been added.
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Excess items" singularName="Backlog item"> <States> <State value="New" type="Proposed" /> <Country value="Committed" type="InProgress" /> <State value="Done" blazon="Consummate" /> </States> . . . </RequirementBacklog > TF402550: Element [elementName] includes more than one metastate mapping for workflow state [stateName].
Metastate value cannot be mapped to more one workflow state.
Error instance
ProcessConfiguration.xml RequirementBacklog element contains two metastate mappings for value="Agile".
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Stories" singularName="Story"> <States> <State value="Active" type="Proposed" /> <State value="Active" type="InProgress" /> <Country value="Resolved" type="InProgress" /> <Country value="Closed" type="Complete" /> </States> . . . </RequirementBacklog > Resolution example
Metastate mappings have been corrected.
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Stories" singularName="Story"> <States> <Country value="New" type="Proposed" /> <State value="Agile" type="InProgress" /> <State value="Resolved" blazon="InProgress" /> <State value="Closed" type="Complete" /> </States> . . . </RequirementBacklog > TF402551: Work item type [witName] doesn't define workflow state [stateName], which is required because ProcessConfiguration maps it to a metastate for element [elementName].
Either correct the ProcessConfiguration.xml file or the WORKFLOW section of the named WIT to add the missing STATE and TRANSITION elements.
Mistake case
ProcessConfiguration.xml RequirementBacklog element specifies value="Committed", nonetheless UserStory.xml doesn't define Committed as a State.
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Stories" singularName="Story"> <States> <State value="New" blazon="Proposed" /> <Land value="Committed" type="InProgress" /> <State value="Active" blazon="InProgress" /> <Country value="Resolved" type="InProgress" /> <State value="Closed" type="Consummate" /> </States> . . . </RequirementBacklog > Resolution example
Removed the State element for Committed.
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Stories" singularName="Story"> <States> <State value="New" type="Proposed" /> <State value="Active" blazon="InProgress" /> <Land value="Resolved" type="InProgress" /> <State value="Closed" type="Complete" /> </States> . . . </RequirementBacklog > TF402552: Chemical element [elementName] requires that for work item blazon [witName] you map exactly one state to metastate [metastateName] for the post-obit states: [stateNames].
Review the STATES section in the ProcessConfiguration.xml file for the named element and ensure that each sate listed in the mistake message is present and mapped to a metastate.
Fault example
ProcessConfiguration.xml RequirementBacklog chemical element is missing the state New which exists on the User Story piece of work item type. It should be in the STATES list mapped to type=Proposed".
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Stories" singularName="Story"> <States> <Land value="Active" type="InProgress" /> <State value="Resolved" blazon="InProgress" /> <State value="Closed" blazon="Complete" /> </States> . . . </RequirementBacklog > Resolution example
Metastate mapping has been corrected.
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Stories" singularName="Story"> <States> <State value="New" type="Proposed" /> <State value="Active" type="InProgress" /> <State value="Resolved" type="InProgress" /> <Land value="Airtight" type="Complete" /> </States> . . . </RequirementBacklog > TF402554: Chemical element [elementName] specifies an unsupported metastate [metastateName].
Review the STATES section in the ProcessConfiguration.xml file for the named element and remove or correct the named metastate.
Error example
ProcessConfiguration.xml RequirementBacklog chemical element contains a misspelled metastate mapping for type=Proposed".
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Stories" singularName="Story"> <States> <Country value="New" type="Propsed" /> <State value="Active" type="InProgress" /> <State value="Resolved" blazon="InProgress" /> <State value="Closed" type="Consummate" /> </States> . . . </RequirementBacklog > Resolution example
Metastate mapping has been corrected.
<RequirementBacklog category="Microsoft.RequirementCategory" pluralName="Stories" singularName="Story"> <States> <State value="New" blazon="Proposed" /> <Land value="Agile" blazon="InProgress" /> <Country value="Resolved" blazon="InProgress" /> <State value="Closed" type="Complete" /> </States> . . . </RequirementBacklog > TF402571: Required element [elementName] is missing from Process Configuration.
Edit the ProcessConfiguration.xml file to add the missing named chemical element.
Review ProcessConfiguration XML element reference for required elements.
TF402572: Cannot find specified file in the process template package.
A file specified in a plug-in file for upload is missing from the aught file. Review all files specified for upload and make certain they are included in the procedure zip file.
Review ProcessConfiguration XML chemical element reference for required elements.
TF402574: ProcessConfiguration doesn't specify required TypeField [typeField].
Edit the ProcessConfiguration.xml file to add the missing named TypeField chemical element.
Review ProcessConfiguration XML element reference for required TypeField elements.
Example
The Scrum procedure specifies the following TypeField elements. If any of these are missing, you'll receive error TF402574.
<TypeFields> <TypeField refname="System.AreaPath" type="Team" /> <TypeField refname="Microsoft.VSTS.Scheduling.RemainingWork" type="RemainingWork" format="format h" /> <TypeField refname="Microsoft.VSTS.Common.BacklogPriority" type="Order" /> <TypeField refname="Microsoft.VSTS.Scheduling.Effort" type="Effort" /> <TypeField refname="Microsoft.VSTS.Mutual.Activeness" blazon="Activeness" /> <TypeField refname="Microsoft.VSTS.Feedback.ApplicationStartInformation" type="ApplicationStartInformation" /> <TypeField refname="Microsoft.VSTS.Feedback.ApplicationLaunchInstructions" blazon="ApplicationLaunchInstructions" /> <TypeField refname="Microsoft.VSTS.Feedback.ApplicationType" type="ApplicationType"> <TypeFieldValues> <TypeFieldValue value="Web application" type="WebApp" /> <TypeFieldValue value="Remote machine" blazon="RemoteMachine" /> <TypeFieldValue value="Client awarding" type="ClientApp" /> </TypeFieldValues> </TypeField> </TypeFields> TF402588: Several portfolio backlogs [backlogNames] have divers [backlogName] as their parent. A parent excess may have only one child backlog.
Only one child portfolio excess can map to a single parent backlog.
Edit ProcessConfiguration to right the parent-child excess specifications.
Error example
<PortfolioBacklog category="Microsoft.EpicCategory" parent="Microsoft.InitiativeCategory" pluralName="Epics" singularName="Ballsy"> ... </PortfolioBacklog> <PortfolioBacklog category="Microsoft.FeatureCategory" parent="Microsoft.InitiativeCategory" pluralName="Features" singularName="Feature"> ... </PortfolioBacklog> Resolution example
Change the parent on the Feature backlog to point to the Epic backlog.
<PortfolioBacklog category="Microsoft.EpicCategory" parent="Microsoft.InitiativeCategory" pluralName="Epics" singularName="Epic"> ... </PortfolioBacklog> <PortfolioBacklog category="Microsoft.FeatureCategory" parent="Microsoft.EpicCategory" pluralName="Features" singularName="Feature"> ... </PortfolioBacklog> TF402589: Portfolio backlog [backlogName] references undefined parent portfolio backlog [backlogName].
The ProcessConfiguration.xml definition contains a parent value that references an undefined portfolio backlog.
Error example
<PortfolioBacklog category="Microsoft.FeatureCategory" parent="Microsoft.EpicCategory" pluralName="Features" singularName="Feature"> Resolution example
Add the Epic PortfolioBacklog to the ProcessConfiguration.xml file.
<PortfolioBacklog category="Microsoft.EpicCategory" pluralName="Epics" singularName="Epic"> <States> <Country value="New" blazon="Proposed" /> <State value="Active" blazon="InProgress" /> <Land value="Resolved" type="InProgress" /> <State value="Closed" type="Complete" /> </States> <Columns> <Column refname="System.WorkItemType" width="100" /> <Column refname="System.Title" width="400" /> <Column refname="System.State" width="100" /> <Cavalcade refname="Microsoft.VSTS.Common.BusinessValue" width="50" /> <Column refname="Microsoft.VSTS.CMMI.RequirementType" width="100" /> <Column refname="System.Tags" width="200" /> </Columns> </PortfolioBacklog> TF402590: Several portfolio backlogs [Backlog ane, Backlog 2] don't define their parent.
Only one portfolio backlog, the meridian backlog, may exist unparented. All other backlogs must include a parent="Microsoft.FooCategory" attribute and value.
Resolution example
<PortfolioBacklog category="Microsoft.FeatureCategory" parent="Microsoft.EpicCategory" pluralName="Features" singularName="Feature"> 402595: Too many portfolio backlogs are divers. A maximum of five are allowed.
Edit the ProcessConfiguration.xml file to remove the extra PortfolioBacklog elements from the PortfolioBacklogs section.
Review ProcessConfiguration XML element reference for more than information.
TF400506: This element defines the states for work items that represent Bugs or Defects.
This mistake occurs when the BugWorkItems section is misconfigured. Each state divers for a work item blazon included in the Microsoft.BugCategory must exist in the set of State values defined in the BugWorkItems section. For case, if the following states are defined for piece of work detail types defined for Issues work detail type—New, Approved, Committed, Done—and so the BugWorkItems department should be configured as follows:
<BugWorkItems category="Microsoft.BugCategory" pluralName="Bugs" singularName="Problems"> <States> <States> <State value="New" type="Proposed" /> <Country value="Canonical" type="Proposed" /> <Land value="Committed" type="InProgress" /> <State value="Done" type="Consummate" /> </States> </BugWorkItems> For more information, see ProcessConfiguration XML chemical element reference.
TF400507: Each work detail type must back up an initial country value that matches i of the states defined in: BugWorkItems.
This error occurs when a piece of work item blazon included in the Microsoft.BugCategory specifies an initial land that isn't included in the BugWorkItems section of the ProcessConfiguration XML file. Either fix the XML definition workflow states for the named work particular types, or update the BugWorkItems department to include the missing country(southward).
For more data, encounter ProcessConfiguration XML element reference.
TF400572: The Project Process Settings must be configured for this characteristic to be used.
This is caused by templates that are from TFS 2010 or earlier versions, before the Projection Procedure Settings existed. Try running Configure features after an upgrade to resolve, or add the ProcessConfiguration XML file to the procedure template.
Piece of work item types
TF402570: You've defined [northward] piece of work detail types. A maximum of [witLimit] is allowed.
You've divers more WITs that are allowed in the process. Review your WorkItems.xml file and reduce the number of WORKITEMTYPE statements it contains and remove the associated WIT definition files from the process.
TF402573: Work item blazon WIT doesn't specify required refname attribute.
Work item types (Bug, User Story, Task, etc.) require the refname attribute. The refname value must be unique and cannot comprise any reserved namespaces. The namespaces-System.XXX and Microsoft.VSTS.30-are reserved by Azure DevOps.
Meet All WITD XML elements reference for more than information.
Error example
<WORKITEMTYPE name="Issues"> Resolution example
<WORKITEMTYPE name="Bug" refname="MyCompany.Issues"> TF402599: The piece of work item type refname [refName] isn't valid as it uses a disallowed namespace [namespace].
Reference names of custom fields and WITs can't use reserved namespaces: System.30 and Microsoft.VSTS.XXX.
Edit the refname attribute of the named WIT.
Error example
<FIELD name="Custom Field" refname="Microsoft.VSTS.CustomField" blazon="String" /> Resolution example
<FIELD proper noun="Custom Field" refname="*CustomNamespace.CustomField*" type="String" /> TF402600: The piece of work particular type reference proper name [refName] isn't valid. Work detail type reference names must incorporate simply letters, no spaces, and at least ane flow (.)
WIT reference names must adhere to established naming conventions: only messages, no spaces, and at least i period (.)
Edit the refname attribute of the named WIT to see naming requirements..
Error example
<WORKITEMTYPE name="Bug" refname="MyCompanyBug32"> Resolution example
<WORKITEMTYPE name="Bug" refname="MyCompany.Bug"> Piece of work item fields
TF402538: Field rule [ruleName] isn't supported.
Edit your WIT definitions to remove the named dominion. The following rules are not supported for import to Azure DevOps: MATCH, CANNOTLOSEVALUE, PROHIBITEDVALUES, and NOTSAMEAS.
TF402539: Field [refName] only allows the following rules: [ruleNames].
Edit your WIT definitions for the named field and remove any not-allowed dominion(due south). Review both the FIELDS and WORKFLOW sections. Most system fields do non allow specifying rules.
Valid rules to use with Arrangement fields
| Name | Immune rules |
|---|---|
| Organization.Title | REQUIRED, DEFAULT |
| System.Description | REQUIRED, DEFAULT |
| System.AssignedTo | REQUIRED, DEFAULT, ALLOWEXISTINGVALUE, VALIDUSER |
| System.ChangedBy | REQUIRED, DEFAULT, ALLOWEXISTINGVALUE, VALIDUSER |
TF402540: Work item type [witName] isn't valid because information technology specifies global listing [GLOBALLIST]. Global lists aren't supported.
Global lists are not supported in VSTS. Replace all instances of GLOBALLIST elements with ALLOWEDVALUES and LISTITEM elements in all WIT definition files. Reference: Define pick lists.
Fault example
<FIELD name="CustomField" refname="MyCompany.CustomField" blazon="String"> <ALLOWEDVALUES> <GLOBALLIST proper noun="Disciplines" /> </ALLOWEDVALUES> </FIELD> Resolution instance
<FIELD proper noun="CustomField" refname="MyCompany.CustomField" type="Cord"> <ALLOWEDVALUES> <LISTITEM value="Architecture" /> <LISTITEM value="Requirements" /> <LISTITEM value="Evolution" /> <LISTITEM value="Release Management" /> <LISTITEM value="Project Management" /> <LISTITEM value="Examination" /> </ALLOWEDVALUES> </FIELD> TF402541: Work item type [witName] isn't valid considering it references global list [globalListName]. Global lists aren't supported.
Global lists are not supported in VSTS. Replace all instances of GLOBALLIST elements with ALLOWEDVALUES and LISTITEM elements in all WIT definition files. Reference: Define option lists.
Error example
<FIELD name="CustomField" refname="MyCompany.CustomField" type="String"> <ALLOWEDVALUES> <GLOBALLIST name="Disciplines" /> </ALLOWEDVALUES> </FIELD> Resolution example
<FIELD proper name="CustomField" refname="MyCompany.CustomField" type="String"> <ALLOWEDVALUES> <LISTITEM value="Architecture" /> <LISTITEM value="Requirements" /> <LISTITEM value="Evolution" /> <LISTITEM value="Release Management" /> <LISTITEM value="Project Management" /> <LISTITEM value="Test" /> </ALLOWEDVALUES> </FIELD> TF402542: The custom field refname [refName] isn't valid as information technology uses disallowed namespace [namespace].
The namespaces-System.XXX and Microsoft.VSTS.Thirty-are reserved in VSTS. Reference names of custom fields and types tin't use these namespaces.
To fix this mistake, rename the refname aspect for the named field in the WIT definition files where it appears.
Error instance
<FIELD name="CustomField" refname="System.CustomField" type="Cord" /> - OR - <FIELD name="CustomField" refname="Microsoft.VSTS.CustomField" blazon="String" /> Resolution example
<FIELD name="CustomField" refname="MyCompany.CustomField" blazon="String" /> TF402544: Field [refName], defined in work item type [witName], requires an ALLOWEDVALUES rule that contains values to support chemical element [elementName] specified in ProcessConfiguration.
Edit the named field in the named WIT to provide the missing ALLOWEDVALUES dominion, referencing the named element for more than details.
The ProcessConfiguration.xml file element, TypeField refname="Microsoft.VSTS.Mutual.Activity" type="Activity", requires a pick listing is divers for the Microsoft.VSTS.Mutual.Activity field in all WITs that belong to the Task Category.
<TypeField refname="Microsoft.VSTS.Mutual.Action" type="Activity" /> If y'all have added bugs to the Job Category, you must ensure that the Bug.xml file contains the named field and specifies the same selection listing as is defined for it in the Job.xml file.
Error example
Problems.xml has the field defined, only non the pick list.
<FIELD name="Activity" refname="Microsoft.VSTS.Common.Action" type="Cord" reportable="dimension"> <HELPTEXT>Blazon of work involved</HELPTEXT> </FIELD> Resolution instance
Corrected Problems.xml
<FIELD name="Action" refname="Microsoft.VSTS.Common.Activity" blazon="Cord" reportable="dimension"> <HELPTEXT>Type of work involved</HELPTEXT> <SUGGESTEDVALUES> <LISTITEM value="Evolution"/> <LISTITEM value="Testing"/> <LISTITEM value="Requirements"/> <LISTITEM value="Design"/> <LISTITEM value="Deployment"/> <LISTITEM value="Documentation"/> </SUGGESTEDVALUES> </FIELD> TF402545: Element [elementName] requires that you lot include field [fieldName] in the definition of work item type [witName].
You should include a corresponding FIELD element in the named WIT definition for each field that you specify within the AddPanel section of the ProcessConfiguration.xml file.
You should also include a Control element within the Class department of the named WIT.
Error example
ProcessConfiguration.xml specifies two custom fields. However, these fields aren't defined in the UserStory.xml file.
<AddPanel> <Fields> <Field refname="System.Title" /> <Field refname="Fabrikam.Product" /> <Field refname="Fabrikam.Technology" /> </Fields> </AddPanel> Resolution instance
Missing FIELD elements added to the UserStory.xml file.
<FIELD name="Product" refname="Fabrikam.Product" blazon="Cord" reportable="dimension"> <FIELD name="Technology" refname="Fabrikam.Technology" blazon="String" reportable="dimension"> To support ProcessConfiguration element [elementName], work item type [witName] must ascertain TypeField [typeField] (field refname [refName]).
In the ProcessConfiguration you created a TypeField with TypeFieldValues. In your piece of work particular blazon you have to reference that same TypeField.
Error example
ProcessConfiguration.xml
<TypeField refname="Custom.ApplicationType" type="ApplicationType"> <TypeFieldValues> <TypeFieldValue value="Web application" type="WebApp" /> <TypeFieldValue value="Remote car" blazon="RemoteMachine" /> <TypeFieldValue value="Client awarding" type="ClientApp" /> </TypeFieldValues> </TypeField> FeedbackRequest.xml is using the Microsoft.VSTS.Feedback.ApplicationType field when it should be using the Custom.ApplicationType field.
<FIELD proper name="Application Blazon" refname="Microsoft.VSTS.Feedback.ApplicationType" type="Cord"> ... </FIELD> Resolution example
FeedbackRequest.xml
<FIELD name="Application Type" refname="Custom.ApplicationType" type="String"> ... </FIELD> TF402556: For field [refName] to be well defined, you must proper noun it [fieldName] and set its type to [fieldType]. Provided [refName] is [fieldName] and type is [fieldType].
If yous are on an on-bounds server and running tfsMigrator, this error is ordinarily generated when your process is out-of-date and a system field is non properly defined. In the majority of those cases y'all need to use the witadmin /changefield control to properly rename the field.
Examples of Reserved Fields
Reserved Arrangement.Thirty and Microsoft.VSTS.30 fields take required name and type values.
| Field | Name | Type |
|---|---|---|
| Organization.Id | ID | Integer |
| System.Title | Title | String |
| Microsoft.VSTS.Scheduling.StoryPoints | Story Points | Double |
| Microsoft.VSTS.Scheduling.RemainingWork | Remaining Work | Double |
| Microsoft.VSTS.Scheduling.OriginalEstimate | Original Guess | Double |
| Microsoft.VSTS.Scheduling.CompletedWork | Completed Work | Double |
Error instance
TF402556: For field Microsoft.VSTS.TCM.ReproSteps to be well defined, yous must proper name it Repro Steps and gear up its type to HTML. Provided Microsoft.VSTS.TCM.ReproSteps is My Repro Steps and type is HTML.
In Issues.xml, the friendly field name has been changed to "My Repro Steps".
<FIELD proper name="My Repro Steps" refname="Microsoft.VSTS.TCM.ReproSteps" type="HTML"> <HELPTEXT>How to see the bug. End by contrasting expected with actual behavior.</HELPTEXT> </FIELD> Resolution example
Issues.xml
<FIELD name="Repro Steps" refname="Microsoft.VSTS.TCM.ReproSteps" type="HTML"> <HELPTEXT>How to see the bug. Terminate by contrasting expected with actual beliefs.</HELPTEXT> </FIELD> TF402557: Inconsistent definitions exist for field [refName] in the following work item types: [witName]. Ensure that all references to a field accept the same RefName, Name, and Type.
FIELD element definitions for fields with the same friendly name must be consistent beyond WITs. Check to ensure that the refname, name, and type attributes are the same in each of your WIT definitions for the named field.
Error instance
Issues.xml
<FIELD name="Hair Color" refname="MyCompany.CustomFields.HairColor" type="String" reportable="dimension" /> UserStory.xml
<FIELD proper noun="Pilus Color 2" refname="MyCompany.CustomFields.HairColor" type="Double" reportable="dimension" /> Detect that the name and type attributes differ from that in the Bug.xml work particular type
Resolution example
Bug.xml
<FIELD name="Pilus Color" refname="MyCompany.CustomFields.HairColor" type="Cord" reportable="dimension" /> UserStory.xml
<FIELD name="Hair Color" refname="MyCompany.CustomFields.HairColor" type="String" reportable="dimension" /> TF402558: The definition of field [refName] is inconsistent with the existing definition of the field in the post-obit templates: [templateNames].
Fields must be divers consistently beyond processes that accept been or that you program to import to Azure DevOps Services. The system doesn't let yous to import a process that contains a FIELD chemical element which is defined ane way in Process A and some other style in Process B. All FIELD element attributes must match.
Example
Process A, Bug.xml
<FIELDS> ... <FIELD proper noun="Foo" refname="MyCompany.CustomFields.Foo" type="String" reportable="dimension" /> ... </FIELDS> Process B, Issues.xml
<FIELDS> ... <FIELD name="Bar" refname="MyCompany.CustomFields.Foo" type="Double" reportable="dimension" /> ... </FIELDS> Find how different values are specified for proper name and blazon attributes.
Resolution
Ensure that fields of the same refname are defined the same across all processes that
have been imported or that you plan to import to Azure DevOps Services.
TF402559: The definition for field [refName] is inconsistent with an existing field. The type is [typeName] merely should be [typeName].
Edit the WIT file(southward) that contains the named field to ensure the specified type attribute value is consistent across all WITs.
TF402562: You lot've defined [n] fields for piece of work detail type [witName]. Merely [fieldLimit] are allowed.
You've defined [north] fields for work item type [witName]. Merely [fieldLimit] are immune. Inside a single WIT, yous can specify only the specified number of fields.
Edit the named WIT and remove the actress custom fields to reduce the total number of fields to be within the allowed limit.
TF402563: You've defined a full of [n] fields for all work item types. Only [fieldLimit] are immune.
Y'all've defined [due north] fields for all WITs defined in the process. Simply [fieldLimit] are immune. This includes System.Thirty and Microsoft.VSTS.XXX namespace fields as well as custom fields.
Review the FIELDS and WORKFLOW sections and determine which custom fields to remove.
TF402566: Yous've defined [north] field rules for work item type [witName]. A maximum of [ruleLimit] is immune.
You've defined [n] field rules for the named WIT which exceeds the immune number of field rules for any 1 WIT.
Edit the named WIT and remove the extra field rules to reduce the total number of fields to be within the allowed limit.
TF402568: Yous've defined [n] fields with syncnamechanges="true" for work detail type [witName]. A maximum of 64 is allowed.
The number of fields with syncnamechanges="true" defined for the named WIT exceeds the immune limit. This includes Organization.Xxx and Microsoft.VSTS.XXX namespace fields besides equally custom fields.
Review the FIELDS department of the named WIT and determine which custom fields to remove or modify.
Example
<FIELD name="Assigned To" refname="System.AssignedTo" blazon="String" reportable="dimension" syncnamechanges="true" > ... </FIELD> TF402569: Y'all've defined [n] values for field [fieldName] in work particular type [witName]. A maximum of [listLimit] is immune.
The number of LISTITEM elements defined for the named field in the named WIT exceeds the immune limit.
Edit the named WIT to reduce the number ofLISTITEM elements so as not to exceed the allowed maximum.
Example
<FIELD proper name="Favorite Color" refname="MyCompany.CustomFields.FavColor" blazon="String" reportable="dimension"> <ALLOWEDVALUES> <LISTITEM value="Color1" /> <LISTITEM value="Color2" /> <LISTITEM value="Color3" /> . . . </ALLOWEDVALUES> </FIELD> Discover the bug and user story refname values are different.
TF402584: Field dominion attributes "for" or "not" aren't supported.
The "for" and "non" attributes are not supported at all for any field rule for import to Azure DevOps Services.
Review the FIELDS and WORKFLOW sections for the presence of "for" and "not" attributes and remove them.
Error instance
<FIELD name="Championship"> <READONLY for="Dev Squad" not="Test Squad" /> </FIELD> Resolution instance
<FIELD proper noun="Title"> <READONLY /> </FIELD> TF402593: Field rules aren't supported for field [fieldName].
Most Arrangement and Microsoft.VSTS fields practice not support rules. See Customize a process for complete list of supported field rules.
Edit the WIT definition files that incorporate the named field and remove the field rules specified for it.
TF402602: The field [refName] must have exactly these values [values].
All fields defined by VSTS in the reserved namespaces-Organisation.Xxx and Microsoft.VSTS.XXX-must not be contradistinct. If you wish to have a different listing of values in these pick listing fields, define your own custom field.
Error example
Bug.xml has the priority field defined, merely has a different list of values than expected.
<FIELD name="Priority" refname="Microsoft.VSTS.Mutual.Priority" blazon="Integer" reportable="dimension"> <ALLOWEDVALUES expanditems="truthful"> <LISTITEM value="0"/> <LISTITEM value="1"/> <LISTITEM value="two"/> </ALLOWEDVALUES> <DEFAULT from="value" value="two" /> </FIELD> Resolution example
Corrected Problems.xml including a new field
<FIELD name="Priority" refname="Microsoft.VSTS.Mutual.Priority" type="Integer" reportable="dimension"> <HELPTEXT>Business organization importance. ane=must gear up; 4=unimportant.</HELPTEXT> <ALLOWEDVALUES expanditems="true"> <LISTITEM value="1"/> <LISTITEM value="2"/> <LISTITEM value="iii"/> <LISTITEM value="4"/> </ALLOWEDVALUES> <DEFAULT from="value" value="two" /> </FIELD> <FIELD name="Custom Priority" refname="Custom.Priority" type="Integer" reportable="dimension"> <HELPTEXT>Business organization importance. 1=must fix; 4=unimportant.</HELPTEXT> <ALLOWEDVALUES expanditems="true"> <LISTITEM value="0"/> <LISTITEM value="1"/> <LISTITEM value="2"/> </ALLOWEDVALUES> <DEFAULT from="value" value="2" /> </FIELD> VS402504: User or group cannot be found [project]\Group Name. Verify that the users and groups used in your work particular type definition exist.
Custom projection scoped groups are not supported. Yous can only reference account level scoped groups.
Error instance
Bug.xml is referencing a project scoped grouping.
... "[project]\Organization Leaders" Resolution example
Create a new business relationship (collection) level grouping "Organization Leaders" and reference information technology appropriately in the XML.
... "[global]\Organization Leaders" Note
A freshly created global group might have a little while earlier being found by the import procedure.
TF237094: Field proper noun '[fieldName]' is used by the field '[refName]', so it cannot be used by the field '[refName]'.
Field name already exist with that same name on a dissimilar field. Change the name of the field.
Error example
TF237094: Field name 'External ID' is used by the field 'Custom.ExistingField.ExternalID', so it cannot be used past the field 'Custom.NewField.ExternalID'.
Resolution example
Change the field name of Custom.NewField.ExternalID
<FIELD name="External ID" refname="Custom.NewField.ExternalID" blazon="string" reportable="dimension" /> Piece of work item layout
VS403104: Work item type [witName] references the required field [refName] which is not included in all layouts.
This alarm is generated if y'all have a required field in a piece of work particular type that is referenced in the <Layout> node but not the <WebLayout>. The <WebLayout> is used to modify the layout of the new form. See WebLayout xml reference for details.
VS403073: Group & <Grouping Name>: violates the rule that a group can only contain a unmarried HTML or WebPage control preceded by label controls..
In the new course layout, a group tin only contain ane HTMLFieldControl or WebPageControl.
Error example
<Section> <Grouping Characterization="Description:"> <Control Characterization="Reason For Asking:" Type="HtmlFieldControl" FieldName="Arrangement.Clarification" /> <Command Characterization="Business Case For Request:" Type="HtmlFieldControl" FieldName="MB.BusinessCase" /> </Group> </Section> To resolve this, create two separate groups that contain i control each.
Resolution example
<Section> <Group Label="Reason for Request"> <Control Characterization="Reason For Request:" Type="HtmlFieldControl" FieldName="System.Description" /> </Group> <Group Label="Business Case"> <Control Label="Business organisation Instance For Asking" Type="HtmlFieldControl" FieldName="Custom.BusinessCase" /> </Grouping> </Section> TF402594: File violates the schema with the following error: The element 'Control' cannot comprise kid element 'Link' because the parent element's content model is empty.
Mistake example
<Command Type="FieldControl" FieldName="customfield.foo" Label="Foo" LabelPosition="Left"> <Link UrlRoot="http://www.visualstudio.microsoft.com/team-services/" /> </Control> Resolution example
<Control Type="FieldControl" FieldName="System.Title" LabelPosition="Left" Label="Title 1" <LabelText> <Text> <Link UrlRoot="http://www.visualstudio.microsoft.com/squad-services/" /> Title 2 </Text> </LabelText> </Control> Workflow definitions
TF402567: You've divers [n] workflow states for work item type [witName]. A maximum of [stateLimit] is allowed.
Yous've defined [north] workflow states for the named WIT which exceeds the allowed number of workflow states for whatever one WIT.
Edit the WORKFLOW section of the named WIT and remove the actress STATE elements to reduce the total number of states to be within the allowed limit.
TF402578: Field [refName] specifies friendly name [friendlyName] which is already in employ past field [refName]. Friendly names must be unique across all field definitions.
Field names must be unique inside the work particular type.
Error example
<FIELD name="Foo" refname="MyCompany.CustomFields.Foo" type="String" reportable="dimension" /> <FIELD name="Foo" refname="MyCompany.CustomFields.Bar" type="String" reportable="dimension" /> Notice there are two fields with the name <FIELD proper name="Foo"
Resolution instance
<FIELD name="Foo" refname="MyCompany.CustomFields.Foo" type="String" reportable="dimension" /> <FIELD name="Bar" refname="MyCompany.CustomFields.Bar" type="String" reportable="dimension" /> TF402579: Proper name [friendlyName] is used multiple times on different fields beyond the post-obit work particular types: [witNames]. Name for fields must be unique across the project collection.
Fields referencing the same refname="MyCompany.FieldName" must accept the same friendly name FIELD proper name="fieldname" value.
Error example
Process A, Bug.xml
<FIELD name="Foo" refname="MyCompany.CustomFields.Foo" blazon="String" reportable="dimension" /> Procedure B, Bug.xml
<FIELD proper noun="Bar" refname="MyCompany.CustomFields.Foo" type="String" reportable="dimension" /> Because both fields share the aforementioned reference name, refname="MyCompany.CustomFields.Foo", they must also specify the aforementioned friendly proper name <FIELD name="Foo" across all processes that have been imported or will exist imported to Azure DevOps Services.
TF402580: You lot tin can just use the name [witName] for a single work item type.
WIT friendly names WORKITEMTYPE proper name="Proper noun" must be unique inside the procedure.
Error example
My Work Item A.xml
<WORKITEMTYPE proper name="My Work Detail" refname="My.MyWorkItemA"> My Work Item B.xml
<WORKITEMTYPE name="My Piece of work Particular" refname="My.MyWorkItemB"> Find how the WORKITEMTYPE name= is the same across both work item types.
Resolution instance
My Work Item A.xml
<WORKITEMTYPE name="My Work Item A" refname="My.MyWorkItemA"> My Work Item B.xml
<WORKITEMTYPE name="My Work Particular B" refname="My.MyWorkItemB"> TF402581: You tin can only apply the refname [refName] for a single work item blazon.
WIT reference names refname="value" must be unique within the process.
Error example
Bug.xml
<WORKITEMTYPE proper noun="Bug" refname="MyCompany.Name"> UserStory.xml
<WORKITEMTYPE name="User Story" refname="MyCompany.Proper noun"> notice both refname values equal "MyCompany.Name"
Resolution example
Bug.xml
<WORKITEMTYPE name="Bug" refname="MyCompany.Problems"> UserStory.xml
<WORKITEMTYPE name="User Story" refname="MyCompany.UserStory"> TF402582: Work detail blazon [witName] contains custom control [controlName] which is not supported.
Custom controls are not supported in Azure DevOps Services. Review the Course department for the named WIT and remove whatever custom controls that are defined.
Mistake example
Type="OneViewMultiValueControl" specifies a custom control. This must be removed or replaced to a supported command.
<Group Label="Engineering Alignment"> <Column PercentWidth="100"> <Control FieldName="Fabrikam.Content.Product" Blazon="FieldControl" Label="Product" LabelPosition="Left" /> <Control FieldName="Fabrikam.Content.Release" Type="FieldControl" Label="Milestone" LabelPosition="Left" /> <Control FieldName="Fabrikam.Content.Engineering" Type="FabrikamMultiValueControl" Label="Technology" LabelPosition="Left" /> </Column> </Group> Test management plug-in errors
The TestManagement.xml file, located in the Test Management folder, must adapt to the syntax and rules described in Define the initial configuration of Test Manager.
TF402533: Element '[elementName]' in TestManagement plug-in is missing the 'fileName' attribute.
Add the missing attribute to the named element in the TestManagement.xml file.
TF402534: TestManagement plug-in contains an unsupported chore '[taskName]'
Correct the named tasked in your TestManagement.xml file.
Error example
The TestResolutionStates element has been misspelled.
<taskXml> <TestResolutionSattes fileName="Examination Management\TestResolutionState.xml" /> </taskXml> Resolution example
Corrected misspellings.
<taskXml> <TestResolutionStates fileName="Exam Management\TestResolutionState.xml" /> </taskXml> Related articles
- Validate and import processes
- Azure DevOps Data Import Service
Feedback
Submit and view feedback for
Source: https://docs.microsoft.com/en-us/azure/devops/organizations/settings/work/import-process/resolve-errors