AreaPath and IterationPath Explanation

Hi I am getting errors with AreaPath-1 and IterationPath-1 Status: Invalid Path Value: Sandbox\Sandbox

{
	"ObjectType": "VstsSyncMigrator.Engine.Configuration.Processing.NodeStructuresMigrationConfig",
	"Enabled": false,
	"BasePaths": ["Product\\Area\\Path1", "Product\\Area\\Path2"]
	"PrefixProjectToNodes": false
}

Can I get an explanation of this area of config file code? I don’t really understand the syntax for Product\\Area\\Path1.

Let’s say my source project that I am migrating has the Area Field: Sandbox and Iteration Field: Sandbox. Do I need to update those BasePath values to Sandbox\Sandbox, assuming my Project name is also Sandbox?

How does this specify iteration?

I noticed that in documentation, PrefixProjectToNodes inserts the path from the source. Do I need to set BasePath if that is the case?

[benz66]

Hi Guys, I’m still having some problems understanding the syntax here even after reading both issue documents. I am migrating from TFS to ADO and I am setting the following base path “\TFS Project Name\Area\Sub-Area” and I see all discovered Areas and Iterations for the whole TFS Project being ignored. It seems that this filter is not even correct? Any help would be most appreciated. Kind regards, Ben

[MichelZ]

Basically you have <projectName>\Area\<path> and <projectName>\Iteration\<path> as “templates”

So for the Sandbox project, it always starts with

\Sandbox\Area for Areas

and \Sandbox\Iteration for Iterations.

It was mainly meant for splitting up projects when migrating from TFS to VSTS. E.g. we had many actual “code” projects in a single TFS Project before (as per previous microsoft guideance) and decided to split them up. So we were able to take specific area/iteration paths into specific (multiple) target projects. E.g. everything under \Sandbox\Area\Projects\SomeProjectName to \SomeProjectName\Area and everything under \Sandbox\Area\Projects\AnotherProject to \AnotherProject\Area