cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Upload an attachment from MS forms to Azure Devops

Hello 

 

I have checked que topics in the community but I was not able to conclude what I need. I have a form - simple one, to request help for operation situations - and sometimes, an attachment is needed. Can be a png, xls, doc. 

 

I want to include the attachment in the work item Im sending to the support. So, the flow I have right now is just:

 

When a new response is submitted

Get response details

Create a work item

 

Questions: how do I get the attachment and how do I upload in the work item?

 

Thank you

1 ACCEPTED SOLUTION

Accepted Solutions

EDIT:
Below only worked if an attachment was actually uploaded but failed if no upload was made.
To fix this, we add a condition based on length on the actual form output that we are using and put the "Parse JSON" and "For Each Attachment" within that "If yes".

 

The condition should be " "0" is not equal to "length(body('Get_response_details')?['the_form_question'])" "

 

NiclasWJ_0-1698997766900.png

 

 

 

Hi @lupompei & @David_MA 

Recently I managed to get this working and since I do not see this "solution" elsewhere in the community I thought of posting it.
This solution adds ALL attachments for me.

 

I am no Power Automate veteran so have that in mind, and sorry in advance for the mix of Swedish and English in the samples below.

NiclasWJ_0-1698658452255.png

NiclasWJ_1-1698658452256.png

NiclasWJ_2-1698658452257.png

 

Explanation:

1. "Parse the JSON" with the question including the upload attachment from the MS Forms "Get Response Details"

Scheme:

 

{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {
            "name": {
                "type": "string"
            },
            "link": {
                "type": "string"
            },
            "id": {
                "type": "string"
            },
            "type": {},
            "size": {
                "type": "integer"
            },
            "referenceId": {
                "type": "string"
            },
            "driveId": {
                "type": "string"
            },
            "status": {
                "type": "integer"
            },
            "uploadSessionUrl": {}
        },
        "required": [
            "name",
            "link",
            "id",
            "type",
            "size",
            "referenceId",
            "driveId",
            "status",
            "uploadSessionUrl"
        ]
    }
}

 

2. "For Each" I then:

3. "OneDrive for Business - Get File Content by Path" where the content is the path such as apps/Microsoft Forms/{form name}/{question}/@{items('For_Each_Attachment')['name']} - This to get the content of all files as Base64, Name is from the first Parse JSON

4. "Compose" with the expression below - This is to retrieve only the Base64 content from the Get File Content which contains other information as well.

 

outputs('Get_File_Content_by_Path')?['body/$content']

 


5. "Send a HTTP request to Azure DevOps - Send Attachment to DevOps" with:

POST

URL = {project}/_apis/wit/attachments?filename=@{items('For_Each_Attachment')['name']}&api-version=7.1

Content-Type = application/octet-stream

Body = Output of "Compose"

Set body as Base64

This is to send the attachment into DevOps, this does not link it to any workitem. Name is from the first Parse JSON.

6. "Parse JSON" with the output from "Send Attachment to DevOps" as content and the following scheme:

 

{
    "type": "object",
    "properties": {
        "id": {
            "type": "string"
        },
        "url": {
            "type": "string"
        }
    }
}

 

This is so we can know what the URL is of the attachment we want to attach later on.

 

7. "Send a HTTP request to Azure DevOps - Add attachment" with:

PATCH

URL = {project}/_apis/wit/workitems/@{outputs('Create_change_request')?['body/id']}/?api-version=7.2-preview

@{outputs('Create_change_request')?['body/id']} is the ID of your workitem which is created before in the flow

Content-Type = application/json-patch+json

Body = ( url = "url" from lst Parse JSON ) ( name = name from first Parse JSON )

 

[
{
"op": "add",
"path": "/relations/-",
"value":
{
"rel": "AttachedFile",
"url": "@{body('Parsa_JSON_2')?['url']}",
"attributes": 
{
"comment": "Automatic attachment upload",
"name":"@{items('For_Each_Attachment')['name']}"
}
}
}
]

 

View solution in original post

4 REPLIES 4

This is something I have been wanting to do as well, but have not tried yet. According to ChatGPT, you can use the Other Fields option in the action to attach a file to the work item. In the Other Fields option, you would send it a JSON object with the corresponding values. It says to use this for attachments:

{
  "attachments": [
    {
      "op": "add",
      "path": "/fields/System.History",
      "value": "<p>Attached file: [filename]</p>",
      "resource": {
        "fileName": "[filename]",
        "fileContent": "[base64-encoded file content]"
      }
    }
  ]
}

