cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

VSTS connection Create Work Item in Area

Hi,

 

I have recently set-up a work-flow to log support tickets automatically in VSTS. This works fine when routing a task to the root project however I choose to log the issue in an area I get the following message

 

Body

{ "$id": "1", "innerException": null, "message": "TF401347: Invalid tree name given for work item -1, field 'System.AreaPath'.", "typeName": "Microsoft.TeamFoundation.WorkItemTracking.Server.WorkItemFieldInvalidTreeNameException, Microsoft.TeamFoundation.WorkItemTracking.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "typeKey": "WorkItemFieldInvalidTreeNameException", "errorCode": 600171, "eventId": 320
 
I'm not sure if I'm putting this information in the correct field. Within the Create new work item step I'm entering the name in the area field. 
 
Any help with this would be appreciated
 
thanks
 
Chris
4 REPLIES 4
tpalmer
Power Automate
Power Automate

Hi Chris - it looks like the area path you're providing is not matching an area path in your VSTS account. Would you be able to send me a quick direct message with more details of what you're entering in Flow and what you see as the area path in VSTS? Thanks!

Thanks for the update. I was facing this issue and after reading your answer I realised my AreaPath name was not present in my VSTS account. (Y)

Otometrics
Regular Visitor

Hello,

 

I too am facing an issue with the area path coming from VSO. I have created a flow for PBI created in one project (P1) of VSO should also be created parallelly in another project (P2). In the Trigger, I have set the area path that should come from the work item created in project p1 and in the Action I am using the Area Path from P1 to set the Area Path for new work item in P2 (I have already created matching area paths in both projects). But MSFlow instead of picking area path from p1 picks it from p2 and sets it incorrectly.

Eric_Zhao
New Member

I maintain an integration between VSTS and Aha!, and I also see the error "Invalid tree name" from time to time. The reason is that product structure is not consistent in the two systems. The product name and product structure/hierarchy must be exactly the same. In your case I suggest you check the integrated systems to make sure they're consistent. 

Helpful resources

Announcements
MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Microsoft Build 768x460.png

Microsoft Build is May 24-26. Have you registered yet?

Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.

May UG Leader Call Carousel 768x460.png

What difference can a User Group make for you?

At the monthly call, connect with other leaders and find out how community makes your experience even better.

PA Survey Carousel Image.png

We want to hear from you!

If you are a small business ISV/Reseller, share your thoughts with our research team.

Users online (1,545)