Hi all,
I am currently trying to build a flow where in completion of an Adobe Sign web form, the flow kicks off, takes the form fields and maps them to the corresponding columns of a SharePoint List.
My flow is currently looking like this:
I'm not sure if this is the correct way to go about this process or how to layout the parse JSON schema so any help or advice would be greatly appreciated.
Thanks,
Hannah 😊
Hi @Hannah123 ,
The approach is correct and the "Parse JSON" schema will depend on the field names exported from Adobe Sign. I never integrated the "Web forms" feature into Power Automate, but assuming that it works similarly to the Adobe Sign agreements generated from templates, you can even build your flow without the "Parse JSON" schema, by populating your "Create item" action with expressions.
For either of these approaches (with or without "Parse JSON" action), I will be happy in helping you with this solution. For that, we will just need you to share the raw outputs from the "Get form field data of agreement in JSON format", so we can understand the structure of the data returned by Adobe Sign. If you don't know how to access the raw outputs, refer to this step-by-step: http://digitalmill.net/2023/06/29/how-to-access-the-raw-outputs-in-power-automate/
Also, make sure to remove any sensitive content from the JSON before sharing it 🙂
Hi @rzaneti, that was a great help.
I now have most of the form fields populating the correct columns in my SharePoint list.
The problem I am having now is that on the form itself there are four different file uploads. I need to somehow put these files into the attachment column in my SharePoint list.
These upload fields are being picked up in my Parse JSON schema, but I am unsure how to add them to the SharePoint list as there is not option for this in the 'Create Item' function.
@Hannah123 @rzaneti This is what I am trying to do also. I have 2 web forms. 1 is just filled out by an end user then approved by someone else. The other is sent to multiple people before finally getting approved.
However, even though I have the event set to "When a web form agreement workflow is completed successfully", i will get multple sharepoint entries, 1 for each for each person it touches.
For my first web form that goes to 2 people, I get all the info in my first sharepoint item that the web filler completed, then a second sharepoint entry thats completely blank because all it is is an an approver. My other webform, since it gets submitted by the form filler, then goes to 3 different people after that, i get 4 different sharepoint entries.
I just want 1 entry after everything has been completed and approved.
Anyone else having an issue like this or know how to fix?
I have this same issue. It works seamlessly when you only have one signature, but it creates multiple list items when the form needs multiple signatures. Let me know if you figure this out.
I have a meeting with Adobe Sign support on Tuesday morning about this. Ill keep you posted.
@KenV7 Just to give you an update. I worked with Sign support, this issue has now been escalated to their development team. As of right now it is considered a known bug with a case number and they are working on a solution and are hoping to provide updated documentation on how to fix the duplicate entry issues once a resolution is found. If I get more information, ill be sure to keep everyone in the loop. Sorry for the delay from my last post, but it's taken Adobe a while to get back to me after our initial contact.
@KenV7 I have some good news. We were finally able to figure out how to make this work.
After you parse json, you will add the next step to Create Item in your sharepoint list, however, you won't use any of the dynamic content from your parse json. If you do, it will immediately add the For Each loop and you're back to having multiple entries for one completed web form.
Rather you want to do a unique string expression that will allow you to grab data that was gathered in the parse json, but only the exact data you need from the cooresponding person who entered it.
For example.
lets say you have a column in the sharepoint list that is named CITY that is filled out by the web form filler, and then you have a column called STATE that is filled in by the approver.
in your parse json, when you view the output, it should tell you what the name of the column is that cooresponds with the CITY field as well as the STATE field, it should be in quotes. I believe the names that are pulled into the parse json are the names of how they were labeled when you create the webform, so they may not match up identically.
When you write your expression to get the CITY that was entered by the web form filler, it will be as follows.
body('Parse_JSON)['formDataList']?[0]?['CITY']
the [0] above is the web form filler. any field you wish to grab from the web form filler will have a [0]. If your form has a web form filler, then it goes to another person for approver. Any fields filled in by the approver will have a [1] in that area, and so on and so forth for any additional people the web form goes to for modifications or approvals. If you have a web from filler, then it goes to 2 other people, you will have 0, 1, and 2. 0 being the web form filler, 1 being the next person it went to after the web from filler, and 2 being the last person it went to.
So after the city is entered by the web form filler and sent to the next person to enter the state, your next expression will be as follows to get the state information entered by the person after the web form filler.
body('Parse_JSON)['formDataList']?[1]?['STATE']
the 0 changed to a 1, because it was the 2nd person to touch the webform that entered the state field, and the column changed from CITY to STATE because STATE was left blank by the original form filler.
You do this for each subsequent entry that you have on your sharepoint list by going through and matching up the 0, 1, 2 etc with whichever person in your process filled out each item. If all you have is a web form filler and a signer, its easy, all of them will be 0. Just remember the field between the quotes, like "CITY" or "STATE" is whatever is between the quotes in your parse json, not what your column in the sharepoint list is.
In the end, your create item in a sharepoint list entry in power automate will have no dynamic content from the parse json, it will all be unique expressions. Give it a try and let me know if you have any issues.
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!
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
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.
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