A Big Thank U to the entire PowerApp Community
The question NOW for me, TO FLOW or NOT to FLOW, versus OFFICE365GROUPS.HTTPREQUEST connector
I have been using a flow for some time now with no issues. (see FIGURE B:1-4 below) From within my Power App the flow gets an attachment from Sharepoint List (A) attachment data card control within a form, and uploads to a SP Document Library (AB), at the same time from the SP list A, extracts the Product ID number value from the same Form was in, to the SP Doclib AB.
This method been working for a while now BUT until recently for some odd reason, been getting a JSON error message (below Fig A). I tried to wrap parameter text with value etc… restarted rebooted rewired , still issues….what is weird is EVEN though am getting the error message the flow runs successfully and the desired result is achieved. I just can't seem to shrug this error message off.
Fig A
After coming across the Office365GroupsHttpRequest Connector Thanks to @Reza Dorrani video, https://www.youtube.com/watch?v=n3mhe88BI34&t=790s
I found this method yielding improved results.
On a blank screen, On a button I put the code below in, which pulls from an attachment control (outside of the form).
(ForAll(DataCardValue12.Attachments,Office365Groups.HttpRequest("https://graph.microsoft.com/v1.0/sites/......./root:/"&ThisRecord.Name&":/content","PUT",ThisRecord.Value)))
This solved the error issue and 1 less flow to call. But My problem is I cannot seem to find a combination of the above code with a patch or collection to get the desired result (See Figure 4 below ) i.e. Product ID Value from a selected gallery item SP list A, to the uploaded attachment column in the SP doc lib AB. all in one shot.
Is it possible to use office365groups.httprequest connector with a Patch or Collection, or maybe a combination with flow in a Power Apps environment to achieve desired results ?
FIGURE B below 1-4
Within my Form , OnSuccess I have a FlowAddanitemtoSPandDocLib.Run(Varlastitem.ID) set to run when an attachment is added, which then triggers flow , and pulls the Product ID number variable with it to the Doc Lib AB
1
2
3
4 - Current result of flow
Solved! Go to Solution.
Hi
I managed to find a solution for the problem - to land documents (without using a flow) from an attachment control to document library with some meta data from Sharepoint List ... see steps added code highlighted in red.
ForAll(DataCardValue52.Attachments,Office365Groups.HttpRequest(" https://graph.microsoft.com/v1.0/sites/..../root:/"&ThisRecord.Name&":/content","PUT",ThisRecord.Value
Refresh(DocLibAB);
ClearCollect(collastdoclib,Last(DocLibAB));
ForAll(collastdoclib,Patch(DocLibAB,LookUp(DocLibAB,ID=collastdoclib[@ID]),{ProdId2Num:varproditem2.ID}))
*Note*
ProdId2Num is column name within SP Doc lib AB where the value from the SP list A will land
varproditem2.ID is the prod SP LIST ID value from SP list A. This variable was initiated and set when clicked a button within a gallery list item of SP list A. The Button had following on the onselect; Set(varproditem2,thisitem);Navigate(newuploaddoclib)
Steps
Watch this excellent video by Reza Dorrani to understand the first forall part - Power Apps DIRECTLY upload files to SharePoint Document Library | GRAPH API - https://youtu.be/n3mhe88BI34
1.After the first FOR ALL I added a new line; REFERESH of the doc library
2.COLLECTION of that last or latest doclib record just added
3.then a new FORALL to MATCH ID's of Collection with Last Doc Lib AB record ID
4.PATCH the variable containing the Sharepoint list ID value to the Doc Lib AB Column (this is the relational table part wanted to achieve)
After a few test runs Worked... No need for the flow
Thanks
Shahzaad
Hi @Shazam007
Is the ParseJSON/Untyped feature enabled for your App?
There has been a change to this feature recently that results in most responses throwing this error.
Could you try casting the flow results returned to a specific type using JSON() function as a wrapper? I know there's a thread in the experimental section for feedback so it might be worth putting in some info there and they do mention about casting types:
https://powerusers.microsoft.com/t5/Power-Apps-Experimental-Features/ParseJSON-feedback/m-p/1877977
Cheers,
Sancho
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Thank you for quick response. See feedback in RED
Is the ParseJSON/Untyped feature enabled for your App? Yes
There has been a change to this feature recently that results in most responses throwing this error. Noted
Could you try casting the flow results returned to a specific type using JSON() function as a wrapper? Yes Tried , still errors
Ok, as I mentioned, you'll need to give your feedback around this issue in the thread that covers this experimental feature as there are no documented fixes or workarounds for this kind of thing as it's still an experimental feature:
https://powerusers.microsoft.com/t5/Power-Apps-Experimental-Features/ParseJSON-feedback/m-p/1877977
Cheers,
Sancho
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Hi
I managed to find a solution for the problem - to land documents (without using a flow) from an attachment control to document library with some meta data from Sharepoint List ... see steps added code highlighted in red.
ForAll(DataCardValue52.Attachments,Office365Groups.HttpRequest(" https://graph.microsoft.com/v1.0/sites/..../root:/"&ThisRecord.Name&":/content","PUT",ThisRecord.Value
Refresh(DocLibAB);
ClearCollect(collastdoclib,Last(DocLibAB));
ForAll(collastdoclib,Patch(DocLibAB,LookUp(DocLibAB,ID=collastdoclib[@ID]),{ProdId2Num:varproditem2.ID}))
*Note*
ProdId2Num is column name within SP Doc lib AB where the value from the SP list A will land
varproditem2.ID is the prod SP LIST ID value from SP list A. This variable was initiated and set when clicked a button within a gallery list item of SP list A. The Button had following on the onselect; Set(varproditem2,thisitem);Navigate(newuploaddoclib)
Steps
Watch this excellent video by Reza Dorrani to understand the first forall part - Power Apps DIRECTLY upload files to SharePoint Document Library | GRAPH API - https://youtu.be/n3mhe88BI34
1.After the first FOR ALL I added a new line; REFERESH of the doc library
2.COLLECTION of that last or latest doclib record just added
3.then a new FORALL to MATCH ID's of Collection with Last Doc Lib AB record ID
4.PATCH the variable containing the Sharepoint list ID value to the Doc Lib AB Column (this is the relational table part wanted to achieve)
After a few test runs Worked... No need for the flow
Thanks
Shahzaad
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 in the Forums 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 of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (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. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
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