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

Adding the attachments to Azure DevOps work item in "Create a Work item" step

Hi ,

 

Is there a way to attach a certain file from email directly to the attachments section in the User story of Azure DevOps, I'm currently having a flow that creates a work item whenever tehre is a new email but can't able to process the attachments linked to it. I need those attachments in the user story itself. Can somebody help me??

64 REPLIES 64

Hi @Anonymous 

 

Currently adding an attachment as a direct action is not supported in flow. However, you can refer to the thread below where a workaround has been suggested for creating the attachments:

https://powerusers.microsoft.com/t5/Building-Flows/Create-work-item-at-Azure-DevOps-from-an-email-with-attachments/td-p/176019

 

You can post an idea here to include this as a feature in flow:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Make sure you name everything the exact same thing as what I have if you are copying and pasting from here. You will need to add in your organization name.

The schema is:

First part flow.PNG

 

 

{
    "type": "object",
    "properties": {
        "Id": {
            "type": "string"
        },
        "Name": {
            "type": "string"
        },
        "ContentBytes": {
            "type": "string"
        },
        "ContentType": {
            "type": "string"
        },
        "Size": {
            "type": "integer"
        }
    }
}

 

 

 

Then

Post the attachment.PNG

the binary function is: 

 

 

 

binary(body('Parse_JSON')?['ContentBytes'])

 

 

 

Make sure you change the areaPath in the relative URI. I left it as mine which is just Portal.
Code snippet for the step above: 
{
    "inputs": {
        "host": {
            "connection": {
                "name""@parameters('$connections')['shared_visualstudioteamservices']['connectionId']"
            }
        },
        "method""post",
        "body": {
            "Method""POST",
            "Headers": {
                "Content-Type""application/octet-stream"
            },
            "Body""@{binary(body('Parse_JSON')?['ContentBytes'])}",
            "IsBase64"true
        },
        "path""/httprequest",
        "queries": {
            "account""YourOrganization"
        },
        "authentication""@parameters('$authentication')"
    },
    "metadata": {
        "flowSystemMetadata": {
            "swaggerOperationId""HttpRequest"
        }
    }
}
Then
compose.PNG
The 'Body' in 'Compose' is the body that you will get from the Http Post which I have named 'Post Attachment'
The 'url' is actually an output function: 

 

 

 

outputs('Compose')['url']

 

 

 

The outputs function is getting the url property from the response json from Post Attachment.
Code snippets for the steps above:
Compose:
{
    "inputs""@body('Post_Attachment')"
}
Compose 2
{
    "inputs""@outputs('Compose')['url']"
}
 

Then

Final 3.PNG
The 'Id' is the work Item Id that gets returned form the create a new work item step. 
The 'Outputs' is from 'Compose2'. It should pop up for you on the add dynamic content popup.  
Code snippet for the step above:
{
    "inputs": {
        "host": {
            "connection": {
                "name""@parameters('$connections')['shared_visualstudioteamservices']['connectionId']"
            }
        },
        "method""post",
        "body": {
            "Method""PATCH",
            "Headers": {
                "Content-Type""application/json-patch+json"
            },
            "Body""[\n  {\n    \"op\": \"add\",\n    \"path\": \"/relations/-\",\n    \"value\": {\n      \"rel\": \"AttachedFile\",\n      \"url\": \"@{outputs('Compose_2')}\",\n      \"attributes\": {\n        \"comment\": \"Spec for the work\"\n      }\n    }\n  }\n]",
            "IsBase64"false
        },
        "path""/httprequest",
        "queries": {
            "account""YourOrganization"
        },
        "authentication""@parameters('$authentication')"
    },
    "metadata": {
        "flowSystemMetadata": {
            "swaggerOperationId""HttpRequest"
        }
    }
}

 

 

Hope this helps!

Make sure you name everything the exact same thing as what I have if you are copying and pasting from here. You will need to add in your organization name.

First part flow.PNG

The schema is:

 

{
"type": "object",
"properties": {
"Id": {
"type": "string"
},
"Name": {
"type": "string"
},
"ContentBytes": {
"type": "string"
},
"ContentType": {
"type": "string"
},
"Size": {
"type": "integer"
}
}
}

 

Then
Post the attachment.PNG
the binary function is: 

 

binary(body('Parse_JSON')?['ContentBytes'])

 

Make sure you change the areaPath in the relative URI. I left it as mine which is just Portal.
 
Then
compose.PNG
The 'Body' in 'Compose' is the body that you will get from the Http Post which I have named 'Post Attachment'
The 'url' is actually an output function: 

 

outputs('Compose')['url']

 

