I am trying to create a new object based on three queries. If this was Powershell....
$a = invoke-restmethod -uri $query1 -method get
$b = invoke-restmethod -uri $query2 -method get
$c = invoke-restmethod -uri $query3 -method get
Each query will return a json payload such as:
==-- $a returns --==
{
"things": [
{
"thing": "Banana",
"Id": 001,
"Skin":"yes"
},
{
"thing":"Apple",
"Id": 002,
"Skin":"yes"
}
]
}
==-- $b returns --==
{
"stuff": [
{
"thing":"Banana",
"id":001,
"Color":"Yellow"
},
{
"thing":"Apple",
"Id": 002,
"Color":"Red"
}
]
}
==-- $c returns --==
{
"transpo": [
{
"thing":"Banana",
"id":001,
"ship":"Yes"
},
{
"thing":"Apple",
"Id": 002,
"ship":"No"
}
]
}
$myObject = new-object psobject
$myObject | add-member -membertype noteproperty -name fruit -value $a.thing
$myObject | add-member -membertype noteproperty -name id -value $a.id
$myObject | add-member -membertype noteproperty -name skin -value $a.skin
$myObject | add-member -membertype noteproperty -name color -value $b.color
$myObject | add-member -membertype noteproperty -name Shipped -value $c.ship
$arrFinal += $myObject
The UI keeps tossing me into endless "Apply to Each" loops and I figure I'm just shoving these rectangles in the wrong order....... I didn't paste screenshots on purpose, you have the payload very simplified, but the context is there. Each query will return results where the name and ID is shared between each. Matching up the rows for error checking is easy.... I know I need to use Select to map things... and this generally works well until I start smashing queries together 🙂
Thank you for your time and assistance.
Solved! Go to Solution.
Try this instead, done in a single action:
Output is:
[
{
"Id": "001",
"thing": "Banana",
"Skin": "yes",
"Color": "Yellow",
"Ship": "Yes"
},
{
"Id": "002",
"thing": "Apple",
"Skin": "yes",
"Color": "Red",
"Ship": "No"
}
]
Expressions in the select are:
From:
range(0, length(outputs('ComposeThings')['things']))
Map...
Id : outputs('ComposeThings')['things'][item()]['Id']
thing : outputs('ComposeThings')['things'][item()]['thing']
Skin : outputs('ComposeThings')['things'][item()]['Skin']
Color : outputs('ComposeStuff')['stuff'][item()]['Color']
Ship : outputs('ComposeTranspo')['transpo'][item()]['ship']
If you want to try out my method, simply copy this code:
{"id":"817779b0-1fe8-4af4-ae35-eff3-1ff14788","brandColor":"#8C3900","connectionReferences":{},"connectorDisplayName":"Control","icon":"data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIiIGhlaWdodD0iMzIiIHZlcnNpb249IjEuMSIgdmlld0JveD0iMCAwIDMyIDMyIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPg0KIDxwYXRoIGQ9Im0wIDBoMzJ2MzJoLTMyeiIgZmlsbD0iIzhDMzkwMCIvPg0KIDxwYXRoIGQ9Im04IDEwaDE2djEyaC0xNnptMTUgMTF2LTEwaC0xNHYxMHptLTItOHY2aC0xMHYtNnptLTEgNXYtNGgtOHY0eiIgZmlsbD0iI2ZmZiIvPg0KPC9zdmc+DQo=","isTrigger":false,"operationName":"CombineArrays","operationDefinition":{"type":"Scope","actions":{"Select":{"type":"Select","inputs":{"from":"@range(0, length(outputs('ComposeThings')['things']))","select":{"Id":"@outputs('ComposeThings')['things'][item()]['Id']","thing":"@outputs('ComposeThings')['things'][item()]['thing']","Skin":"@outputs('ComposeThings')['things'][item()]['Skin']","Color":"@outputs('ComposeStuff')['stuff'][item()]['Color']","Ship":"@outputs('ComposeTranspo')['transpo'][item()]['ship']"}},"runAfter":{"ComposeTranspo":["Succeeded"]}},"ComposeThings":{"type":"Compose","inputs":{"things":[{"thing":"Banana","Id":"001","Skin":"yes"},{"thing":"Apple","Id":"002","Skin":"yes"}]},"runAfter":{}},"ComposeTranspo":{"type":"Compose","inputs":{"transpo":[{"thing":"Banana","id":"001","ship":"Yes"},{"thing":"Apple","Id":"002","ship":"No"}]},"runAfter":{"ComposeStuff":["Succeeded"]}},"ComposeStuff":{"type":"Compose","inputs":{"stuff":[{"thing":"Banana","id":"001","Color":"Yellow"},{"thing":"Apple","Id":"002","Color":"Red"}]},"runAfter":{"ComposeThings":["Succeeded"]}}},"runAfter":{}}}
Add a new action in a flow, go to my clipboard, press CTRL-V, and you should see a new scope called "Combine Arrays".
Ok ... so I've thumbed along and here I am.
The best way to actually merge things is using the Append String to Variable!!
This way I build a counter and if I am now at my max rows I add a comma at the end and if I am at my max rows I add a comma at the end, Brilliant!
Now in order to select from 2 different sources I will need to have 2 foreach loops or in this case 2 Apply to each conditions. The end output is easy
{
"blah":"items('Apply_to_each_2')?['blah']",
"foo":"items(Apply_to_each_3')?['foo']",
"bar":"items(Apply_to_each_2)?['bar']",
} <---(no comma cause I'm matching the max, if I wasn't it would look like }, )
The Problem: As you can see in the Apply to each 2 && Apply to each 3 I am using the dynamic var. The trouble is that the Dynamic var looks like this, body('My_Second_Query')?['body']?['fruits'] -and it spits back null.
I've run into this before and if I use a manual expression and type, body('My_Second_Query')?['fruits'] Unfortunately, in the case of this Apply to each Power Automate is telling me that my manually typed line is not valid. "Correct to include a valid reference to 'My_Second_Query' for the input paramter(s) of action 'Apply_to_each_2'.
Thanks again everyone for taking the time to read and provide any advice, assistance, theories and/or superstitions. 😄
...and now I'm further along. THe problem I had on the last post was just Power Automate a-la-msft douchiness; for whatever reason if I deleted the Expression text, typed only the first part expression() and then clicked to insert inside the (), then all was fine..... meh..
Now I am into a logic trouble! Below you can see where it's happening, when I am inside the first "apply to each" it is going to run the second apply to each foreach row in the first. <- not what I want!
Inside the second apply to each, I have an Append Variable (string) and Append Variable (array). This is working amazingly well! { "object<dynamic counter>" : [ { "thing": "<dyn value>", "blah":"<dyn value>"}]}, <cntnd>
So I end up with a formatted array of objects (or however I want it to be, I'm formatted the variable myself.
What's causing this double foreach (apply to each) is that I'm merging the results of two GET queries. When I do that, the Flow Editor automagically inserts me into these loops.... argh.. so close but yet so far.....
Anyhow help, ideas, alien distress calls, coffee recommendations -> any of those would be greatly appreciated peeps! 😄
Try this instead, done in a single action:
Output is:
[
{
"Id": "001",
"thing": "Banana",
"Skin": "yes",
"Color": "Yellow",
"Ship": "Yes"
},
{
"Id": "002",
"thing": "Apple",
"Skin": "yes",
"Color": "Red",
"Ship": "No"
}
]
Expressions in the select are:
From:
range(0, length(outputs('ComposeThings')['things']))
Map...
Id : outputs('ComposeThings')['things'][item()]['Id']
thing : outputs('ComposeThings')['things'][item()]['thing']
Skin : outputs('ComposeThings')['things'][item()]['Skin']
Color : outputs('ComposeStuff')['stuff'][item()]['Color']
Ship : outputs('ComposeTranspo')['transpo'][item()]['ship']
If you want to try out my method, simply copy this code:
{"id":"817779b0-1fe8-4af4-ae35-eff3-1ff14788","brandColor":"#8C3900","connectionReferences":{},"connectorDisplayName":"Control","icon":"data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIiIGhlaWdodD0iMzIiIHZlcnNpb249IjEuMSIgdmlld0JveD0iMCAwIDMyIDMyIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPg0KIDxwYXRoIGQ9Im0wIDBoMzJ2MzJoLTMyeiIgZmlsbD0iIzhDMzkwMCIvPg0KIDxwYXRoIGQ9Im04IDEwaDE2djEyaC0xNnptMTUgMTF2LTEwaC0xNHYxMHptLTItOHY2aC0xMHYtNnptLTEgNXYtNGgtOHY0eiIgZmlsbD0iI2ZmZiIvPg0KPC9zdmc+DQo=","isTrigger":false,"operationName":"CombineArrays","operationDefinition":{"type":"Scope","actions":{"Select":{"type":"Select","inputs":{"from":"@range(0, length(outputs('ComposeThings')['things']))","select":{"Id":"@outputs('ComposeThings')['things'][item()]['Id']","thing":"@outputs('ComposeThings')['things'][item()]['thing']","Skin":"@outputs('ComposeThings')['things'][item()]['Skin']","Color":"@outputs('ComposeStuff')['stuff'][item()]['Color']","Ship":"@outputs('ComposeTranspo')['transpo'][item()]['ship']"}},"runAfter":{"ComposeTranspo":["Succeeded"]}},"ComposeThings":{"type":"Compose","inputs":{"things":[{"thing":"Banana","Id":"001","Skin":"yes"},{"thing":"Apple","Id":"002","Skin":"yes"}]},"runAfter":{}},"ComposeTranspo":{"type":"Compose","inputs":{"transpo":[{"thing":"Banana","id":"001","ship":"Yes"},{"thing":"Apple","Id":"002","ship":"No"}]},"runAfter":{"ComposeStuff":["Succeeded"]}},"ComposeStuff":{"type":"Compose","inputs":{"stuff":[{"thing":"Banana","id":"001","Color":"Yellow"},{"thing":"Apple","Id":"002","Color":"Red"}]},"runAfter":{"ComposeThings":["Succeeded"]}}},"runAfter":{}}}
Add a new action in a flow, go to my clipboard, press CTRL-V, and you should see a new scope called "Combine Arrays".
OOHhhhhh I wish I would have read this earlier 😄 That's an interesting take on things! I wish I would have thought of that! Thanks @Paulie78 🤓
Multiple uses of Compose() might actually be quicker.
I figured out what was causing the world's most painful inner and outer foreach loops, syntax!
If I click on the auto-fun-magic variable, it started spitting out the endless "Apply_to_each" loops. Not bad if you are cross-referencing two arrays, you get into some deep weeds positioning yourself - forget it if you add a third!
Keyboard mashing this insanity lead me to a more manual version of what you painted.
I've initialized a series of variables and because I had an army of counters and terminates I was perfectly setup to track myself inside of things.
side note
If you ever find yourself needing to quickly save a mash of painted JSON, mixing the preview COPY to clipboard and paste after a terminate is worth it's weight in gold !
/end side note
For the most part things are working now and I've shaved off a little over a minute of runtime. At the end I insert APPEND to ARRAY and when my counter reaches max I append the last one without a comma (see sample below - gives me an array of objects, kinda what you did with compose)
{
"Corp@{variables('intCounter')}": [
{
"Thing":"@{variables('strThing')}",
"SymbolID":"@{variables('intFilterSymID')}",
"Description":"@{variables('strBravoDescription')}",
"Color":"@{variables('intBravoColor')}",
"Ship":"@{variables('strBravoShip')}",
"SuperPower":"@{variables('strCharlieSuperPower')}"
}
]
},
I'm still struggling with the Select.
$2Array | ? {$_.ID -eq $1Array[$Counter].ID} | select color <- this is what I'm trying to replicate ATM.
...unless there's a way I can initialize a variable referencing the ID....
"Set Variable"
@{variables( @equals(body('2Array').....stuff..... ) )}
I need a way to dig out of 2Array a couple of bits of data. ID is common between 1Array and 2Array.
left and right of 'is equal to' spit out the same id number. When I run it, the input of the select is everything { blah blah blah } then I expect the output to be the chunk matching my ID, { blah }. Alas, the output shows the same as the input { blah blah blah }
Oh!! snap, I wish I had read the def on Range() 😛 that's handy!
So how do you know you are selecting the right data? What if I want to make sure that
outputs('ComposeThings')['things'][item()]['Id'] is equal to outputs('ComposeThings')['stuff'][item()]['Id']
before I populate my final step ? That good ol' data integrity check 🙂 .........
would I do an initial SELECT, map ID1, ID2, ID3 to their respective sources, then run a condition IF ID1 is equal to ID2 -and IF ID1 is equal to ID3, YES -> then do the real select?
@Paulie78 Range() has changed my life in a way that the Word paint brush change my copy/pastes 😄 This is also one of those perfect ones, a function right in front of your eyeballs [who knows for how long] and you just never used it! Anybody doing filters and selects, read this solution!!! Thanks again @Paulie78
@NorthernChuck very honoured to have had a positive impact on your life 😅. I only started using range recently myself and can't get enough of it. Well done for sorting it 👍😘
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