Hi all,
First time posting here - hoping somebody can help!
I'm creating an Instant flow triggered from PowerApps. The purpose of this flow is to grab ONE item from a SharePoint list based on an ID which the Power App would pass when running the flow.
For some reason, whenever I add the 'Get Item' action in Flow, I get the following error:
The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'Invalid type. Expected Integer but got String.'.
If I remove the 'Get Item' action, it runs just fine. Here's my entire flow, for reference. You can see I've tried converting the value to an integer with no joy. In addition, I've tried not even using this value in the Get Items call (just setting the ID value to '3'), and it still doesn't work. Very confused and would appreciate any help!
It's worth noting:
For some odd reason, this doesn't present any issue when using the 'Get Items' action and passing '$filter= ID eq <param from Power Apps>' , or when using an HTTP request with the same. I just don't know how to send either of those methods back to PowerApps in a way that would get me what I need (people picker.email property to compare current user email against.)
Solved! Go to Solution.
OK... I found a workaround. Silly, but here it is:
It seems powerapps could only return me an input as a string, and flow got angry any time I tried to reference that input as an integer, or even as an input to a variable that would be used as an integer.
Now, I'm doing the 'Ask in PowerApps' within my 'Init StringIDVar' (type String.), then I initiate an integer variable 'InitIDVar' and set it's value to StringIDVar.
I use 'InitIDVar' in my 'Get Item' ID Param, and it works beautifully.
ID is a number column in SharePoint and you are supply string which is causing type mismatch. please use int(3) in expression for get item.
Thanks
Hardesh
@Hardesh15 -- unfortunately that doesn't resolve the issue. I have tried the following:
All 3 options return the same error when I test the flow.
@Hardesh15 I'm not an expert but based on my most recent screenshot it looks like the type is integer. "InitializeVariable_value" was created when I clicked the 'Ask in PowerApps' button in the context of setting the 'SelectedItemID' integer variable. I didn't get an option to select the 'type' (I don't think I ever have when I'm doing an 'Ask in PowerApps'.
@Hardesh15 Been trying to debug for several hours now 😫
This flow runs fine:
As soon as I add a 'Ask in Powerapps', even if I don't use that variable, the flow fails to start with the same error when I supply any number:
IF I remove the 'Get Items' action, leaving only the Init variable action, unless I wrap the InitializeVariable_Value in an int() expression, I get the following error:
After wrapping the 'Initializevariable_Value' in an int() function like so:
..the flow runs fine again (without the 'Get Item', so it's really just firing and setting an integer variable.)
The moment I add a 'Get Item' action back, and pass that variable (which IS AN INTEGER) as the 'ID' param:
We receive the same error message on type mismatch:
Very, very confused.
OK... I found a workaround. Silly, but here it is:
It seems powerapps could only return me an input as a string, and flow got angry any time I tried to reference that input as an integer, or even as an input to a variable that would be used as an integer.
Now, I'm doing the 'Ask in PowerApps' within my 'Init StringIDVar' (type String.), then I initiate an integer variable 'InitIDVar' and set it's value to StringIDVar.
I use 'InitIDVar' in my 'Get Item' ID Param, and it works beautifully.
Hi, I'm experiencing the same issue when trying to use a PowerApps trigger to get a SharePoint item
I tried the solution posted above but still encounter issues.
Please see attached screenshot, it doesn't seem to handle the transition from string to integer.
We have other solutions currently in use that perform the same action (PowerApp trigger to get SharePoint item) which are still working without issue?
I should have clarified in my original solution post -- I'm wrapping the string variable in an int() expression as follows:
I just reproduced this solution on another flow I was working on this morning, so I hope this helps! 😎
Hi, Could you edit your original solution and add that you wrap your string in int() please?
I wonder if the int64 type used by PowerApps trigger is different to the integer type used by `Get Item` SP Action.
Hi @NathanScott ,
May you help me with this? I have the same issue but the data type I am using is String. Here's the screenshot error:
I am having this error on the simplest of Exports (one field of string values from a table) in Power BI's Power Automate.
It is a VERY simple automation.
Thoughts.
**bleep** Moffat
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