The outputs function is getting the url property from the response json from Post Attachment.
 
Then
Final 3.PNG
The 'Id' is the work Item Id that gets returned form the create a new work item step. 
The 'Outputs' is from 'Compose2'. It should pop up for you on the add dynamic content popup.  

Hope this helps!

Anonymous
Not applicable

@TheSwilliam 

Thank you for the solution. I implemented your solution and the flow did run successfully, but the file wasn't attached to the work item in Azure DevOps. Can you please advise?

Hi @Anonymous,

 

Can you send screen shots of your two Http request actions? You have to make sure the first is a POST with the header "Content-Type""application/octet-stream". The second one has to be a PATCH with the header  "Content-Type": "application/json-patch+json" 

Anonymous
Not applicable

@TheSwilliam 

Thank you for your quick response.

Please find attached the screenshots:

johns4Upmc_0-1599074442994.png

 

 

johns4Upmc_1-1599074584001.png

 

@Anonymous everything looks good there. Do you mind sending the binary function and the compose functions. You can just send the code. Also what type of files are you sending/how big are they? You may need to change your upload type from simple to chunked. Here is the link if you'd like to read about it. 

https://docs.microsoft.com/en-us/rest/api/azure/devops/wit/attachments/create?view=azure-devops-rest-6.0#start-a-chunked-upload

Anonymous
Not applicable

@TheSwilliam 

 

johns4Upmc_0-1599075680979.png

Binary Function : 

binary(body('Parse_JSON')?['ContentBytes'])
Anonymous
Not applicable

@TheSwilliam The file is a normal .txt or .pdf file

@Anonymous I see your issue. You are grabbing the wrong body in your first compose. You need to grab the body that the first http request generates. 

Anonymous
Not applicable

Thank you @TheSwilliam. I did update the body part, but still the files are not getting attached. 

@Anonymous  I think you are also grabbing the wrong thing in your compose2. When you peak at the code this is what you should see in your compose 2:

outputs('Compose')['url'])

Anonymous
Not applicable

@TheSwilliam 

Thank you so much. I was able to attach the file to the Work Item in Azure DevOps.

Anonymous
Not applicable

Is there any reason why Post Attachment isn't an option for me? I'm just using the pro trial right now, but is it possible our instance of Azure Devops might be limiting functionality in some way?

Anonymous
Not applicable

@Anonymous I believe you would need Azure DevOps Premium connector to implement this functionality.

@Anonymous I renamed the ‘send an http request to azure devops’ action to ‘Post Attachment’ that’s why it isn’t showing up for you. Just use send an http request to azure devops and you’ll be good 

Nice solution and worked flawlessly for my flow.

Thanks!

Great tutorial,  I'm getting error and i have tried everything not sure why i'm getting it as followed the instructions closely:

You must pass a valid patch document in the body of the request.  I am testing with a .xlsx
Azure DevOps ActivityId: 4bbf592f-9f6d-4b1b-9b37-64c3fab79e50
Details: {"$id":"1","innerException":null,"message":"You must pass a valid patch document in the body of the request.","typeName":"Microsoft.VisualStudio.Services.Common.VssPropertyValidationException, Microsoft.VisualStudio.Services.Common","typeKey":"VssPropertyValidationException","errorCode":0,"eventId":3000}
clientRequestId: eaa606b1-3ae9-4041-8b18-27309ce4f369

Here is what i have in the body:

[
{
"op:"add",
"path":"/relations/-",
"value":{
"rel":"AttachedFile",
"url":"@{outputs('Compose_2')}",
"attributes":{
"comment":"Adding attachments"
}
}
}
]

 

Any help would be appreciated it. 

Great tutorial,  I'm getting error and i have tried everything not sure why i'm getting it as followed the instructions closely:

You must pass a valid patch document in the body of the request.  I am testing with a .xlsx
Azure DevOps ActivityId: 4bbf592f-9f6d-4b1b-9b37-64c3fab79e50
Details: {"$id":"1","innerException":null,"message":"You must pass a valid patch document in the body of the request.","typeName":"Microsoft.VisualStudio.Services.Common.VssPropertyValidationException, Microsoft.VisualStudio.Services.Common","typeKey":"VssPropertyValidationException","errorCode":0,"eventId":3000}
clientRequestId: eaa606b1-3ae9-4041-8b18-27309ce4f369

Here is what i have in the body:

[
{
"op:"add",
"path":"/relations/-",
"value":{
"rel":"AttachedFile",
"url":"@{outputs('Compose_2')}",
"attributes":{
"comment":"Adding attachments"
}
}
}
]

 

Any help would be appreciated it. 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Users online (5,119)