It also says, replace [filename] with the desired file name and [base64-encoded file content] with the base64-encoded content of the file you want to attach. Note that the fileName property within the resource object should also match the file name.

 

In the above example, the file attachment is added to the work item's System.History field. You can modify the path property to specify a different field for the attachment if needed.

 

To use this JSON object in Power Automate, you can include it as part of the "Other Fields" value within the "Create work item" action. Specify the "Other Fields" value as the JSON object described above, and the file will be attached to the work item during creation.

 

Remember to encode the file content as base64 before including it in the JSON object. You can use appropriate methods or actions in Power Automate to convert the file content to base64 format before assigning it to the fileContent property.

 

Keep in mind that there may be limitations on file size and attachment capabilities in Azure DevOps. Make sure to review and comply with the Azure DevOps documentation regarding attachments and any restrictions that may apply.

EDIT:
Below only worked if an attachment was actually uploaded but failed if no upload was made.
To fix this, we add a condition based on length on the actual form output that we are using and put the "Parse JSON" and "For Each Attachment" within that "If yes".

 

The condition should be " "0" is not equal to "length(body('Get_response_details')?['the_form_question'])" "

 

NiclasWJ_0-1698997766900.png

 

 

 

Hi @lupompei & @David_MA 

Recently I managed to get this working and since I do not see this "solution" elsewhere in the community I thought of posting it.
This solution adds ALL attachments for me.

 

I am no Power Automate veteran so have that in mind, and sorry in advance for the mix of Swedish and English in the samples below.

NiclasWJ_0-1698658452255.png

NiclasWJ_1-1698658452256.png

NiclasWJ_2-1698658452257.png

 

Explanation:

1. "Parse the JSON" with the question including the upload attachment from the MS Forms "Get Response Details"

Scheme:

 

{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {
            "name": {
                "type": "string"
            },
            "link": {
                "type": "string"
            },
            "id": {
                "type": "string"
            },
            "type": {},
            "size": {
                "type": "integer"
            },
            "referenceId": {
                "type": "string"
            },
            "driveId": {
                "type": "string"
            },
            "status": {
                "type": "integer"
            },
            "uploadSessionUrl": {}
        },
        "required": [
            "name",
            "link",
            "id",
            "type",
            "size",
            "referenceId",
            "driveId",
            "status",
            "uploadSessionUrl"
        ]
    }
}

 

2. "For Each" I then:

3. "OneDrive for Business - Get File Content by Path" where the content is the path such as apps/Microsoft Forms/{form name}/{question}/@{items('For_Each_Attachment')['name']} - This to get the content of all files as Base64, Name is from the first Parse JSON

4. "Compose" with the expression below - This is to retrieve only the Base64 content from the Get File Content which contains other information as well.

 

outputs('Get_File_Content_by_Path')?['body/$content']

 


5. "Send a HTTP request to Azure DevOps - Send Attachment to DevOps" with:

POST

URL = {project}/_apis/wit/attachments?filename=@{items('For_Each_Attachment')['name']}&api-version=7.1

Content-Type = application/octet-stream

Body = Output of "Compose"

Set body as Base64

This is to send the attachment into DevOps, this does not link it to any workitem. Name is from the first Parse JSON.

6. "Parse JSON" with the output from "Send Attachment to DevOps" as content and the following scheme:

 

{
    "type": "object",
    "properties": {
        "id": {
            "type": "string"
        },
        "url": {
            "type": "string"
        }
    }
}

 

This is so we can know what the URL is of the attachment we want to attach later on.

 

7. "Send a HTTP request to Azure DevOps - Add attachment" with:

PATCH

URL = {project}/_apis/wit/workitems/@{outputs('Create_change_request')?['body/id']}/?api-version=7.2-preview

@{outputs('Create_change_request')?['body/id']} is the ID of your workitem which is created before in the flow

Content-Type = application/json-patch+json

Body = ( url = "url" from lst Parse JSON ) ( name = name from first Parse JSON )

 

[
{
"op": "add",
"path": "/relations/-",
"value":
{
"rel": "AttachedFile",
"url": "@{body('Parsa_JSON_2')?['url']}",
"attributes": 
{
"comment": "Automatic attachment upload",
"name":"@{items('For_Each_Attachment')['name']}"
}
}
}
]

 

hi , thanks. I will try to implement here and check if works for me. Really appreciate

Thanks for sharing @NiclasWJ - worked like a charm!

I used the SharePoint Get file content using Path as I am using a Form that is stored under a Group/Team. 

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

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.    

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